Bug#1042262: cumin: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13
Pyparsing upstream finally made the v3.1.2 release the other day with the fix. So I guess once that lands in unstable it should be ok. On Sat, Apr 6, 2024 at 12:30 AM Antoine Beaupré wrote: > On 2023-07-27 13:04:22, Riccardo Coccioli wrote: > > I've checked the issue and opened a bug upstream to pyparsing [1] as this > > is indeed a regression. > > Running CI on cumin I've also found that pylint is reporting new issues > > related to pyparsing code, for which I've opened a separate bug upstream > > [2]. > > > > [1] https://github.com/pyparsing/pyparsing/issues/502 > > [2] https://github.com/pyparsing/pyparsing/issues/501 > > Hi! > > Thanks for this! It looks like those are fixed upstream, do we need to > update pyparsing to 3.1.2 to fix this bug or what's the next step? > > (upstream 502 is fixed in 3.1.1, in unstable, but 501 is only in > 3.1.2...) > > a. > > -- > Sous le projecteur, on ne voit pas les autres. > - Félix Leclerc >
Bug#1042262: cumin: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13
I've checked the issue and opened a bug upstream to pyparsing [1] as this is indeed a regression. Running CI on cumin I've also found that pylint is reporting new issues related to pyparsing code, for which I've opened a separate bug upstream [2]. [1] https://github.com/pyparsing/pyparsing/issues/502 [2] https://github.com/pyparsing/pyparsing/issues/501
Bug#1042262: cumin: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13
This seems to be caused by the version change of python3-pyparsing fom 3.0.9-1 in bookworm to 3.1.0-1 in trixie/sid. At first sight it looks like that this minor version change in pyparsing has caused some backward incompatibility. I'll have a look in the next few days at what changed and try to patch cumin to be compatible with the newer version while maintaining the existing backward compatibility with pyparsing up to 2.2.0. On Wed, Jul 26, 2023 at 10:31 PM Lucas Nussbaum wrote: > Source: cumin > Version: 4.2.0-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230726 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > debian/rules build > > dh build --with python3 --buildsystem=pybuild > >dh_update_autotools_config -O--buildsystem=pybuild > >dh_autoreconf -O--buildsystem=pybuild > >dh_auto_configure -O--buildsystem=pybuild > > I: pybuild base:240: python3.11 setup.py config > > /usr/lib/python3/dist-packages/setuptools/__init__.py:84: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > > !! > > > > > > > > Requirements should be satisfied by a PEP 517 installer. > > If you are using pip, you can try `pip install --use-pep517`. > > > > > > > > !! > > dist.fetch_build_eggs(dist.setup_requires) > > WARNING: The wheel package is not available. > > running config > >dh_auto_build -O--buildsystem=pybuild > > I: pybuild base:240: /usr/bin/python3 setup.py build > > /usr/lib/python3/dist-packages/setuptools/__init__.py:84: > _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are > deprecated. > > !! > > > > > > > > Requirements should be satisfied by a PEP 517 installer. > > If you are using pip, you can try `pip install --use-pep517`. > > > > > > > > !! > > dist.fetch_build_eggs(dist.setup_requires) > > WARNING: The wheel package is not available. > > running build > > running build_py > > creating /<>/.pybuild/cpython3_3.11_cumin/build/cumin > > copying cumin/__init__.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin > > copying cumin/cli.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin > > copying cumin/transport.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin > > copying cumin/grammar.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin > > copying cumin/color.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin > > copying cumin/query.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin > > creating > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/transports > > copying cumin/transports/clustershell.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/transports > > copying cumin/transports/__init__.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/transports > > creating > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/backends > > copying cumin/backends/direct.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/backends > > copying cumin/backends/knownhosts.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/backends > > copying cumin/backends/__init__.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/backends > > copying cumin/backends/openstack.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/backends > > copying cumin/backends/puppetdb.py -> > /<>/.pybuild/cpython3_3.11_cumin/build/cumin/backends > >dh_auto_test -O--buildsystem=pybuild > > I: pybuild base:240: cd > /<>/.pybuild/cpython3_3.11_cumin/build; python3.11 -m pytest > /<>/cumin/tests/unit > > = test session starts > == > > platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0 > > rootdir: /<> > > configfile: pytest.ini > > plugins: cov-4.1.0, requests-mock-1.9.3 > > collected 416 items > > > > ../../../cumin/tests/unit/test_backends.py . > [ 0%] > > ../../../cumin/tests/unit/test_cli.py .. > [ 7%] > > ../../../cumin/tests/unit/test_color.py . > [ 9%] > > ../../../cumin/tests/unit/test_grammar.py ... > [ 12%] > > ../../../cumin/tests/unit/test_init.py . > [ 19%] > > ../../../cumin/tests/unit/test_query.py > [ 23%] > > ../../../cumin/tests/unit/test_transport.py > [ 24%] > > ../../../cumin/tests/unit/backends/test_direct.py ... > [ 24%] > > ../../../cumin/tests/unit/backends/test_grammars.py ..F. > [ 26%] > > ../../../cumin/tests/unit/backends/test_knownhosts.py .. > [ 31%] > > > [ 32%] > > ../../../cumin/tests/unit/backends/test_openstack.py
Bug#1037183: Removing isc-dhcp-server breaks apparmor config
Package: isc-dhcp-server Version: 4.4.3-P1-1.1 When installing, then removing (not purging) isc-dhcp-server, it leave a broken apparmor config, leading to the following error: Jun 05 12:19:02 rpadovani apparmor.systemd[155394]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/usr.sbin.dhcpd at line 72: Could not open 'dhcpd.d' Jun 05 12:19:02 rpadovani apparmor.systemd[155458]: AppArmor parser error for /etc/apparmor.d/usr.sbin.dhcpd in profile /etc/apparmor.d/usr.sbin.dhcpd at line 72: Could not open 'dhcpd.d Jun 05 12:19:02 rpadovani apparmor.systemd[155377]: Error: At least one profile failed to load It looks like the instruction at https://salsa.debian.org/debian/isc-dhcp/-/blob/master/debian/apparmor/usr.sbin.dhcpd#L72 should be #include if exists to allow the directory to remain empty. (see "#include mechanism" in the apparmor.d(5) manpage)
Bug#1024783:
Hi, this patch should fix the issue https://review.opendev.org/c/openstack/ironic/+/866861 Thanks Riccardo
Bug#1024952:
Hi, I'm looking into this issue and after a couple of tests I still can't reproduce it. I'm using python 3.11.0 This is the output of pip freeze alembic==1.8.1 amqp==5.1.1 appdirs==1.4.4 async-timeout==4.0.2 attrs==22.1.0 automaton==3.0.1 autopage==0.5.1 bandit==1.7.4 bcrypt==4.0.0 cachetools==5.2.0 certifi==2022.9.24 cffi==1.15.1 charset-normalizer==2.1.1 click==8.1.3 cliff==4.0.0 cmd2==2.4.2 construct==2.10.68 coverage==6.4.4 cryptography==36.0.2 debtcollector==2.5.0 decorator==5.1.1 dnspython==2.2.1 dogpile.cache==1.1.8 eventlet==0.33.1 extras==1.0.0 fasteners==0.17.3 fixtures==4.0.1 Flask==2.2.2 future==0.18.2 futurist==2.4.1 gitdb==4.0.9 GitPython==3.1.27 greenlet==1.1.3 idna==3.3 ifaddr==0.2.0 importlib-metadata==4.12.0 -e git+ https://opendev.org/openstack/ironic-inspector.git@c2e4d64b605b5ca22c5135b2ba3d94f1da90f1a1#egg=ironic_inspector ironic-lib==5.3.0 iso8601==1.0.2 itsdangerous==2.1.2 Jinja2==3.1.2 jmespath==1.0.1 jsonpatch==1.32 jsonpath-rw==1.4.0 jsonpointer==2.3 jsonschema==4.14.0 keystoneauth1==5.0.0 keystonemiddleware==10.1.0 kombu==5.2.4 Mako==1.2.2 MarkupSafe==2.1.1 msgpack==1.0.4 munch==2.5.0 netaddr==0.8.0 netifaces==0.11.0 openstacksdk==0.101.0 os-service-types==1.7.0 oslo.cache==3.2.0 oslo.concurrency==5.0.1 oslo.config==9.0.0 oslo.context==5.0.0 oslo.db==12.1.0 oslo.i18n==5.1.0 oslo.log==5.0.0 oslo.messaging==14.0.0 oslo.metrics==0.5.0 oslo.middleware==5.0.0 oslo.policy==4.0.0 oslo.rootwrap==6.3.1 oslo.serialization==5.0.0 oslo.service==3.0.0 oslo.upgradecheck==2.0.0 oslo.utils==6.0.1 oslotest==4.5.0 packaging==21.3 Paste==3.5.2 PasteDeploy==2.1.1 pbr==5.10.0 ply==3.11 prettytable==3.4.1 prometheus-client==0.14.1 pycadf==3.1.1 pycparser==2.21 pyinotify==0.9.6 pymemcache==3.5.2 pyparsing==3.0.9 pyperclip==1.8.2 pyrsistent==0.18.1 python-dateutil==2.8.2 python-keystoneclient==5.0.1 python-subunit==1.4.0 pytz==2022.2.1 PyYAML==6.0 repoze.lru==0.7 requests==2.28.1 requestsexceptions==1.4.0 rfc3986==1.5.0 Routes==2.5.1 six==1.16.0 smmap==5.0.0 SQLAlchemy==1.4.40 sqlalchemy-migrate==0.13.0 sqlparse==0.4.2 statsd==3.3.0 stestr==3.2.1 stevedore==4.0.2 Tempita==0.5.2 tenacity==6.3.1 testresources==2.0.1 testscenarios==0.5.0 testtools==2.5.0 tooz==3.1.0 urllib3==1.26.12 vine==5.0.0 voluptuous==0.13.1 wcwidth==0.2.5 WebOb==1.8.7 Werkzeug==2.2.2 wrapt==1.14.1 yappi==1.4.0 zeroconf==0.39.0 zipp==3.8.1 The tests are executed using tox in a clean virtual environment. Thanks Riccardo
Bug#1025124:
hi, this patch should fix the issue https://review.opendev.org/c/openstack/sushy/+/866782 thanks Riccardo
Bug#924685: RFP: cumin -- An automation and orchestration framework
On Wed, Nov 23, 2022 at 5:15 PM Moritz Mühlenhoff wrote: > Hi Antoine, > > [Adding Riccardo Coccioli, my colleague at Wikimedia and the primary > author of Cumin to CC] > > > which makes me wonder: should we drop the debian branch on github and > > gerrit? or should we (say, debian sponsors) pull changes from you and > > sync them to salsa? > > > > how should we play this long term? > > My proposal would be to discard the debian branch on gerrit/github and > make salsa.debian.org the authoritative repository for Cumin debs (and > just build backports for apt.wikimedia.org based on the latest version > on salsa/unstable). > > But let's hear from Riccardo on this as well. > > Cheers, > Moritz > I'd like to better understand why it would be better/easier to move the debian branch into salsa instead of leaving it attached to the upstream project. I'm not that familiar with the whole debian process, so correct me if I'm missing something obvious. It would seem to me that leaving the debian branch into the upstream repository would also allow other distro/users to build their own deb package using the same config without importing a separate repository. As for the debian/watch file if you don't mind I would like to upload a slightly different one that I use for another project as the tags are all signed and it does work with the new GitHub APIs (see also the recent "Q: uscan with GitHub" thread in debian-devel). Thanks both for resuming the work on this! Riccardo
Bug#986018: avahi-daemon: local DoS (daemon dies) on badly formatted hostname query to /run/avahi-daemon/socket
Red Hat assigned CVE-2021-3502 to this bug. Some additional information can be found in [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1946914 Thanks, -- Riccardo Schirone Red Hat -- Product Security Email: rschi...@redhat.com PGP-Key ID: CF96E110 signature.asc Description: PGP signature
Bug#984938: avahi-daemon: local DoS by event-busy-loop from writing long lines to /run/avahi-daemon/socket
I have requested a CVE through Red Hat. I'm proposing a patch upstream[1]. Additional details about the flaw at [2]. [1] https://github.com/lathiat/avahi/pull/330 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1939614#c3 Thanks, -- Riccardo Schirone Red Hat -- Product Security Email: rschi...@redhat.com PGP-Key ID: CF96E110 signature.asc Description: PGP signature
Bug#954824: tentative patch for building pipewire support
Hello, attached an untested patch that may be do it, it would take a while to build chromium on my laptop. In the near future the default version of pipewire would be 0.3.0 anyway so the version config can be dropped: https://bugs.chromium.org/p/chromium/issues/detail?id=1146942 Thanks -- Riccardo Magliocchetti diff --git a/debian/control b/debian/control index fd75500..d785781 100644 --- a/debian/control +++ b/debian/control @@ -91,6 +91,7 @@ Build-Depends: libcups2-dev (>= 1.5.0), libevent-dev (>= 1.4.13), libgcrypt20-dev, + libpipewire-0.3-dev, fonts-ipafont-gothic, fonts-ipafont-mincho, diff --git a/debian/rules b/debian/rules index 917c6f9..a110b72 100755 --- a/debian/rules +++ b/debian/rules @@ -96,6 +96,8 @@ defines+=use_gio=true \ proprietary_codecs=true \ ffmpeg_branding=\"Chrome\" \ fieldtrial_testing_like_official_build=true \ + rtc_use_pipewire=true \ + rtc_pipewire_version=0.3 \ # handle parallel build options njobs=1
Bug#956811: [3dprinter-general] Bug#956811: Bug#956811: Confirmed
Thank you Gregor, I'm using Appimage (which works fine). I plan to switch to Bullseye very soon: I will definitely try the package and post the results here. However, I find these reports interesting: at least it is known that there is a problem with this package. I've been using Debian for years, but I don't know what the package management policies are, I'd just like to point out that right now, the package is useless. If I try to run cura using: QT_QUICK_CONTROLS_STYLE=material cura I get a some warnings and the UI is still broken: https://www.brixelstudio.it/Cura.png Thank you, Riccardo ps. I accidentally sent my personal data in a previous e-mail: I wrote to owner@... is it right? Who can I contact to delete my phone number? Thanks! On Thu, 21 Jan 2021 20:39:32 +0100 Gregor Riepl wrote: > > The stable debian Buster is shipping a very old version... > > https://packages.debian.org/buster/cura > > Well... I'm sorry to say, but it's very, very unlikely that buster will > receive an updated Cura version. New package versions usually land in > sid and testing, and a new Debian stable release will happen later this > year anyway. > > If you'd like to run a current version of Cura (that works a little bit > better than the outdated one in buster), I warmly recommend that you > update to bullseye now and help with testing. As a matter of fact, I > think Debian testing is much more suited for desktop use than stable. > > If you just want to "make it work", you can use the AppImage provided by > UltiMaker, of course. > > That being said, the rendering issue is still present in 4.8. If the > upstream patch won't help, we'll have to go back and see if anything can > be done on the Debian side. > > In the meantime, can you try running Cura with the theme override I > mentioned? Perhaps it will help for now. >
Bug#956811: Confirmed
I do confirm that the bug is present now in the cura package (v. 3.3.1) and makes the software unusable. This has been reported to Cura developers: https://github.com/Ultimaker/Cura/issues/6841 It is not related to video card (it does not work with modern intel or nvidia). Using Debian 10, 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux Thank you, Riccardo
Bug#980171: libobs-dev: missing dependency on libsmde-dev
Package: libobs-dev Version: 26.1.2+dfsg1-1 Severity: normal X-Debbugs-Cc: riccardo.magliocche...@gmail.com Hello, I'm trying to build an obs plugin but it fails because of missing include: In file included from /usr/include/obs/graphics/vec4.h:22, from /usr/include/obs/graphics/vec3.h:21, from /usr/include/obs/obs.h:26, from /usr/include/obs/obs-module.h:20, from ../pipewire.h:23, from ../window-capture.c:21: /usr/include/obs/util/sse-intrin.h:24:10: fatal error: simde/x86/sse2.h: File o directory non esistente 24 | #include Given than it's from an obs header file libobs-dev may depend on libsmde-dev. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libobs-dev depends on: ii libobs0 26.1.2+dfsg1-1 libobs-dev recommends no packages. libobs-dev suggests no packages. -- no debconf information -- Riccardo Magliocchetti @rmistaken
Bug#976961:
Also submitted upstream: https://github.com/mate-desktop/mate-sensors-applet/issues/117
Bug#976961: Graphs with the same unit should use the same scale
Package: mate-sensors-applet Version: 1.24.1-1 I would like to be able to compare readings on graphs showing temperature at a glance: if the bar on the disk temp is higher than the CPU temperature graph, then it should mean that the disk temperature is higher than the CPU's. However, this is not currently the case: each graph is scaled according to the sensor's min and max values, making graphs useless without hovering for reading the actual values. The attached screenshot shows a disk temperature graph (left) seemingly higher than the CPU temperature graph (right), but hovering reveals that the opposite is true: disk is at 45 °C and CPU is at 58 °C. Currently installed relevant packages: ``` Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== ii mate-sensors-applet1.24.1-1 amd64Display readings from hardware sensors in your MATE panel ii mate-sensors-applet-common 1.24.1-1 all Display readings from hardware sensors in your MATE panel (common files) ``` Thanks, Riccardo
Bug#962713: please add support for x13as
On Fri, 12 Jun 2020, Dirk Eddelbuettel wrote: | Quickly looking at the source code of gretl, I am under the impression that it | may need to be slightly patched in order to find the x13as executable (it seems | to hardcode a Windows .exe path). But I did not really investigate, so I leave | that up to you. I believe that no adjustment is needed. The .exe path you're referring to is buried within an #if directive, and is only used when cross-compiling for windows. In fact, I just installed the debian x13as package and tried using that from within gretl instead of my home-baked x13as, and it works just fine. --- Riccardo (Jack) Lucchetti Dipartimento di Scienze Economiche e Sociali (DiSES) Università Politecnica delle Marche (formerly known as Università di Ancona) r.lucche...@univpm.it http://www2.econ.univpm.it/servizi/hpp/lucchetti ---
Bug#935653: [unattended-upgrades] /usr/bin/unattended-upgrade hogging cpu
Package: unattended-upgrades
Version: 1.14
Severity: normal
--- Please enter the report below this line. ---
Hello,
I have /usr/bin/python3 /usr/bin/unattended-upgrade using 100% of a core calling
stat in a very tight loop for no apparent good reason. It does so by holding the
/var/lib/dpkg/lock-frontend lock.
Even after a kill -9, a new process shows the same behaviour.
Stracing it looks like it's in a loop calling stat for files that does not
exists:
sudo strace -c -p 6778
strace: Process 6778 attached
strace: [ Process PID=6778 runs in x32 mode. ]
strace: [ Process PID=6778 runs in 64 bit mode. ]
^Cstrace: Process 6778 detached
% time seconds usecs/call callserrors syscall
-- --- --- - -
100,000,147692 1 77789 57944 stat
-- --- --- - -
100.000,147692 77789 57944 total
Excerpt on actual calls:
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-en",
{st_mode=S_IFREG|0644, st_size=208649, ...}) = 0
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it",
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.xz",
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.bz2",
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.lzma",
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.gz",
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.lz4",
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
stat("/var/lib/apt/lists/ftp.de.debian.org_debian_dists_sid_contrib_i18n_Translation-it.zst",
0x7ffd7bd40c80) = -1 ENOENT (File o directory non esistente)
...
Thanks
--
Riccardo Magliocchetti
@rmistaken
http://menodizero.it
Bug#933092: [pypy3] watch regex should match pypy3.6
Package: pypy3 Version: 7.0.0+dfsg-3 Severity: minor --- Please enter the report below this line. --- Upstream is now following python3.6 compatibility so the watch regex should follow pypy3.6 and not pypy3.5 as in https://salsa.debian.org/debian/pypy3/commit/b457512dc589007b23c7c824925b8da37e0a0048 Thanks -- Riccardo Magliocchetti @rmistaken http://menodizero.it
Bug#868015: knockd does not start after system reboot
Package: knockd Version: 0.7-1 Followup-For: Bug #868015 Dear Maintainer, Kindly consider fixing the bug. A patch has been available since Sep 2017 and it consists in a 3 line edit to the systemd unit file. BR, Riccardo -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-0.bpo.1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages knockd depends on: ii libc6 2.24-11+deb9u4 ii libpcap0.8 1.8.1-3 ii logrotate 3.11.0-0.1 ii lsb-base9.20161125 knockd recommends no packages. knockd suggests no packages. -- Configuration Files: /etc/knockd.conf changed: [redacted - not useful] -- no debconf information
Bug#923522: Upgrading `linux-image-4.9.0-8-amd64` breaks loading kernel modules
> > The problem is that both packages install kernel modules in the same > > directory `/lib/modules/4.9.0-8-amd64` although they are not binary > > compatible. > > This is a known issue with upgrades that we don't currently plan to > fix. May I ask why no fix will be considered? > > Needless to say, the issue with loading kernel modules is corrected by a > > reboot, but I think that the larger issue here is that upgrading a > > kernel package, on the *stable* distribution and *keeping the same > > (nominal) kernel version*, can break a running system -- all while that a > > solution for this problem has been known for many years now... > > Normally all required modules would be loaded during boot, so there's > no breakage. I beg to differ. The case which prompted me to report this bug (see [1]) is the following: 1. spin up a cloud-based Debian VM, 2. run `apt upgrade`, *then* 3. install & customize software. If the kernel has to be upgraded, then this can break after step 2.; e.g. you may not be able to run `ip6tables` because IPv6 modules cannot be loaded. Still, I think this kind of usage of cloud-based VMs is common enough to merit some consideration. I can also imagine usage scenarios where this could be an issue with physical servers as well, since it basically breaks "hotplug" functionality -- forcing an immediate reboot after an update. I can understand if the project has already given it consideration and decided that the issue is not worth time spent fixing it or the additional hassle in packaging kernels, but to me it was surprising enough that I think it needs to be documented somehow (e.g. FAQ?): sysadmins should be alerted that you're basically assumed to reboot *immediately* after `apt upgrade`. [1]: https://github.com/gc3-uzh-ch/elasticluster/issues/609
Bug#923522: Upgrading `linux-image-4.9.0-8-amd64` breaks loading kernel modules
Package: linux-image-4.9.0-8-amd64 Version: 4.9.144-3.1 As of March 1, 2019, running `apt upgrade` on a recent Debian 9 official cloud image, results in package `linux-image-4.9.0-8-amd64` being upgraded: $ apt list --upgradable [...] linux-image-4.9.0-8-amd64/stable-updates 4.9.144-3.1 amd64 [upgradable from: 4.9.130-2] [...] However, after the upgrade, kernel modules are no longer loadable; here is an example triggered by `ip6tables-restore`: # tail /var/log/syslog Mar 1 10:11:08 stretch kernel: [ 502.887305] nf_defrag_ipv6: disagrees about version of symbol inet_frags_fini Mar 1 10:11:08 stretch kernel: [ 502.887894] nf_defrag_ipv6: Unknown symbol inet_frags_fini (err -22) Mar 1 10:11:08 stretch kernel: [ 502.888985] nf_defrag_ipv6: disagrees about version of symbol inet_frag_find Mar 1 10:11:08 stretch kernel: [ 502.889712] nf_defrag_ipv6: Unknown symbol inet_frag_find (err -22) Mar 1 10:11:08 stretch kernel: [ 502.890386] nf_defrag_ipv6: disagrees about version of symbol ip6_expire_frag_queue Mar 1 10:11:08 stretch kernel: [ 502.891048] nf_defrag_ipv6: Unknown symbol ip6_expire_frag_queue (err -22) Mar 1 10:11:08 stretch kernel: [ 502.891885] nf_defrag_ipv6: Unknown symbol pskb_trim_rcsum_slow (err 0) Mar 1 10:11:08 stretch kernel: [ 502.893030] nf_defrag_ipv6: disagrees about version of symbol inet_frag_kill Mar 1 10:11:08 stretch kernel: [ 502.893688] nf_defrag_ipv6: Unknown symbol inet_frag_kill (err -22) Mar 1 10:11:08 stretch kernel: [ 502.894594] xt_conntrack: cannot load conntrack support for proto=10 The problem is that both packages install kernel modules in the same directory `/lib/modules/4.9.0-8-amd64` although they are not binary compatible. Needless to say, the issue with loading kernel modules is corrected by a reboot, but I think that the larger issue here is that upgrading a kernel package, on the *stable* distribution and *keeping the same (nominal) kernel version*, can break a running system -- all while that a solution for this problem has been known for many years now... Thanks for any help! Riccardo
Bug#916026: bootchart2 FTBFS with glibc 2.28
Il 09/12/18 14:10, Adrian Bunk ha scritto:
Source: bootchart2
Version: 0.14.4-3
Severity: serious
Tags: ftbfs buster sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bootchart2.html
...
collector/collector.c: In function 'enter_environment':
collector/collector.c:633:47: warning: implicit declaration of function
'makedev' [-Wimplicit-function-declaration]
if (mknod (TMPFS_PATH "/kmsg", S_IFCHR|0666, makedev(1, 11)) < 0) {
^~~
...
cc -g -Wall -O0 -pthread -Icollector -o bootchart-collector
collector/collector.o collector/output.o collector/tasks.o
collector/tasks-netlink.o collector/dump.o
/usr/bin/ld: collector/collector.o: in function `enter_environment':
/build/1st/bootchart2-0.14.4/collector/collector.c:633: undefined reference to
`makedev'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:39: bootchart-collector] Error 1
This has already been fixed upstream here:
commit add58c3b57064afd6f7d2fd5f09006d28a3e770e
Author: Mike Frysinger
Date: Thu Apr 21 00:19:32 2016 -0400
include sys/sysmacros.h for major/minor/makedev
These funcs are defined in the sys/sysmacros.h header, not sys/types.h.
Linux C libraries are updating to drop the implicit include, so we need
to include it explicitly.
diff --git a/collector/collector.c b/collector/collector.c
index cfdcb26..2f3ce6b 100644
--- a/collector/collector.c
+++ b/collector/collector.c
@@ -33,6 +33,7 @@
#include "common.h"
#include
+#include
#include
#include
#include
--
Riccardo Magliocchetti
@rmistaken
http://menodizero.it
Bug#904917: Gnome randomly crash and restart to login.
Dear maintainer, on the Dell G5 system this is a relevant dmesg log of a gnome crash / restart. Thank you, Ricky [ 50.196800] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/fecs_bl.bin [ 50.197146] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/fecs_inst.bin [ 50.197393] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/fecs_data.bin [ 50.197627] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/fecs_sig.bin [ 50.197870] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/gpccs_bl.bin [ 50.198150] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/gpccs_inst.bin [ 50.198298] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/gpccs_data.bin [ 50.198394] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/gr/gpccs_sig.bin [ 50.199588] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/sec2/image.bin [ 50.199878] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/sec2/desc.bin [ 50.200022] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/sec2/sig.bin [ 50.202673] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/acr/ucode_load.bin [ 50.203144] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/acr/ucode_unload.bin [ 50.203509] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/acr/bl.bin [ 50.203671] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/acr/unload_bl.bin [ 50.204262] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/nvdec/scrubber.bin [ 52.352010] nouveau :01:00.0: secboot: error during falcon reset: -110 [ 52.352023] nouveau :01:00.0: gr: init failed, -110 [ 52.885053] fuse init (API version 7.27) [ 55.621474] Bluetooth: RFCOMM TTY layer initialized [ 55.621486] Bluetooth: RFCOMM socket layer initialized [ 55.621495] Bluetooth: RFCOMM ver 1.11 [ 58.296647] rfkill: input handler disabled [ 61.275809] pci_raw_set_power_state: 9 callbacks suppressed [ 61.275811] nouveau :01:00.0: Refused to change power state, currently in D3 [ 241.914334] rfkill: input handler enabled [ 242.243702] nouveau :01:00.0: Refused to change power state, currently in D3 [ 243.782266] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/nvdec/scrubber.bin [ 245.823526] nouveau :01:00.0: secboot: error during falcon reset: -110 [ 245.823539] nouveau :01:00.0: gr: init failed, -110 [ 253.707510] nouveau :01:00.0: Refused to change power state, currently in D3 [ 254.370102] nouveau :01:00.0: firmware: direct-loading firmware nvidia/gp106/nvdec/scrubber.bin [ 256.415398] nouveau :01:00.0: secboot: error during falcon reset: -110 [ 256.415406] nouveau :01:00.0: gr: init failed, -110 [ 257.889260] rfkill: input handler disabled [ 264.783277] nouveau :01:00.0: Refused to change power state, currently in D3
Bug#904917: general: Gnome randomly crash and restart to login.
I have used gnome on the previus cited Lenovo Laptop without extension for some months and gnome is generally more stable BUT occasionaly I had the same identical crash. Nvidia drivers were loaded. I had setup the same identical system on a Dell G5, withOUT nvidia drivers but nouveau only and I suffer the same identical trouble, about once every day. Gnome exensions are enabled: - Freon - GsConnect I do 3d graphics but crash is totally indipendent and happens even on a soft use (mail, browser, ecc...). Here some info. I'll post dmesg info next crash. Thank you, Riccardo # lsmod | grep nouveau nouveau 2162688 1 mxm_wmi16384 1 nouveau ttm 131072 1 nouveau drm_kms_helper196608 2 i915,nouveau drm 471040 23 drm_kms_helper,i915,ttm,nouveau i2c_algo_bit 16384 2 i915,nouveau video 45056 4 dell_wmi,dell_laptop,i915,nouveau wmi28672 6 dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor,mxm_wmi,nouveau button 16384 1 nouveau # lspci -nnk | grep -iA2 vga 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e9b] Subsystem: Dell Device [1028:0825] Kernel driver in use: i915 -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106M [GeForce GTX 1060] [10de:1c20] (rev a1) Kernel driver in use: nouveau Kernel modules: nouveau Il giorno dom, 29/07/2018 alle 15.50 +0200, Riccardo Gagliarducci ha scritto: > Package: general > Severity: grave > Justification: causes non-serious data loss > > Dear Maintainer, > > on Lenovo laptop ideapad 520 Gnome randomly crash and, after some > seconds of > text, the system ask me to login to gnome, as if I had access to it > during > boot. > All the opened software and data is gone. > > It happens 1 to 4 times a day. > > I have consulted the syslog, kern, Xorg but I can't find any hints on > the > package is causing the error. > > > The laptop harware is: > Intel® Core™ i7-8550U CPU @ 1.80GHz × 8 > > and double graphic card: > > VGA compatible controller: Intel Corporation UHD Graphics 620 > (Kabylake > GT2)(rev 07) > Subsystem: Lenovo UHD Graphics 620 > Kernel driver in use: i915 > > 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev > ff) > Kernel modules: nvidia > > The system is Debian GNU/Linux buster/sid 64 bit using bumblebee and > Nvidia > driver Version: 390.48. > > > Thank you, > Riccardo > > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing'), (2, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), > LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash
Bug#909728: I found a workaround
On Tue, 2 Oct 2018 08:51:25 +0200 Matijs van Zuijlen wrote: Dear maintainer, The folder /usr/local/share/fonts turned out to be empty. Removing it stopped the messages appearing. Oh, thank you so much, that was driving me crazy. In fact, maybe the severity for this bug could be upgraded, since (a) seems to be related to bug #897251 (which was then apparently resolved via a workaround, but still...); the exact chain of events that triggers the message on stderr is very well laid out in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897251#18 (b) it hits the "gretl" program quite badly: gretl uses gnuplot as its graphical engine, and throws an error if gnuplot throws something on stderr (which is what happens if you have an empty /usr/local/share/fonts dir). --- Riccardo (Jack) Lucchetti Dipartimento di Scienze Economiche e Sociali (DiSES) Università Politecnica delle Marche (formerly known as Università di Ancona) r.lucche...@univpm.it http://www2.econ.univpm.it/servizi/hpp/lucchetti ---
Bug#904917: general: Gnome randomly crash and restart to login.
I'm leaving for holidays, may I freeze this bug until end of August? In dmsg, I found: [ 6737.746966] gnome-shell[2131]: segfault at 663466343778 ip 7f0a52cf3c31 sp 7ffd58e51e98 error 4 in libgobject- 2.0.so.0.5600.1[7f0a52cbe000+52000] But I'd like to investigate more... Thank you, Riccardo Il giorno sab, 04/08/2018 alle 02.21 +0200, Simon Richter ha scritto: > Hi, > > On 04.08.2018 01:32, Riccardo Gagliarducci wrote: > > > after firmware update it still happens ~once a day, > > still without doing anything particular. > > Is anything listed in the kernel log? > > After a crash, log back in, then, as root: > > # cat /proc/uptime > > The first number is the number of seconds the system is running. > > # dmesg > > This will dump the kernel logfile to the console. At the beginning of > each line is a timestamp. The uptime you got earlier gives you a > rough > estimate which lines are recent, these have a good chance of being > related. > >Simon >
Bug#904917: general: Gnome randomly crash and restart to login.
Thank you, after firmware update it still happens ~once a day, still without doing anything particular. RG Il giorno dom, 29/07/2018 alle 11.03 -0300, Henrique de Moraes Holschuh ha scritto: > On Sun, 29 Jul 2018, Riccardo Gagliarducci wrote: > > on Lenovo laptop ideapad 520 Gnome randomly crash and, after some > > seconds of > > Are you using the latest version of the ideapad 520 firmware > (BIOS/UEFI > and EC) ? If not, please upgrade it. >
Bug#904917: general: Gnome randomly crash and restart to login.
Package: general Severity: grave Justification: causes non-serious data loss Dear Maintainer, on Lenovo laptop ideapad 520 Gnome randomly crash and, after some seconds of text, the system ask me to login to gnome, as if I had access to it during boot. All the opened software and data is gone. It happens 1 to 4 times a day. I have consulted the syslog, kern, Xorg but I can't find any hints on the package is causing the error. The laptop harware is: Intel® Core™ i7-8550U CPU @ 1.80GHz × 8 and double graphic card: VGA compatible controller: Intel Corporation UHD Graphics 620 (Kabylake GT2)(rev 07) Subsystem: Lenovo UHD Graphics 620 Kernel driver in use: i915 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev ff) Kernel modules: nvidia The system is Debian GNU/Linux buster/sid 64 bit using bumblebee and Nvidia driver Version: 390.48. Thank you, Riccardo -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (2, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Bug#677224: wicd-gtk tray icon status always says "Not connected", able to reproduce?
I had to install python-appindicator to show the wicd-gtk tray icon in the recently-updated enlightenment environment (#894529). The tray icon stays not connected (exclamation mark in a black-bordered triangle) even if I am connected. Sooo, to reproduce: root@hactar:~# LANG=C dpkg -l *wicd* *appindicator* *enlightenment* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii enlightenment 0.22.1-3 amd64 X11 window manager based on EFL ii enlightenment-data 0.22.1-3 all X11 window manager based on EFL - run time data files ii libappindicator1:amd64 0.4.92-5 amd64 allow applications to export a menu into the panel ii libayatana-appindicator3-1 0.5.3-3 amd64 Ayatana Application Indicators (GTK-3+ version) ii python-appindicator0.4.92-5 amd64 Python bindings for libappindicator ii python-wicd1.7.4+tb2-5 all wired and wireless network manager - Python module un python2.7-appindicator (no description available) ii wicd 1.7.4+tb2-5 all wired and wireless network manager - metapackage un wicd-cli (no description available) un wicd-client (no description available) un wicd-curses (no description available) ii wicd-daemon1.7.4+tb2-5 all wired and wireless network manager - daemon ii wicd-gtk 1.7.4+tb2-5 all wired and wireless network manager - GTK+ client The tray icon used to work with the old enlightenment version (e17), without appindicator (xembed support?) Thanks for your work, Riccardo
Bug#894529: wicd-gtk tray icon not showing anymore in enlightenment (missing appindicator dependency)
Package: wicd-gtk Version: 1.7.4+tb2-5 Severity: normal Hi, I just updated my window manager (enlightenment) and the wicd-gtk tray icon was not showing anymore. It seems around e20 they stopped providing the xembed tray-system support in favour of appindicator. Could you please add python-appindicator as depends/raccomends for wicd-gtk? (then I think I can reproduce #677224, but at least I have some icon to click on) :) Thanks for maintaining wicd! Riccardo
Bug#892912: pytrainer: startup fails because gtk2 features were dropped from matplotlib
Source: pytrainer Version: 1.11.0-1 Severity: grave Tags: sid buster upstream Forwarded: https://github.com/pytrainer/pytrainer/issues/114 Since matplotlib 2.1.1-1 was uploaded to unstable dropping gtk2 features (last january) pytrainer fails at startup throwing an ImportError. Please see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885511 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889137 https://github.com/pytrainer/pytrainer/issues/114 Severity set to grave as pytrainer is unusable (both in sid and testing). Thanks for your work, Riccardo
Bug#882011: same thing for python-enum34
Uops, sorry, I have just seen you already retitled/fixed the bug... I'm sorry for the noise. Riccardo
Bug#882011: same thing for python-enum34
Control: retitle -1 python-cryptography: no longer depends on cffi-backend and enum, programs fail to start The same is happening with obnam and python-enum34: riccio@hactar:~$ obnam generations Traceback (most recent call last): File "/usr/bin/obnam", line 18, in import obnamlib File "/usr/lib/python2.7/dist-packages/obnamlib/__init__.py", line 91, in from .app import App, ObnamIOError, ObnamSystemError File "/usr/lib/python2.7/dist-packages/obnamlib/app.py", line 25, in import paramiko File "/usr/lib/python2.7/dist-packages/paramiko/__init__.py", line 30, in from paramiko.transport import SecurityOptions, Transport File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 33, in from cryptography.hazmat.primitives.ciphers import algorithms, Cipher, modes File "/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/__init__.py", line 7, in from cryptography.hazmat.primitives.ciphers.base import ( File "/usr/lib/python2.7/dist-packages/cryptography/hazmat/primitives/ciphers/base.py", line 12, in from cryptography.exceptions import ( File "/usr/lib/python2.7/dist-packages/cryptography/exceptions.py", line 7, in from enum import Enum ImportError: No module named enum Thanks, Riccardo
Bug#878540: munin-plugins-core: issues with snmp/name resolution
Package: munin-plugins-core Version: 2.0.33-1 Severity: minor Hi, it seems that if you can't resolve hostnames when munin-node starts, the SNMP-based plugins will be assigned to the local host name instead of the node name one expects. More details: - zaphod.casa.mia: munin-node and dns server (I discovered the issue at boot time, but you can reproduce it stopping the DNS server or removing entries from /etc/hosts) - c877-cs-1.casa.mia: the device we want to monitor via snmp - /etc/munin/munin.conf stanzas: [zaphod.casa.mia] address 127.0.0.1 use_node_name yes [c877-cs-1.casa.mia] address 127.0.0.1 use_node_name no Steps to reproduce: 1. telnet localhost 4949 1a. list zaphod.casa.mia -> check that no snmp_* entries are shown 1b. list c877-cs-1.casa.mia -> check that the usual snmp_* entries are shown 2. stop the dns and/or remove the entry from /etc/hosts 3. start munin-node 4. telnet localhost 4949 4a. list zaphod.casa.mia -> snmp_c877-cs-1.casa.mia_* appear 4b. list c877-cs-1.casa.mia -> only snmp_c877-cs-1.casa.mia_uptime is shown (sometimes something else) In /var/log/munin/munin-node.log is then seen (just one for clarity): 2017/10/14-12:25:33 [707] Error output from snmp_c877-cs-1.casa.mia_if_2: 2017/10/14-12:25:33 [707] Could not set up SNMP 2 session to c877-cs-1.casa.mia: Unable to resolve the UDP/IPv4 address "c877-cs-1.casa.mia" 2017/10/14-12:25:33 [707] Service 'snmp_c877-cs-1.casa.mia_if_2' exited with status 11/0. /etc/munin/plugins/snmp_c877-cs-1.casa.mia_if_2 is a symlink to /usr/share/munin/plugins/snmp__if_ Seeing the above log I'm not sure if this report should be assigned to munin-node or if it's something in Munin::Plugin::SNMP. Thanks for maintaining munin, Riccardo -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages munin-plugins-core depends on: ii munin-common 2.0.33-1 ii perl 5.24.1-3+deb9u2 Versions of packages munin-plugins-core recommends: ii libnet-snmp-perl 6.0.1-2 Versions of packages munin-plugins-core suggests: pn conntrack pn libcache-cache-perl pn libdbd-mysql-perl pn libnet-dns-perl pn libnet-netmask-perl pn libnet-telnet-perl pn libxml-parser-perl ii python 2.7.13-2 ii ruby 1:2.3.3 -- no debconf information
Bug#873292: ip(8) changed syntax
I think the issue you are seeing is due to a syntax change in the ip(8) command. Please compare: https://manpages.debian.org/jessie/iproute2/ip-link.8.en.html https://manpages.debian.org/stretch/iproute2/ip-link.8.en.html ciao, Riccardo
Bug#804629: linux-image-amd64: Cannot mount LVM RAID1 file system at boot
I've just had the chance to try again now. Sorry but I had to try on a different server. On 2017-03-24 12:02, Jarek Kamiński wrote: W dniu 24.03.2017 o 11:45, SW Riccardo Scartozzi pisze: On recent kernels it just works. Sorry but as said in my previous post I'm still experiencing the issue even with the kernel version 4.9 from backports. Have you tried creating the volume on 4.9, or just activating a previously-created volume? I confirm you that it works! The logical volume with raid1 has to be created on kernel linux 4.9, if the raid is created on different linux version (as it was my first case) it won't be possible to activate it neighter after switching to kernel 4.9!!! I can then also confirm that the activation of lvmetad is totally irrelevant. So I can confirm what Jarek Kamiński said: the bug is solved since 4.9. Thank you again, risca
Bug#804629: linux-image-amd64: Cannot mount LVM RAID1 file system at boot
On recent kernels it just works. Sorry but as said in my previous post I'm still experiencing the issue even with the kernel version 4.9 from backports. I believe the bug can be closed now. Sorry, but the bug is still present! As Jarek Kamiński himself said: The legacy mirror is not affected, only raid1. The steps to reproduce are: lvcreate -L 100M --type raid1 -m 1 -n test-raid lvchange -an test-raid lvchange -ay test-raid and it either works or not. I haven't test to activate and deactivate the logical volume, therefore I experience the issue every time on system reboot (but I will make a go). Here is what I get on logs (sorry for not posting earlier): [0.00] Linux version 4.9.0-0.bpo.2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.9.13-1~bpo8+1 (2017-02-27) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.2-amd64 root=/dev/md1 ro rootdelay=10 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.2-amd64 root=/dev/md1 ro rootdelay=10 [0.600171] pmd_set_huge: Cannot satisfy [mem 0xf800-0xf820] with a huge-page mapping due to MTRR override. [0.976001] systemd-udevd[90]: starting version 215 [0.976401] random: systemd-udevd: uninitialized urandom read (16 bytes read) [1.004407] usb usb1: Manufacturer: Linux 4.9.0-0.bpo.2-amd64 xhci-hcd [1.007544] usb usb2: Manufacturer: Linux 4.9.0-0.bpo.2-amd64 xhci-hcd [1.293276] usb usb3: Manufacturer: Linux 4.9.0-0.bpo.2-amd64 ehci_hcd [1.313268] usb usb4: Manufacturer: Linux 4.9.0-0.bpo.2-amd64 ehci_hcd [ 14.155760] md: raid1 personality registered for level 1 [ 14.157449] md: raid0 personality registered for level 0 [ 14.573040] md: raid6 personality registered for level 6 [ 14.573101] md: raid5 personality registered for level 5 [ 14.573160] md: raid4 personality registered for level 4 [ 14.611467] md: md1 stopped. [ 14.611779] md: bind [ 14.611910] md: bind [ 14.612648] md/raid1:md1: active with 2 out of 2 mirrors [ 14.612730] md1: detected capacity change from 0 to 20970405888 [ 14.895923] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: (null) [ 15.936768] systemd-udevd[359]: starting version 215 [ 17.755542] EXT4-fs (md1): re-mounted. Opts: errors=remount-ro [ 19.971243] md/raid1:mdX: not clean -- starting background reconstruction [ 19.972180] md/raid1:mdX: active with 2 out of 2 mirrors [ 19.977646] mdX: invalid bitmap file superblock: bad magic [ 19.978540] mdX: bitmap file superblock: [ 19.978547] mdX: failed to create bitmap (-22) System infos: $ uname -a Linux SWhost 4.9.0-0.bpo.2-amd64 #1 SMP Debian 4.9.13-1~bpo8+1 (2017-02-27) x86_64 GNU/Linux $ cat /etc/debian_version 8.7 Thank you, risca
Bug#804629: linux-image-amd64: Cannot mount LVM RAID1 file system at boot
I was experiencing the same issue as describe in this bug report and, as pointed by Harrison Metzger, the bug was probably introduced after kernel 3.16-3-amd64 because for sure it was working until that version. I don't get what causes the problem. It could be interesting to test if the problem is affect only if the mirror is a type raid1 or also if it is a type "mirror" (legacy). I don't know neighter if there is a problem while shutting down (is it the same if the OS reboot or it before rebooting the mirror is deactivate?). But the funniest thing is that if you activate lvmetad (switch to option "use_lvmetad = 1" in /etc/lvm/lvm.conf) the lvm with mirror type as raid1 starts to work again after reboot (at least tested on squeeze Linux 4.9.0-0.bpo.2-amd64 #1 SMP Debian 4.9.13-1~bpo8+1 (2017-02-27) x86_64 GNU/Linux). I don't know why nor it seem documented. Hope that this will save some headache to you as well. Cheers, risca
Bug#855940: alacarte: Python context internal state bug. Syslog
Package: alacarte Version: 3.11.91-2 Severity: normal Dear Maintainer, checking /var/log/syslog I discover that: Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python context internal state bug. this should not happen! Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python context internal state bug. this should not happen! Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python context internal state bug. this should not happen! Feb 23 10:32:29 triceratopo alacarte-made-7.desktop[1599]: ERROR: Python context internal state bug. this should not happen! The log reports this line hundreds of times each seconds, ending with a huge log: root@triceratopo:/var/log# ls -lah syslog -rw-r- 1 root adm 766M feb 23 15:40 syslog I do expect: alacarte not causing this error limit the report of this error alacarte version is 3.11.91-2 status is Ok, installed Thank you, Riccardo -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages alacarte depends on: ii gir1.2-gdkpixbuf-2.0 2.31.1-2+deb8u5 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gmenu-3.0 3.13.3-6 ii gir1.2-gtk-3.03.14.5-1+deb8u1 ii gnome-menus 3.13.3-6 ii python-gi 3.14.0-1 pn python:any alacarte recommends no packages. alacarte suggests no packages. -- no debconf information
Bug#847204: nfs-kernel-server: `systemctl status` incorrectly reports server "active" even if not started
apper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 56360 status 1000241 tcp 39499 status On the other hand, `systemctl restart nfs-kernel-server` (or a reboot) does actually start the NFS server. System information: $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 8.6 (jessie) Release:8.6 Codename: jessie $ dpkg -l nfs-kernel-server nfs-common linux-image-3.16.0-4-amd64 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=-=-=== ii linux-image-3.16.0-4-amd643.16.36-1+deb8u1 amd64 Linux 3.16 for 64-bit PCs ii nfs-common1:1.2.8-9 amd64 NFS support files common to client and server ii nfs-kernel-server 1:1.2.8-9 amd64 support for NFS kernel server $ uname -a Linux debian-nfs-bug 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux Thanks, Riccardo
Bug#838572: clang-3.9: scan-view-3.9 does not find python modules
Package: clang-3.9 Version: 1:3.9-1 Severity: normal Hello, scan-view-3.9 fails to find the needed python modules: $ scan-view-3.9 scan-build-master/ Traceback (most recent call last): File "/usr/bin/scan-view-3.9", line 143, in main() File "/usr/bin/scan-view-3.9", line 140, in main run(port, args, args.root) File "/usr/bin/scan-view-3.9", line 70, in run import ScanView ImportError: No module named ScanView the problem is that os.path.dirname(__file__) is /usr/bin and not /usr/share/clang/scan-view-3.9/bin as expected by the script. A quick way to fix that is to hardcode the scan-view dir: $ diff -u ../bin/scan-view.old ../bin/scan-view --- ../bin/scan-view.old2016-09-22 16:31:01.209052200 +0200 +++ ../bin/scan-view2016-09-22 16:39:19.383579819 +0200 @@ -22,6 +22,8 @@ kDefaultPort = 8181 kMaxPortsToTry = 100 +BASE_DIR = '/usr/share/clang/scan-view-3.9' + ### @@ -61,7 +63,7 @@ def run(port, options, root): # Prefer to look relative to the installed binary -share = os.path.dirname(__file__) + "/../share/" +share = os.path.join(BASE_DIR, 'share') if not os.path.isdir(share): # Otherwise look relative to the source share = os.path.dirname(__file__) + "/../../scan-view/share" -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages clang-3.9 depends on: ii binutils 2.27-8 ii libc62.24-3 ii libc6-dev2.24-3 ii libclang-common-3.9-dev 1:3.9-1 ii libclang1-3.91:3.9-1 ii libgcc-6-dev 6.2.0-4 ii libgcc1 1:6.2.0-4 ii libjsoncpp1 1.7.4-3 ii libllvm3.9 1:3.9-1 ii libobjc-6-dev6.2.0-4 ii libstdc++-6-dev 6.2.0-4 ii libstdc++6 6.2.0-4 Versions of packages clang-3.9 recommends: ii llvm-3.9-dev 1:3.9-1 ii python2.7.11-2 Versions of packages clang-3.9 suggests: pn clang-3.9-doc pn gnustep pn gnustep-devel -- no debconf information
Bug#833295: BUG: unable to handle kernel NULL pointer dereference at gen6_ppgtt_insert_entries+0xc9/0x160
Package: src:linux Version: 4.6.4-1 Severity: normal Tags: upstream Hello, got this crash with kernel 4.6.3, no idea on how to reproduce. Aug 2 17:14:33 rieux kernel: [624938.589267] BUG: unable to handle kernel NULL pointer dereference at (null) Aug 2 17:14:33 rieux kernel: [624938.589310] IP: [] gen6_ppgtt_insert_entries+0xc9/0x160 [i915] Aug 2 17:14:33 rieux kernel: [624938.589376] PGD 1d5d67067 PUD 107361067 PMD 0 Aug 2 17:14:33 rieux kernel: [624938.589399] Oops: [#1] SMP Aug 2 17:14:33 rieux kernel: [624938.589415] Modules linked in: ufs(E) qnx4(E) hfsplus(E) hfs(E) minix(E) ntfs(E) vfat(E) msdos(E) fat(E) jfs(E) xfs(E) libcrc32c(E) dm_mod(E) cpuid(E) hmac(E) drbg(E) ansi_cprng (E) ctr(E) ccm(E) hid_generic(E) hid_roccat_koneplus(E) hid_roccat(E) hid_roccat_common(E) usbhid(E) hid(E) udf(E) crc_itu_t(E) loop(E) usb_serial_simple(E) usbserial(E) xt_addrtype(E) br_netfilter(E) ipt_MASQUE RADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_conntrack(E) nf_conntrack(E) xt_CHECKSUM(E) iptable_mangle(E) ipt_REJECT(E) nf_reject_ipv4(E) x t_tcpudp(E) overlay(E) tun(E) bridge(E) stp(E) llc(E) ebtable_filter(E) ebtables(E) ip6table_filter(E) ip6_tables(E) iptable_filter(E) ip_tables(E) x_tables(E) cpufreq_userspace(E) cpufreq_stats(E) cpufreq_conse rvative(E) cpufreq_powersave(E) bnep(E) fuse(E) snd_hda_codec_hdmi(E) binfmt_misc(E) arc4(E) iTCO_wdt(E) iTCO_vendor_support(E) intel_rapl(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) coretemp(E) kvm_intel(E) kvm(E) irqbypass(E) crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) uvcvideo(E) joydev(E) evdev(E) videobuf2_vmalloc(E) videobuf2_memops(E) videobuf2_v4l2(E) serio_raw(E) iwlmvm(E) pcspkr(E) mac80211( E) cdc_mbim(E) videobuf2_core(E) sg(E) videodev(E) media(E) cdc_wdm(E) iwlwifi(E) cdc_acm(E) cdc_ncm(E) btusb(E) usbnet(E) btrtl(E) rtsx_pci_ms(E) mii(E) btbcm(E) btintel(E) memstick(E) bluetooth(E) cfg80211(E) wmi(E) thinkpad_acpi(E) nvram(E) rfkill(E) ac(E) battery(E) snd_hda_codec_realtek(E) snd_hda_codec_generic(E) i915(E) snd_hda_intel(E) snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) snd_pcm(E) snd_timer(E) snd(E) soundcore(E) drm_kms_helper(E) video(E) drm(E) mei_me(E) i2c_algo_bit(E) mei(E) i2c_i801(E) lpc_ich(E) shpchp(E) tpm_tis(E) tpm(E) processor(E) button(E) parport_pc(E) ppdev(E) lp(E) parport(E) autofs4(E) ext4( E) ecb(E) crc16(E) jbd2(E) mbcache(E) btrfs(E) crc32c_generic(E) xor(E) raid6_pq(E) sd_mod(E) crc32c_intel(E) rtsx_pci_sdmmc(E) mmc_core(E) aesni_intel(E) aes_x86_64(E) glue_helper(E) lrw(E) gf128mul(E) ablk_hel per(E) cryptd(E) psmouse(E) rtsx_pci(E) mfd_core(E) ahci(E) libahci(E) libata(E) scsi_mod(E) ehci_pci(E) ehci_hcd(E) xhci_pci(E) xhci_hcd(E) e1000e(E) ptp(E) pps_core(E) usbcore(E) usb_common(E) thermal(E) fjes( E) Aug 2 17:14:33 rieux kernel: [624938.590189] CPU: 1 PID: 28204 Comm: vlc Tainted: GE 4.6.0-1-amd64 #1 Debian 4.6.3-1 Aug 2 17:14:33 rieux kernel: [624938.590211] Hardware name: LENOVO 20AQ007SIX/20AQ007SIX, BIOS GJET79WW (2.29 ) 09/03/2014 Aug 2 17:14:33 rieux kernel: [624938.590231] task: 8801d5d72180 ti: 8800a0cf8000 task.ti: 8800a0cf8000 Aug 2 17:14:33 rieux kernel: [624938.590249] RIP: 0010:[] [] gen6_ppgtt_insert_entries+0xc9/0x160 [i915] Aug 2 17:14:33 rieux kernel: [624938.590294] RSP: 0018:8800a0cfba20 EFLAGS: 00010246 Aug 2 17:14:33 rieux kernel: [624938.590308] RAX: RBX: RCX: Aug 2 17:14:33 rieux kernel: [624938.590325] RDX: 880036c4f160 RSI: 8800a9d32000 RDI: 8800a0cfba38 Aug 2 17:14:33 rieux kernel: [624938.590342] RBP: R08: R09: 880231512000 Aug 2 17:14:33 rieux kernel: [624938.590359] R10: R11: R12: 880231512000 Aug 2 17:14:33 rieux kernel: [624938.590375] R13: R14: 0001 R15: 8800a9d32ffc Aug 2 17:14:33 rieux kernel: [624938.590393] FS: 7fb7aff2f700() GS:88023e24() knlGS: Aug 2 17:14:33 rieux kernel: [624938.590412] CS: 0010 DS: ES: CR0: 80050033 Aug 2 17:14:33 rieux kernel: [624938.590426] CR2: CR3: 000234243000 CR4: 001406e0 Aug 2 17:14:33 rieux kernel: [624938.590443] Stack: Aug 2 17:14:33 rieux kernel: [624938.590448] 0200 8801d5d72180 02007bcadc60 880036c4f160 Aug 2 17:14:33 rieux kernel: [624938.590469] 0005 0001 503253b2 880036be0640 Aug 2 17:14:33 rieux kernel: [624938.590489] 8800a88abe80 0002 0001 Aug 2 17:14:33 rieux kernel: [624938.590510] Call Trace: Aug 2 17:14:33 rieux kernel: [624938.590529] [] ? aliasing_gtt_bind_vma+0x90/0xe0 [i915] Aug 2 17:14:33 rieux kernel: [624938.590556] [] ? i915_vma_bind+0xbb/0x160 [i915] Aug 2 17:14:33 rieux kernel: [624938.590582] [] ?
Bug#825818: gnome-terminal crash when dragging tab to another terminal
Hello Andreas Il 25/07/2016 19:53, Andreas Henriksson ha scritto: Hello Riccardo Magliocchetti. Thanks for your bug report. On Mon, May 30, 2016 at 12:10:04PM +0200, Riccardo Magliocchetti wrote: Package: gnome-terminal [...] When dragging a tab to another gnome-terminal instance, gnome-terminal crashes with the attached backtrace. [...] I've opened a bug report in the upstream bug tracker with a patch that fixes the issue for me, see above. Thanks! the patch is working fine for me too. -- Riccardo Magliocchetti
Bug#825909: firefox-esr: crash when loading videos
Package: firefox-esr
Version: 45.1.1esr-1+b1
Severity: grave
Justification: renders package unusable
Loading pages with videos (e.g. http://www.lastampa.it/multimedia/video) makes
firefox-esr crash with the attached backtrace.
Problem is it happens with embedded video too (ads maybe?) so you can't ust
avoid video specific urls.
-- Package-specific info:
-- Extensions information
Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: user-disabled
Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled
Name: FireTray
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{9533f794-00b4-4354-aa15-c2bbda6989f8}
Package: xul-ext-firetray
Status: user-disabled
Name: Italiano (IT) Language Pack locale
Location:
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-it
Status: enabled
Name: MeasureIt
Location: ${PROFILE_EXTENSIONS}/{75CEEE46-9B64-46f8-94BF-54012DE155F0}.xpi
Status: user-disabled
Name: Rai Smooth Streaming Player(raismth)
Location: ${PROFILE_EXTENSIONS}/rais...@mitm.rc.xpi
Status: user-disabled
Name: RESTClient
Location: ${PROFILE_EXTENSIONS}/{ad0d925d-88f8-47f1-85ea-8463569e756e}.xpi
Status: enabled
Name: Tema predefinito theme
Location:
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled
Name: User Agent Switcher
Location: ${PROFILE_EXTENSIONS}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}.xpi
Status: enabled
Name: Wappalyzer
Location: ${PROFILE_EXTENSIONS}/wappaly...@crunchlabz.com.xpi
Status: user-disabled
Name: YouTube HTML5 Switch
Location: ${PROFILE_EXTENSIONS}/jid0-cocuq7nysnpcj72da3557kkx...@jetpack.xpi
Status: enabled
Name: YSlow
Location: ${PROFILE_EXTENSIONS}/ys...@yahoo-inc.com.xpi
Status: user-disabled
-- Plugins information
Name: GNOME Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled
-- Addons package information
ii firefox-esr 45.1.1esr-1+b1 amd64Mozilla Firefox web browser
- Extended Support Release (ESR)
ii firefox-esr-l10n-it 45.1.1esr-1all Italian language package
for Firefox ESR
ii gnome-shell 3.20.2-1 amd64graphical shell for the
GNOME desktop
ii xul-ext-firetray0.6.1+dfsg-1 all system tray extension for
Firefox, Thunderbird, etc.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox-esr depends on:
ii debianutils 4.7
ii fontconfig2.11.0-6.4
ii libasound21.1.0-1
ii libatk1.0-0 2.20.0-1
ii libc6 2.22-7
ii libcairo2 1.14.6-1+b1
ii libdbus-1-3 1.10.8-1
ii libdbus-glib-1-2 0.106-1
ii libevent-2.0-52.0.21-stable-2+b1
ii libffi6 3.2.1-4
ii libfontconfig12.11.0-6.4
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6-20160117-1
ii libgdk-pixbuf2.0-02.34.0-1
ii libglib2.0-0 2.48.1-1
ii libgtk2.0-0 2.24.30-2
ii libhunspell-1.4-0 1.4.1-2
ii libnspr4 2:4.12-2
ii libnss3 2:3.23-2
ii libpango-1.0-01.40.1-1
ii libsqlite3-0 3.13.0-1
ii libstartup-notification0 0.12-4
ii libstdc++65.3.1-14
ii libvpx3 1.5.0-3
ii libx11-6 2:1.6.3-1
ii libxcomposite11:0.4.4-1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes31:5.0.1-2+b2
ii libxrender1 1:0.9.9-2
ii libxt61:1.1.5-1
ii procps2:3.3.11-3
ii zlib1g1:1.2.8.dfsg-2+b1
Versions of packages firefox-esr recommends:
ii gstreamer1.0-libav 1.8.1-1
ii gstreamer1.0-plugins-good 1.8.1-1
Versions of packages firefox-esr suggests:
ii fonts-lmodern 2.004.5-3
pn fonts-stix | otf-stix
ii libcanberra0 0.30-3
ii libgnomeui-0 2.24.5-3.1
ii libgssapi-krb5-2 1.14.2+dfsg-1
pn mozplugger
-- no debconf information
#0 0x55cad8c4d414 in mozalloc_abort(char const*)
(msg=msg@entry=0x7157c6ac "[26391] ###!!! ABORT: X_GLXDestroyPixmap:
GLXBadPixmap; 2 requests ago: file
/build/firefox-esr-PVtIUB/firefox-esr-45.1.1esr/toolkit/xre/nsX11ErrorHandler.cpp,
line 157")
at
/build/firefox-esr-PVtIUB/firefox-esr-45.1.1esr/memory/mozalloc/mozalloc_abort.cpp:33
#1 0x7f576e168bbf in
Bug#825818: gnome-terminal crash when dragging tab to another terminal
Package: gnome-terminal
Version: 3.20.2-1
Severity: important
When dragging a tab to another gnome-terminal instance, gnome-terminal crashes
with the
attached backtrace.
Thanks in advance
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-terminal depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii gconf-service3.2.6-3
ii gnome-terminal-data 3.20.2-1
ii gsettings-desktop-schemas3.20.0-3
ii libatk1.0-0 2.20.0-1
ii libc62.22-7
ii libcairo-gobject21.14.6-1+b1
ii libcairo21.14.6-1+b1
ii libdconf10.26.0-1
ii libgconf-2-4 3.2.6-3
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-1
ii libgtk-3-0 3.20.5-4
ii libnautilus-extension1a 3.20.1-2
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii libuuid1 2.28-5
ii libvte-2.91-00.44.2-1
ii libx11-6 2:1.6.3-1
Versions of packages gnome-terminal recommends:
ii dbus-x11 1.10.8-1
ii gvfs 1.28.2-1
ii yelp 3.20.1-1
gnome-terminal suggests no packages.
#0 0x7fd990a31478 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
resultvar = 0
pid = 28496
selftid = 28496
#1 0x7fd990a328fa in __GI_abort () at abort.c:89
save_stage = 2
act =
{__sigaction_handler = {sa_handler = 0x23fe130, sa_sigaction =
0x23fe130}, sa_mask = {__val = {133, 140572422390496, 140572450193520,
140732230515520, 72057594037927936, 16777216, 9511602413006487552,
140572601876480, 140572442725768, 37740848, 140569984630785, 0, 37740981,
140572414823288, 0, 140572414823200}}, sa_flags = 0, sa_restorer = 0x90}
sigs = {__val = {32, 0 }}
#2 0x7fd991233d75 in g_assertion_message
(domain=domain@entry=0x7fd9927ba2c7 "Gtk", file=file@entry=0x7fd992838d88
"/build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtkwidget.c", line=line@entry=5804,
func=func@entry=0x7fd99283ca10 <__func__.63114> "gtk_widget_get_frame_clock",
message=message@entry=0x1e7bee0 "assertion failed: (window != NULL)") at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gtestutils.c:2429
lstr =
"5804\000\177\000\000\000\257\203\340?_\366\215\032.Q\221\331\177\000\000r\034\203\222\331\177\000"
s = 0x23fe130
"Gtk:ERROR:/build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtkwidget.c:5804:gtk_widget_get_frame_clock:
assertion failed: (window != NULL)"
#3 0x7fd991233e0a in g_assertion_message_expr
(domain=domain@entry=0x7fd9927ba2c7 "Gtk", file=file@entry=0x7fd992838d88
"/build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtkwidget.c", line=line@entry=5804,
func=func@entry=0x7fd99283ca10 <__func__.63114> "gtk_widget_get_frame_clock",
expr=expr@entry=0x7fd992831c72 "window != NULL") at
/build/glib2.0-wnDt2X/glib2.0-2.48.1/./glib/gtestutils.c:2452
s = 0x1e7bee0 "assertion failed: (window != NULL)"
#4 0x7fd99276f00e in gtk_widget_get_frame_clock
(widget=widget@entry=0x21068c0 [TerminalTabLabel]) at
/build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtkwidget.c:5804
__func__ = "gtk_widget_get_frame_clock"
#5 0x7fd992774977 in gtk_widget_unrealize (widget=0x21068c0
[TerminalTabLabel]) at
/build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtkwidget.c:5511
__func__ = "gtk_widget_unrealize"
#6 0x7fd99278032d in gtk_widget_unparent (widget=0x21068c0
[TerminalTabLabel]) at
/build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtkwidget.c:4621
priv = 0x21067e0
nqueue = 0x1e41d80
toplevel =
old_parent =
__func__ = "gtk_widget_unparent"
#7 0x7fd992659e97 in gtk_notebook_remove_tab_label
(notebook=notebook@entry=0x1efe200 [TerminalNotebook], page=0x234f8f0,
page=0x234f8f0) at /build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtknotebook.c:4987
#8 0x7fd99265a044 in gtk_notebook_remove (list=0x1e49320,
notebook=0x1efe200 [TerminalNotebook]) at
/build/gtk+3.0-29jmON/gtk+3.0-3.20.5/./gtk/gtknotebook.c:5058
need_resize = 1
destroying = 0
priv = 0x1efe010
page = 0x234f8f0
next_list =
tab_label = 0x21068c0 [TerminalTabLabel]
notebook = 0x1efe200 [TerminalNotebook]
priv =
page =
Bug#824390: Bug solved after upgrade
It looks like the problem was related to some incompatibility issue with a previous version of some library (libecal-1.2 is my guess). -- Saluti, Riccardo
Bug#824390: gnome-shell-calendar-server gets SegFault after stack smashing detected
Package: gnome-shell Version: 3.20.2-1 Severity: normal After the last upgrade (from version 3.18) I noticed an high CPU utilization for gnome.shell. This seems to be related to the process gnome-shell-calendar-server crashing and being restarted continuously. Running the process within a debugger provides this output: (gdb) run Starting program: /usr/lib/gnome-shell/gnome-shell-calendar-server [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffef4c7700 (LWP 5487)] [New Thread 0x7fffeecc6700 (LWP 5489)] [New Thread 0x7fffee4c5700 (LWP 5490)] [New Thread 0x7fffedab7700 (LWP 5494)] [New Thread 0x7fffed2b6700 (LWP 5495)] (gnome-shell-calendar-server:5424): e-data-server-CRITICAL **: ESourceRegistry: Failed to create a data source object for path '/org/gnome/evolution/dataserver/SourceManager/Source_3': Source file is missing a [Data Source] group [New Thread 0x7fffd75b0700 (LWP 5506)] *** stack smashing detected ***: /usr/lib/gnome-shell/gnome-shell-calendar-server terminated Program received signal SIGSEGV, Segmentation fault. 0x73a08d1b in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1 The backtrace is: (gdb) bt #0 0x73a08d1b in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1 #1 0x73a0a6b8 in _Unwind_Backtrace () from /lib/x86_64-linux-gnu/libgcc_s.so.1 #2 0x7603ed96 in __GI___backtrace (array=array@entry=0x7fffc5c0, size=size@entry=64) at ../sysdeps/x86_64/backtrace.c:109 #3 0x75f68875 in backtrace_and_maps (do_abort=, do_abort@entry=2, written=, fd=fd@entry=9) at ../sysdeps/unix/sysv/linux/libc_fatal.c:47 #4 0x75fbafe5 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x760b0d11 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:172 #5 0x76042357 in __GI___fortify_fail ( msg=msg@entry=0x760b0cf9 "stack smashing detected") at fortify_fail.c:31 #6 0x76042320 in __stack_chk_fail () at stack_chk_fail.c:28 #7 0x7738a5f7 in e_cal_recur_ensure_rule_end_date ( comp=, prop=0x711180, exception=, refresh=0, tz_cb=0x404f20, tz_cb_data=0x7fffdc02df80) at e-cal-recur.c:3933 #8 0x7f7f7f7f7f7f7f7f in ?? () #9 0x7f7f7f7f7f7f7f7f in ?? () #10 0x7f7f7f7f7f7f7f7f in ?? () #11 0x7f7f7f7f7f7f7f7f in ?? () #12 0x7f7f7f7f7f7f7f7f in ?? () (But due to probable stack corruption and lack of debugging symbols I don't think this so meaningful) I can provide also a core dump, if needed. The warning about the missing data source object is a warning due to my evolution configuration being very old (some glitch in an upgrade back in gnome2 i think) but it never led to probems. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1 ii evolution-data-server3.18.5-1 ii gir1.2-accountsservice-1.0 0.6.40-3 ii gir1.2-atspi-2.0 2.20.1-1 ii gir1.2-caribou-1.0 0.4.20-1 ii gir1.2-clutter-1.0 1.26.0-2 ii gir1.2-freedesktop 1.48.0-2 ii gir1.2-gcr-3 3.20.0-2 ii gir1.2-gdesktopenums-3.0 3.20.0-3 ii gir1.2-gdm-1.0 3.20.1-1 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.48.0-2 ii gir1.2-gnomebluetooth-1.03.18.3-1 ii gir1.2-gnomedesktop-3.0 3.20.2-1 ii gir1.2-gtk-3.0 3.20.4-1 ii gir1.2-gweather-3.0 3.20.0-1 ii gir1.2-ibus-1.0 1.5.11-1 ii gir1.2-mutter-3.03.20.2-1 ii gir1.2-networkmanager-1.01.2.0-1 ii gir1.2-nmgtk-1.0 1.2.0-2 ii gir1.2-pango-1.0 1.40.1-1 ii gir1.2-polkit-1.00.105-15 ii gir1.2-soup-2.4 2.54.1-1 ii gir1.2-telepathyglib-0.120.24.1-1.1 ii gir1.2-telepathylogger-0.2 0.8.2-1 ii gir1.2-upowerglib-1.00.99.4-2 ii gjs 1.45.3-2 ii gnome-backgrounds3.20-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.20.1-1 ii gnome-shell-common 3.20.2-1 ii
Bug#811592: fixed upstream
Hello, this has been fixed upstream in the uwsgi-2.0 branch as commit 56de2057b2bc7016b69615e6e8cb61dd255f3dca https://github.com/unbit/uwsgi/commit/56de2057b2bc7016b69615e6e8cb61dd255f3dca thanks for reporting -- Riccardo Magliocchetti @rmistaken http://menodizero.it
Bug#803063: [libapache2-mod-fastcgi] missing libtool-bin build depend
Package: libapache2-mod-fastcgi Version: 2.4.7~0910052141 Severity: important --- Please enter the report below this line. --- debuild does not work because of missing libtool, installing libtool-bin fixed the build for me: make[1]: Entering directory '/home/rm/src/libapache-mod-fastcgi-2.4.7~0910052141/build-tmp/20' libtool --tag=CC --mode=compile arm-linux-gnueabihf-gcc -std=gnu99 -pthread -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -DLINUX -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_FORTIFY_SOURCE=2 -I/usr/include/apache2 -DLINUX -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/usr/include/apr-1.0 -I/usr/include/apache2 -I. -I/usr/include/apr-1.0 -I/usr/include -prefer-pic -c mod_fastcgi.c && touch mod_fastcgi.slo /bin/bash: libtool: command not found /usr/share/apache2/build/rules.mk:212: recipe for target 'mod_fastcgi.slo' failed --- System information. --- Architecture: amd64 Kernel: Linux 4.2.0-1-amd64 Debian Release: stretch/sid 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Riccardo Magliocchetti @rmistaken http://menodizero.it
Bug#796832: pandoc generating bibliography issue
Package: pandoc
Version: 1.12.4.2
I would try to convert the way I write my scientific articles from
Sweave/LaTeX to knitr/pandoc.
I've been able to reproduce almost everithing with the exceptions of the
references.
I googled a lot and I read the official and unofficial guide to the
pandoc references but I've not
yet found the right solution to my problem: no citations are included in
my document.
This is what I've done:
added bibliography: myBib.bib to the header of the file
added the citation using [@KEY], where KEY is the key entry in my
.bib file
added # References section at the bottom of my document
convert .Rmd file to .md file using knitr
from shell I run:
pandoc -H headers.tex --bibliography=myBib.bib -o article.pdf
article.md
The .pdf file was generated but with non citation references
I've also tried to generate the .tex file and then to compile it
pandoc --bibliography=myBib.bib -o article.tex article.md
also using the --natbib and --biblatex switch, but nothing changes.
Opening the .tex file I noticed that the citations were converted as:
{[}@01, @46{]}
while in the .md file I wrote: [@01, @46].
I installed pandoc (1.15.0.6) and pandoc-citeproc from source and all
seems to work properly.
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages pandoc depends on:
ii libc62.19-18
ii libffi6 3.1-2+b2
ii libgmp10 2:6.0.0+dfsg-6
ii libicu52 52.1-8+deb8u2
ii liblua5.1-0 5.1.5-7.1
ii libpcre3 2:8.35-3.3
ii libyaml-0-2 0.1.6-3
ii pandoc-data 1.12.4.2~dfsg-1
ii zlib1g 1:1.2.8.dfsg-2+b1
pandoc recommends no packages.
Versions of packages pandoc suggests:
pn etoolbox none
ii pandoc-citeproc0.4.0.1-1
ii texlive-latex-recommended 2014.20141024-2
ii texlive-luatex 2014.20141024-2
ii texlive-xetex 2014.20141024-2
-- no debconf information
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Riccardo ric.rom...@gmail.com
To: Debian Bug Tracking System 700...@bugs.debian.org
Subject: pandoc generating bibliography issue
Message-ID: 20150824175846.29380.79392.reportbug@mb
X-Mailer: reportbug 6.6.3
Date: Mon, 24 Aug 2015 19:58:46 +0200
X-Debbugs-Cc: ric.rom...@gmail.com
Package: pandoc
Followup-For: Bug #700329
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
I would try to convert the way I write my scientific articles from Sweave/LaTeX
to knitr/pandoc.
I've been able to reproduce almost everithing with the exceptions of the
references.
I googled a lot and I read the official and unofficial guide to the pandoc
references but I've not
yet found the right solution to my problem: no citations are included in my
document.
This is what I've done:
added bibliography: myBib.bib to the header of the file
added the citation using [@KEY], where KEY is the key entry in my .bib file
added # References section at the bottom of my document
convert .Rmd file to .md file using knitr
from shell I run:
pandoc -H headers.tex --bibliography=myBib.bib -o article.pdf article.md
The .pdf file was generated but with non citation references
I've also tried to generate the .tex file and then to compile it
pandoc --bibliography=myBib.bib -o article.tex article.md
also using the --natbib and --biblatex switch, but nothing changes.
Opening the .tex file I noticed that the citations were converted as: {[}@01,
@46{]}
while in the .md file I wrote: [@01, @46].
I installed pandoc and pandoc-citeproc from source and all seems to work
properly.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages pandoc depends on:
ii libc62.19-18
ii libffi6 3.1-2+b2
ii libgmp10 2:6.0.0+dfsg-6
ii libicu52 52.1-8+deb8u2
ii liblua5.1-0 5.1.5-7.1
ii libpcre3 2:8.35-3.3
ii libyaml-0-2 0.1.6-3
ii pandoc-data 1.12.4.2~dfsg-1
ii zlib1g 1:1.2.8.dfsg-2+b1
pandoc recommends no packages.
Versions of packages
Bug#787323: gthumb: Memory leaks with freehand rotations
On Sun, May 31, 2015 at 4:19 PM, Herbert Parentes Fortes Neto h...@ig.com.br wrote: How did you monitored the mem usage ? Did you use the [arrows at the top] ? Can you test the version in 'testing' ? No, the issue is with the freehand rotation: http://imgur.com/Lw2jgNv Trying it with version 3:3.4.0-2 and appropriate updates of all dependencies to the version current in stretch, the bug is still present: in fact, immediately after clicking the button in the previous screenshot, the image size in pixels changes to a ridiculously high size, which may be connected to this issue: http://imgur.com/Cmgfuhd Example of leak after rotating about 20 seventeen megapixel images: http://imgur.com/yMTP5aV This may likely be an upstream bug, as I recall it happening on another OS (not sure whether it was Arch Linux or a still-in-testing Jessie) a few months ago...
Bug#787323: gthumb: Memory leaks with freehand rotations
Package: gthumb Version: 3:3.3.1-2+b2 Severity: important While using gthumb's editor mode in a way typical of correcting newly taken images, mainly involving: -freehand rotation -cropping -selecting the next photo and agreeing to save changes gthumb's memory footprint will increase for every image rotated, if not closed at strategic intervals. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gthumb depends on: ii gsettings-desktop-schemas 3.14.1-1 ii gthumb-data 3:3.3.1-2 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libexiv2-13 0.24-4.1 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgstreamer-plugins-base1.0-0 1.4.4-2 ii libgstreamer1.0-0 1.4.4-2 ii libgtk-3-0 3.14.5-1 ii libjavascriptcoregtk-3.0-0 2.4.8-2 ii libjpeg62-turbo 1:1.3.1-12 ii libjson-glib-1.0-0 1.0.2-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpng12-0 1.2.50-2+b2 ii librsvg2-2 2.40.5-1 ii libsecret-1-0 0.18-1+b1 ii libsoup2.4-12.48.0-1 ii libstdc++6 4.9.2-10 ii libtiff54.0.3-12.3 ii libwebkit2gtk-3.0-252.4.8-2 ii libwebp50.4.1-1.2+b2 ii multiarch-support 2.19-18 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages gthumb recommends: pn bison none pn flexnone ii gstreamer0.10-gnomevfs 0.10.36-2 ii gvfs-bin1.22.2-1 gthumb suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774594: [ruby-libvirt] Please package 0.5.2
Package: ruby-libvirt Version: 0.5.1-3+b1 Severity: wishlist --- Please enter the report below this line. --- Hello, it would be nice to have latest upstream version 0.5.2 packaged as it is requested by vagrant kvm plugin. thanks in advance --- System information. --- Architecture: amd64 Kernel: Linux 3.16.0-4-amd64 Debian Release: 8.0 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773396: codelite: Can't run programs (Could not launch terminal for debugger)
Package: codelite Version: 6.1.1+dfsg-4 Severity: important After installing CodeLite on a brand new Jessie system with MATE, I am experiencing the same problem that occurred on a comparable well-used in late September: 1: Open any project (tested with a new GCC console program template). 2: Click the Play (run in debug mode) button. 3: An error window pops up, stating Could not launch terminal for debugger. This condition of failure is independent of which terminal emulator(s) are installed -- with the package recommending any, but upstream specifying xterm -- and any of the Settings Global Editor Terminal options. After discussing the issue in CodeLite's IRC channel the first time I noticed the problem, the developer came to a conclusion that the Debian package was significantly different from what he made (I also downloaded the source package and shown him some included patches that I found as relevant to the issue, with no conclusive results from the discussion that followed). Installing the upstream package from http://codelite.org/LiteEditor/Repositories#toc1 (designed, however, for Wheezy) appears to be the only immediate solution. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages codelite depends on: ii libc6 2.19-13 ii libclang1-3.5 1:3.5-8 ii libgcc1 1:4.9.1-19 ii libglib2.0-02.42.1-1 ii libgtk2.0-0 2.24.25-1 ii libssh-gcrypt-4 0.6.3-3+b1 ii libstdc++6 4.9.1-19 ii libwxbase3.0-0 3.0.2-1+b1 ii libwxgtk3.0-0 3.0.2-1+b1 ii libwxsqlite3-3.0-0 3.1.1~dfsg1-1 Versions of packages codelite recommends: ii g++ 4:4.9.1-5 ii gcc 4:4.9.1-5 ii gdb 7.7.1+dfsg-5 ii mate-terminal [x-terminal-emulator] 1.8.1+dfsg1-3 ii wx-common3.0.2-1+b1 ii xterm [x-terminal-emulator] 312-1 Versions of packages codelite suggests: ii codelite-plugins 6.1.1+dfsg-4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770933: [mdbtools] Please update homepage in package description
Package: mdbtools Version: 0.7.1-2 Severity: minor --- Please enter the report below this line. --- The package description should be updated to reference https://github.com/brianb/mdbtools instead of the sourceforge homepage. --- System information. --- Architecture: i386 Kernel: Linux 3.16.6 Debian Release: jessie/sid 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754854: [uwsgi] patch 1005 should not be needed
Il 05/11/2014 21:29, Jonas Smedegaard ha scritto: Hi Riccardo, Quoting Riccardo Magliocchetti (2014-11-05 16:56:45) Il 27/10/2014 17:44, Riccardo Magliocchetti ha scritto: Il 25/10/2014 21:28, Jonas Smedegaard ha scritto: Riccardo Magliocchetti wrote: Patch 1005_emperor-pg-fix-cflags.patch should have been already fixed upstream in 7c31b6657ffdbbbe566822fbcdb6cf2eb4b44026 so could be removed. Indeed that upstream commit look quite related, but removing patch 1005 cause the build to fail - just tried for 2.0.7-1. Help investigating what is going on here is appreciated. Looks like the saner option would be to remove the build hack that was added for unknown reason, see: https://github.com/unbit/uwsgi/pull/759 A more conservative patch has been applied to master, so it would be nice if you can substitute 1005 with [1]. If that works fine for you i'll ask to have it backported to 2.0.x so you can drop it. Thanks for trying - unfortunately it fails: plugins/systemd_logger/systemd_logger.c: In function 'uwsgi_systemd_logger': plugins/systemd_logger/systemd_logger.c:13:4: error: format not a string literal and no format arguments [-Werror=format-security] sd_journal_print(LOG_INFO, base); ^ cc1: all warnings being treated as errors using profile: debian/buildconf/uwsgi-plugin.ini detected include path: ['/usr/lib/gcc/x86_64-linux-gnu/4.9/include', '/usr/local/include', '/usr/lib/gcc/x86_64-linux-gnu/4.9/include-fixed', '/usr/include/x86_64-linux-gnu', '/usr/include'] *** uWSGI building and linking plugin plugins/systemd_logger *** x86_64-linux-gnu-gcc -pthread -fPIC -shared -o ./systemd_logger_plugin.so -I. -O2 -I. -Wall -Werror -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -DUWSGI_HAS_IFADDRS -DUWSGI_ZLIB -DUWSGI_LOCK_USE_MUTEX -DUWSGI_EVENT_USE_EPOLL -DUWSGI_EVENT_TIMER_USE_TIMERFD -DUWSGI_EVENT_FILEMONITOR_USE_INOTIFY -DUWSGI_PCRE -DUWSGI_ROUTING -DUWSGI_CAP -DUWSGI_UUID -DUWSGI_VERSION=\2.0.8-debian\ -DUWSGI_VERSION_BASE=2 -DUWSGI_VERSION_MAJOR=0 -DUWSGI_VERSION_MINOR=8 -DUWSGI_VERSION_REVISION=0 -DUWSGI_VERSION_CUSTOM=\debian\ -DUWSGI_YAML -DUWSGI_LIBYAML -DUWSGI_JSON -DUWSGI_SSL -I/usr/include/libxml2 -DUWSGI_XML -DUWSGI_XML_LIBXML2 -DUWSGI_PLUGIN_DIR=\.\ -Dsystemd_logger_plugin=systemd_logger_plugin plugins/systemd_logger/systemd_logger.c -Wl,-z,relro -lsystemd *** unable to build systemd_logger plugin *** Fixed in: https://github.com/unbit/uwsgi/commit/3406441d9585026cdfeb2d0bc979ad9bf527824d I've compiled all plugins in master branch so it should be fine in 2.0.x too. Let me know otherwise. If everything is fine i'll backport the uwsgiconfig.py patch so with 2.0.9 hopefully we can drop both patches. thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754854: [uwsgi] patch 1005 should not be needed
Il 27/10/2014 17:44, Riccardo Magliocchetti ha scritto: Hello, Il 25/10/2014 21:28, Jonas Smedegaard ha scritto: Hi, Riccardo Magliocchetti wrote: Patch 1005_emperor-pg-fix-cflags.patch should have been already fixed upstream in 7c31b6657ffdbbbe566822fbcdb6cf2eb4b44026 so could be removed. Indeed that upstream commit look quite related, but removing patch 1005 cause the build to fail - just tried for 2.0.7-1. Help investigating what is going on here is appreciated. Looks like the saner option would be to remove the build hack that was added for unknown reason, see: https://github.com/unbit/uwsgi/pull/759 A more conservative patch has been applied to master, so it would be nice if you can substitute 1005 with [1]. If that works fine for you i'll ask to have it backported to 2.0.x so you can drop it. [1] https://github.com/unbit/uwsgi/commit/35acf3793d9c586c366d6d9b2b9f9f124f302060 thanks -- Riccardo Magliocchetti -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767471: [initramfs-tools] / formatted as ext3 but mounted as ext4 not fsck-able
Package: initramfs-tools Version: 0.118 Severity: normal --- Please enter the report below this line. --- I have a ext3 formatted / which in /etc/fstab is mounted with ext4. This does not cope well with the logic in hooks/fsck which assumes that fsck.$fs will work with a filesystem entry $fs in /etc/fstab. So at boot the initramfs warns that fsck.ext3 is missing and cannot do the check on /. This may not be a common case but still a fsck error or warning at boot for / it's annoying. I've attached an untested patch with a tentative fix. --- System information. --- Architecture: i386 Kernel: Linux 3.16.6 Debian Release: jessie/sid 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+- klibc-utils (= 2.0-1~) | 2.0.4-2 cpio | 2.11+dfsg-2 kmod | 18-3 OR module-init-tools | 18-3 udev | 215-5+b1 Recommends (Version) | Installed -+-=== busybox (= 1:1.01-3) | 1:1.22.0-9 OR busybox-initramfs| OR busybox-static | Suggests (Version) | Installed ==-+-=== bash-completion| --- Output from package bug script --- -- initramfs sizes -rw-r--r-- 1 root root 4,9M ago 13 12:02 /boot/initrd.img-3.14.16 -rw-r--r-- 1 root root 4,9M ott 6 12:07 /boot/initrd.img-3.16.4 -rw-r--r-- 1 root root 5,4M ott 27 11:39 /boot/initrd.img-3.16.5 -rw-r--r-- 1 root root 4,7M ott 28 11:31 /boot/initrd.img-3.16.6 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.6 root=UUID=770e4e60-f57b-4299-a18d-ed558a68d750 ro quiet acpi_backlight=vendor -- resume RESUME=/dev/sda3 -- /proc/filesystems ext3 ext2 ext4 fuseblk -- lsmod Module Size Used by dm_mod 79494 0 iptable_filter 1762 0 ip_tables 15195 1 iptable_filter x_tables 21829 2 ip_tables,iptable_filter ctr 3857 1 ccm 7451 1 cpufreq_stats 3136 0 bnep 10410 2 bluetooth 241284 5 bnep uinput 7665 1 ipv6 316592 26 cuse6277 0 fuse 75002 2 cuse joydev 8792 0 loop 17367 0 uvcvideo 64359 0 videobuf2_vmalloc 2968 1 uvcvideo videobuf2_memops2410 1 videobuf2_vmalloc videobuf2_core 25764 1 uvcvideo v4l2_common 6110 1 videobuf2_core videodev 129098 3 uvcvideo,v4l2_common,videobuf2_core i915 797927 3 fbcon 34821 71 bitblit 4640 1 fbcon iTCO_wdt5736 0 softcursor 1349 1 bitblit arc42072 2 sdhci_pci 11598 0 iwldvm110824 0 mac80211 450072 1 iwldvm cfbfillrect 3317 1 i915 cfbimgblt 2296 1 i915 i2c_algo_bit5374 1 i915 sdhci 24389 1 sdhci_pci snd_hda_codec_hdmi 34683 2 mmc_core 97042 1 sdhci snd_hda_codec_realtek58964 1 snd_hda_codec_generic48330 1 snd_hda_codec_realtek pcspkr 2054 0 font8131 1 fbcon tileblit2239 1 fbcon samsung_laptop 9075 0 coretemp5905 0 cfbcopyarea 3017 1 i915 psmouse59351 0 e1000e147839 0 evdev 10197 23 snd_hda_intel 20239 6 iwlwifi88968 1 iwldvm snd_hda_controller 20981 1 snd_hda_intel snd_hda_codec 115704 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller yenta_socket 20471 0 pcmcia_rsrc 1301 1 yenta_socket cfg80211 464686 3 iwlwifi,mac80211,iwldvm snd_hwdep 6187 1 snd_hda_codec pcmcia_core15627 1 yenta_socket snd_pcm86549 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller serio_raw 4666 0 drm_kms_helper 41936 1 i915 lpc_ich13821 0 drm 276323 5 i915,drm_kms_helper mfd_core3603 1 lpc_ich snd_timer 19153 1 snd_pcm thermal 9844 0 i2c_i8019223 0 i2c_core 43251 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev battery10068 0 fan 2914 0 acpi_cpufreq7317 1 snd66690 20 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
Bug#754854: [uwsgi] patch 1005 should not be needed
Hello, Il 25/10/2014 21:28, Jonas Smedegaard ha scritto: Hi, Riccardo Magliocchetti wrote: Patch 1005_emperor-pg-fix-cflags.patch should have been already fixed upstream in 7c31b6657ffdbbbe566822fbcdb6cf2eb4b44026 so could be removed. Indeed that upstream commit look quite related, but removing patch 1005 cause the build to fail - just tried for 2.0.7-1. Help investigating what is going on here is appreciated. Looks like the saner option would be to remove the build hack that was added for unknown reason, see: https://github.com/unbit/uwsgi/pull/759 I've built uwsgi debian package git master nicely on ia32 with that patch. Asked to be backported to 2.0 too. thanks -- Riccardo Magliocchetti -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765528: chromium: Warnings while installing package from scratch
Package: chromium Version: 38.0.2125.101-2 Severity: minor Trying to install this package from a never-installed (including purged) state generates multiple dpkg errors. It does not however influence the result, which ends with the package properly configured and working (notwithstanding other current bugs). riki@kawoshin:~$ sudo LC_ALL=C aptitude install chromium The following NEW packages will be installed: chromium 0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/36.9 MB of archives. After unpacking 144 MB will be used. Selecting previously unselected package chromium. (Reading database ... 141823 files and directories currently installed.) Preparing to unpack .../chromium_38.0.2125.101-2_amd64.deb ... dpkg: error: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! dpkg: error: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! dpkg: error: --compare-versions takes three arguments: version relation version Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! Unpacking chromium (38.0.2125.101-2) ... Processing triggers for man-db (2.7.0.2-1) ... Processing triggers for mime-support (3.57) ... Processing triggers for desktop-file-utils (0.22-1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii libasound2 1.0.28-1 ii libc62.19-11 ii libcairo21.12.16-5 ii libcap2 1:2.24-6 ii libcups2 1.7.5-4 ii libdbus-1-3 1.8.8-1+b1 ii libexpat12.1.0-6 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.30.8-1+b1 ii libglib2.0-0 2.42.0-2 ii libgnome-keyring03.12.0-1 ii libgtk2.0-0 2.24.24-1 ii libharfbuzz0b0.9.35-1 ii libjpeg8 8d1-1 ii libnspr4 2:4.10.7-1 ii libnss3 2:3.17.1-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpci3 1:3.2.1-3 ii libspeechd2 0.8-6 ii libspeex11.2~rc1.2-1 ii libsrtp0 1.4.5~20130609~dfsg-1 ii libstdc++6 4.9.1-16 ii libudev1 215-5+b1 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1 ii libxdamage1 1:1.1.4-2 ii libxext6 2:1.3.2-1 ii libxfixes3 1:5.0.1-2 ii libxi6 2:1.7.4-1 ii libxml2 2.9.1+dfsg1-4 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii libxslt1.1 1.1.28-2+b1 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.2-1 ii xdg-utils1.1.0~rc1+git20111210-7.1 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-inspector none pn chromium-l10n none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764921: [docker.io] broken upgrade with stale pidfile
Package: docker.io Version: 1.2.0~dfsg1-1 Severity: normal --- Please enter the report below this line. --- It looks like upgrade breaks if there's a stale pidfile and docker is not running: (Reading database ... 364101 files and directories currently installed.) Preparing to unpack .../docker.io_1.2.0~dfsg1-2_i386.deb ... [] Stopping Docker: dockerstart-stop-daemon: warning: failed to kill 19512: No such process 1 pids were not killed No process in pidfile '/var/run/docker-ssd.pid' found running; none killed. invoke-rc.d: initscript docker, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... [] Stopping Docker: dockerstart-stop-daemon: warning: failed to kill 19512: No such process 1 pids were not killed No process in pidfile '/var/run/docker-ssd.pid' found running; none killed. invoke-rc.d: initscript docker, action stop failed. dpkg: error processing archive /var/cache/apt/archives/docker.io_1.2.0~dfsg1-2_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 1 dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/docker.io_1.2.0~dfsg1-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- System information. --- Architecture: i386 Kernel: Linux 3.14.16 Debian Release: jessie/sid 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764921: Acknowledgement ([docker.io] broken upgrade with stale pidfile)
Quick update: it also breaks with no pidfile and with an empty pidfile. thanks -- Riccardo Magliocchetti -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764073: xserver-xorg-input-synaptics: bcm5974 (Apple unibody trackpad) fails after extended idle
Although this report was about the first occurrence of an apparently random problem, it hasn't happened again in a week since rebooting to 3.16.3-2. On Sun, Oct 5, 2014 at 4:38 PM, maximilian attems m...@stro.at wrote: On Sun, Oct 05, 2014 at 02:43:23PM +0200, Julien Cristau wrote: Control: reassign -1 src:linux 3.14.15-2 Last night, I left my computer by turning down the screen brighness to zero and the keyboard's to about 20%. could you please reproduce on latest linux image 3.16.3-2? thanks. -- maks
Bug#764073: xserver-xorg-input-synaptics: bcm5974 (Apple unibody trackpad) fails after extended idle
Package: xserver-xorg-input-synaptics Version: 1.8.1-1 Severity: normal Last night, I left my computer by turning down the screen brighness to zero and the keyboard's to about 20%. When I increased them again this morning, the mouse cursor wouldn't move. I immediately tried touching the trackpad with the whole palm (an empirical fix for a problem I experienced while running my computer without battery where the cursor would stop moving after clicking), which didn't help. Removing and reloading the module fixed the problem; I'm not aware of this issue having ever repeated. selection of dmesg output follows: [455030.430023] JBD2: Error -5 detected when updating journal superblock for sdb1-8. [491747.172823] bcm5974: bad trackpad package, length: 8 [491747.180897] bcm5974: bad trackpad package, length: 8 [491747.187898] bcm5974: bad trackpad package, length: 8 [491747.196890] bcm5974: bad trackpad package, length: 8 [...] [491769.758147] bcm5974: bad trackpad package, length: 8 [491780.974885] usbcore: deregistering interface driver bcm5974 [491785.276737] input: bcm5974 as /devices/pci:00/:00:1a.7/usb3/3-1/3-1.2/3-1.2:1.2/input/input18 [491785.277028] usbcore: registered new interface driver bcm5974 -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Sep 24 11:18 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2397280 Sep 22 23:49 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.14-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 SMP Debian 3.14.15-2 (2014-08-09) Xorg X server log files on system: -- -rw-r--r-- 1 root root 47768 Oct 5 10:53 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [15.523] X.Org X Server 1.16.0.901 (1.16.1 RC 1) Release Date: 2014-09-15 [15.523] X Protocol Version 11, Revision 0 [15.523] Build Operating System: Linux 3.14-2-amd64 x86_64 Debian [15.524] Current Operating System: Linux kawoshin 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 [15.524] Kernel command line: initrd=\99ac1c5451ce3149296bcd315421df82\3.14-2-amd64\initrd root=UUID=ee979a81-454c-414c-a576-73dbdb7f7167 ro quiet [15.524] Build Date: 16 September 2014 02:45:53PM [15.524] xorg-server 2:1.16.0.901-1 (http://www.debian.org/support) [15.524] Current version of pixman: 0.32.6 [15.524]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [15.524] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [15.525] (==) Log file: /var/log/Xorg.0.log, Time: Wed Sep 24 11:20:57 2014 [15.526] (==) Using system config directory /usr/share/X11/xorg.conf.d [15.528] (==) No Layout section. Using the first Screen section. [15.528] (==) No screen section available. Using defaults. [15.528] (**) |--Screen Default Screen Section (0) [15.528] (**) | |--Monitor default monitor [15.528] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [15.528] (==) Automatically adding devices [15.528] (==) Automatically enabling devices [15.528] (==) Automatically adding GPU devices [15.530] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [15.530]Entry deleted from font path. [15.530] (WW) The directory /usr/share/fonts/X11/100dpi/ does not exist. [15.530]Entry deleted from font path. [15.530] (WW) The directory /usr/share/fonts/X11/75dpi/ does not exist. [15.530]Entry deleted from font path. [15.530] (WW) The directory /usr/share/fonts/X11/Type1 does not exist. [15.530]Entry deleted from font path. [15.530] (WW) The directory /usr/share/fonts/X11/100dpi does not exist. [15.530]Entry deleted from font path. [15.530] (WW) The directory /usr/share/fonts/X11/75dpi does not exist. [15.530]Entry deleted from font path. [15.530] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [15.530] (==) ModulePath set to /usr/lib/xorg/modules [15.530] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [15.530] (II) Loader magic: 0x7fcede59ad80 [
Bug#762080: [samba] log dir not created after purge and reinstall
Package: samba Version: 2:4.1.11+dfsg-1 Severity: normal --- Please enter the report below this line. --- how to reproduce: sudo apt-get install samba sudo dpkg --purge samba sudo apt-get install samba Then since /var/log/samba does not exist samba will print [2014/09/18 10:43:49.879102, 0] ../lib/util/debug.c:597(reopen_logs_internal) Unable to open new log file '/var/log/samba/log.smbd': File o directory non esistente [2014/09/18 10:43:49.879692, 0] ../lib/util/debug.c:597(reopen_logs_internal) Unable to open new log file '/var/log/samba/log.smbd': File o directory non esistente [2014/09/18 10:43:49.879768, 0] ../lib/util/debug.c:597(reopen_logs_internal) Unable to open new log file '/var/log/samba/log.smbd': File o directory non esistente --- System information. --- Architecture: i386 Kernel: Linux 3.14.16 Debian Release: jessie/sid 500 unstableftp.de.debian.org 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== adduser | 3.113+nmu3 heimdal-hdb-api-8 | libpam-modules| 1.1.8-3.1 libpam-runtime (= 1.0.1-11) | 1.1.8-3.1 lsb-base (= 4.1+Debian) | 4.1+Debian13 procps| 1:3.3.9-7 python (= 2.7) | 2.7.8-1 python-dnspython | 1.12.0-1 python-ntdb | 1.0-5 python-samba | 2:4.1.11+dfsg-1 samba-common (= 2:4.1.5+dfsg-1) | 2:4.1.11+dfsg-1 samba-common-bin (= 2:4.1.5+dfsg-1) | 2:4.1.11+dfsg-1 samba-dsdb-modules| 2:4.1.11+dfsg-1 tdb-tools | 1.3.0-1.1 update-inetd | 4.43 python ( 2.8) | 2.7.8-1 python2.7:any | libasn1-8-heimdal (= 1.4.0+git20110226) | 1.6~rc2+dfsg-8 libbsd0(= 0.5.0) | 0.7.0-2 libc6(= 2.8) | 2.19-11 libcomerr2 (= 1.01) | 1.42.12-1 libhdb9-heimdal(= 1.4.0+git20110226) | 1.6~rc2+dfsg-8 libkdc2-heimdal(= 1.4.0+git20110226) | 1.6~rc2+dfsg-8 libkrb5-26-heimdal (= 1.4.0+git20110226) | 1.6~rc2+dfsg-8 libldb1 (= 0.9.21) | 1:1.1.17-1 libpopt0(= 1.14) | 1.16-10 libpython2.7 (= 2.7) | 2.7.8-7 libroken18-heimdal (= 1.4.0+git20110226) | 1.6~rc2+dfsg-8 libtalloc2 (= 2.0.4~git20101213) | 2.1.1-2 libtdb1(= 1.2.7+git20101214) | 1.3.0-1.1 libtevent0(= 0.9.14) | 0.9.21-1 samba-libs (= 2:4.1.5+dfsg-1) | 2:4.1.11+dfsg-1 Recommends (Version) | Installed -+-=== attr | 1:2.4.47-2 logrotate| 3.8.7-1 samba-vfs-modules| 2:4.1.11+dfsg-1 Suggests (Version) | Installed ==-+-= bind9 (= 1:9.5.1) | bind9utils | ctdb | ldb-tools | ntp| smbldap-tools | winbind| -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754441: GMastermind Relicensing
Hi Riley, the program comes with a COPYING file, which standard to contain the license used. In thiscase, it contains the GPL v2 or later. In other words: 1) the program headers contain reference to the GPL v2 or later 2) the COPYING file distirbuted with GMastermind contains the GPL v2 or later text 3) only the readme file contains a reference to the program being distributed GPL v2 without the or later clause To me it is clear that the intent is the program to be under GPLv2 or later and that the readme.txt contains a small omission. The source files and the COPYING file have priority! Given this, I already consider all my contributions under the GPL v2 or later clause. Riccardo On 2014-07-22 09:26:48 +0200 Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: Hi Riccardo, Even if you're not the original author, if you've made any modifications to the work, you own copyright on them. For example, Linus Torvalds is not the only copyright holder of Linux; the other ~5000 contributors all have copyright on it as well. This is why the kernel can't be upgraded to GPL-3, even if Linus wants to. So, having a statement from you would be helpful. (You are only relicensing *your* contributions) Also, what do you mean by the COPYING is the full GPL v2 or later? Riley -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754441: GMastermind Relicensing
Hi Riley, thanks for inquirying. I am not the original author of GMastermind, thus I cannot relicense it, if you need that explicit statement, you need to ask Marko Riedel. I see you put it in CC, I do not know if that email address is current though. We just got permissions to incorporate GMastermind in GAP. I think the original author licensed it under GPLv2+. The README file is misleading and probably written in haste. Not only the header files explicitely say or later, but also the COPYING is the full GPL v2 or later statement. The README file says to refer to gpl.txt, this is probably inaccurate and COPYING was intended. I would say that the original intentions are pretty clear. Just in the case, I corrected the README file and also updated COPYING to the current GPL v2+ file from fsf, it had even the old FSF address. Perhaps that statement should be removed totally and just COPYING should be included. Riccardo Riley Baird wrote: Hi, I'm currently packaging GMastermind for Debian. In the process, it has been discovered that, according to a technical reading of the README, GMastermind is licensed under GPL-2 only (i.e. without or, at your option, any later version). However, according to the headers on the source files, it would appear that the intention was to license under GPL-2 or any later version. If you are fine with releasing your contributions under GPL-2+, please copy the following statement, fill in your name and send it to the email addresses below. (If not, then please send a message anyway so we know.) - I, YOUR NAME, irrevocably give permission to use, redistribute, modify and to distribute modified copies of any and all of my contributions to the program GMastermind under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (should anyone choose to do so) any later version. No warranty, not even the implied warranties of merchantability or fitness for a particular purpose, is given by this license grant. --- Please send this statement to the following email addresses: bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch 754...@bugs.debian.org pkg-gnustep-maintain...@lists.alioth.debian.org gap-dev-disc...@nongnu.org NOTE: If you don't want to be bothered by licensing issues again, send the following statement in instead. I, YOUR NAME, release my contributions to the program GMastermind into the public domain. This applies worldwide. In some countries, this may not be legally possible; if so: I grant anyone the right to use this my contributions to the program GMastermind for any purpose, without any conditions, unless such conditions are required by law. - Thanks in advance, Riley Baird -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755106: same error with pypy
Hello, i see the same error when i try to create a virtualenv with pypy: $ virtualenv -p /usr/bin/pypy pypyvenv Running virtualenv with interpreter /usr/bin/pypy New pypy executable in pypyvenv/bin/pypy Installing setuptools, pip... Complete output from command /home/rm/src/pypyvenv/bin/pypy -c import sys, pip; sys...d\] + sys.argv[1:])) setuptools pip: Traceback (most recent call last): File app_main.py, line 75, in run_toplevel File app_main.py, line 581, in run_it File string, line 1, in module ZipImportError: cannot import name 'CertificateError' ...Installing setuptools, pip...done. Traceback (most recent call last): File app_main.py, line 75, in run_toplevel File /usr/lib/python3/dist-packages/virtualenv.py, line 2378, in module main() File /usr/lib/python3/dist-packages/virtualenv.py, line 830, in main symlink=options.symlink) File /usr/lib/python3/dist-packages/virtualenv.py, line 1032, in create_environment install_wheel(to_install, py_executable, search_dirs) File /usr/lib/python3/dist-packages/virtualenv.py, line 975, in install_wheel 'PIP_NO_INDEX': '1' File /usr/lib/python3/dist-packages/virtualenv.py, line 917, in call_subprocess % (cmd_desc, proc.returncode)) OSError: Command /home/rm/src/pypyvenv/bin/pypy -c import sys, pip; sys...d\] + sys.argv[1:])) setuptools pip failed with error code 1 thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754333: [libreoffice-common] one more path to remove
Package: libreoffice-common Version: 1:4.2.5-1 --- Please enter the report below this line. --- Here's the empry dir that makes the rmdir fail: $ find /var/lib/libreoffice/share/ /var/lib/libreoffice/share/ /var/lib/libreoffice/share/config --- System information. --- Architecture: i386 Kernel: Linux 3.14.2 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+-== libreoffice-style-default | OR libreoffice-style | ure | 4.3.0~rc3-1 libreoffice-core (= 1:4.1.2-2) | 1:4.3.0~rc3-1 python (= 2.7) | 2.7.6-2 python ( 2.8) | 2.7.6-2 libc6 (= 2.4) | 2.19-4 libgcc1(= 1:4.1.1) | 1:4.9.1-1 libpython2.7 (= 2.7) | 2.7.7-2 libstdc++6 (= 4.1.1) | 4.9.1-1 uno-libs3 (= 4.1.0~alpha) | 4.3.0~rc3-1 ure | 4.3.0~rc3-1 libreoffice-core (= 1:4.3.0~rc3-1) | 1:4.3.0~rc3-1 python3 (= 3.4~) | 3.4.1-1 python3( 3.5) | 3.4.1-1 python3.4 | 3.4.1-6 libc6 (= 2.4) | 2.19-4 libgcc1(= 1:4.1.1) | 1:4.9.1-1 libpython3.4(= 3.4~b1) | 3.4.1-6 libstdc++6 (= 4.1.1) | 4.9.1-1 uno-libs3 (= 4.1.0~alpha) | 4.3.0~rc3-1 ure | 4.3.0~rc3-1 Recommends (Version) | Installed =-+-=== xfonts-mathml | 6 python3-uno(= 4.0~) | 1:4.3.0~rc3-1 OR python-uno| libexttextcat-data| 3.4.4-1 Suggests (Version) | Installed ===-+-=== libreoffice-style-crystal | libreoffice-style-hicontrast| libreoffice-style-oxygen| 1:4.3.0~rc3-1 libreoffice-style-sifr | libreoffice-style-tango | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755290: [libreoffice-base] duplicated files with libreoffice-common
Package: libreoffice-base Version: 1:4.3.0~rc3-1 Severity: normal --- Please enter the report below this line. --- Hello, here's the upgrade error: Unpacking libreoffice-common (1:4.3.0~rc3-1) over (1:4.2.5-1) ... dpkg: error processing archive /var/cache/apt/archives/libreoffice-common_1%3a4.3.0~rc3-1_all.deb (--unpack): trying to overwrite '/usr/lib/libreoffice/share/basic/script.xlc', which is also in package libreoffice-base 1:4.3.0~rc3-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Looking at debian/rules 2283 mv $(PKGDIR)-common/$(OODIR)/share/basic/Access2Base \ 2284 $(PKGDIR)-base/$(OODIR)/share/basic 2285 cp $(PKGDIR)-common/$(OODIR)/share/basic/dialog.xlc \ 2286 $(PKGDIR)-base/$(OODIR)/share/basic 2287 cp $(PKGDIR)-common/$(OODIR)/share/basic/script.xlc \ 2288 $(PKGDIR)-base/$(OODIR)/share/basic these cp should be mv instead? --- System information. --- Architecture: i386 Kernel: Linux 3.14.2 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-= libreoffice-base-core (= 1:4.3.0~rc3-1) | 1:4.3.0~rc3-1 libreoffice-base-drivers(= 1:4.3.0~rc3-1) | 1:4.3.0~rc3-1 libreoffice-core(= 1:4.3.0~rc3-1) | 1:4.3.0~rc3-1 libc6(= 2.4) | 2.19-4 libgcc1 (= 1:4.1.1) | 1:4.9.1-1 libstdc++6 (= 4.9) | 4.9.1-1 uno-libs3(= 4.1.0~alpha) | 4.3.0~rc3-1 ure | 4.3.0~rc3-1 fontconfig| 2.11.0-5 fonts-opensymbol | 2:102.6+LibO4.2.5-1 libreoffice-common ( 1:4.3.0~rc3) | 1:4.2.5-1 ure (= 4.2~) | 4.3.0~rc3-1 libatk1.0-0 (= 1.12.4) | 2.12.0-1 libboost-date-time1.55.0 | 1.55.0+dfsg-2 libc6 (= 2.16) | 2.19-4 libcairo2 (= 1.2.4) | 1.12.16-2 libclucene-contribs1 (= 2.3.3.4) | 2.3.3.4-4 libclucene-core1 (= 2.3.3.4) | 2.3.3.4-4 libcmis-0.4-4 (= 0.4.0) | 0.4.1-7 libcups2 (= 1.4.0) | 1.7.4-1 libcurl3-gnutls (= 7.16.2) | 7.37.0-1+b1 libdbus-1-3(= 1.0.2) | 1.8.6-1 libdbus-glib-1-2(= 0.78) | 0.102-1 libeot0 | 0.01-2 libexpat1 (= 2.0.1) | 2.1.0-6 libexttextcat-2.0-0(= 2.2-8) | 3.4.4-1 libfontconfig1 (= 2.11) | 2.11.0-5 libfreetype6 (= 2.3.5) | 2.5.2-1 libgcc1 (= 1:4.1.1) | 1:4.9.1-1 libgdk-pixbuf2.0-0(= 2.22.0) | 2.30.7-1 libgl1-mesa-glx | 10.2.3-1 OR libgl1| libglew1.10 (= 1.10.0) | 1.10.0-3 libglib2.0-0 (= 2.15.0) | 2.40.0-3 libglu1-mesa | 9.0.0-2 OR libglu1 | libgraphite2-3 (= 1.2.2) | 1.2.4-3 libgtk2.0-0 (= 2.24.0) | 2.24.24-1 libharfbuzz-icu0 (= 0.9.18) | 0.9.29-1 libharfbuzz0b (= 0.9.18) | 0.9.29-1 libhunspell-1.3-0 (= 1.3.3) | 1.3.3-1 libhyphen0 (= 2.7.1) | 2.8.7-2 libice6 (= 1:1.0.0) | 2:1.0.8-2 libicu52(= 52~m1-1~) | 52.1-4 libjpeg8 (= 8c) | 8d1-1 liblangtag1(= 0.4.0) | 0.5.1-2 liblcms2-2 (= 2.2+git20110628) | 2.6-3 libldap-2.4-2 (= 2.4.7) | 2.4.39-1 libmythes-1.2-0 | 2:1.2.4-1 libneon27-gnutls | 0.30.0-3 libnspr4 (= 2:4.9-2~) | 2:4.10.6-1 OR libnspr4-0d (= 1.8.0.10) | 2:4.10.6-1 libnss3 (= 2:3.13.4-2~) | 2:3.16.3-1 OR libnss3-1d (= 3.12.0~1.9b1) | 2:3.16.3-1 libodfgen-0.1-1 | 0.1.1-1 libpango-1.0-0(= 1.14.0) | 1.36.3-1 libpangocairo-1.0-0 (= 1.14.0) | 1.36.3-1 libpangoft2-1.0-0 (= 1.14.0) | 1.36.3-1 libpng12-0 (= 1.2.13-4) | 1.2.50-1 librevenge-0.0-0
Bug#754854: [uwsgi] patch 1005 should not be needed
Package: uwsgi Version: 2.0.6~dfsg-2 Severity: wishlist --- Please enter the report below this line. --- Patch 1005_emperor-pg-fix-cflags.patch should have been already fixed upstream in 7c31b6657ffdbbbe566822fbcdb6cf2eb4b44026 so could be removed. --- System information. --- Architecture: i386 Kernel: Linux 3.14.2 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-== uwsgi-core (= 2.0.6~dfsg-2) | 2.0.6~dfsg-2 lsb-base | 4.1+Debian13 initscripts (= 2.88dsf-13.3) | 2.88dsf-53.2 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751299: homebank: Add account adjustment feature
Package: homebank Version: 4.5.5-2 Severity: wishlist Tags: upstream This software could benefit from a feature called account adjustment in some of its competitors e.g. Microsoft Money 2003: as HomeBank is right now you can only set a starting balance and transactions are incrementally applied over that. In certain scenarios (like keeping track of your paper money), the ability to record the value of an account at any arbitrary moment would greatly enhance the usability of this program. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages homebank depends on: ii homebank-data4.5.5-2 ii libatk1.0-0 2.12.0-1 ii libc62.18-7 ii libcairo21.12.16-2 ii libfontconfig1 2.11.0-5 ii libfreetype6 2.5.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.23-1 ii libofx4 1:0.9.4-2.1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpangoft2-1.0-01.36.3-1 Versions of packages homebank recommends: ii librsvg2-common 2.40.2-1 homebank suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744989: [libharfbuzz0b] Please provide debug symbols package
Package: libharfbuzz0b Version: 0.9.27-1 Severity: wishlist --- Please enter the report below this line. --- --- System information. --- Architecture: i386 Kernel: Linux 3.12.12 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+- libc6 (= 2.4) | 2.18-4 libfreetype6(= 2.3.9) | 2.5.2-1 libglib2.0-0 (= 2.30.0) | 2.40.0-2 libgraphite2-3 (= 1.2.2) | 1.2.4-2 Package's Recommends field is empty. Package's Suggests field is empty. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726965: workaround
Removing acceleration works, in the sense that I get a usable display. However, the speed is ridiculous, it takes almost a second to move a window... with acceleration the old system was instead quite snappy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742897: [libffi6] 3.1 update makes icedove crash
Package: libffi6
Version: 3.1~rc1-2
Severity: serious
--- Please enter the report below this line. ---
Hi,
libffi broke icedove 24.4.0-1. Gdm3 / gnome shell are broken for me too
but i don't know if it is the same issue. Downgrading to 3.0.13-12 fixed
the issue for me.
Here's a snippet of the stack trace, sorry i didn't have symbols at the
time.
Program received signal SIGSEGV, Segmentation fault.
js::ctypes::CClosure::ClosureStub (cif=0xe04a34c0, result=0xc3f0,
args=0xc390, userData=0x23)
at
/build/icedove-n9H_k3/icedove-24.4.0/mozilla/js/src/ctypes/CTypes.cpp:6114
6114
/build/icedove-n9H_k3/icedove-24.4.0/mozilla/js/src/ctypes/CTypes.cpp:
File o directory non esistente.
(gdb) bt full
#0 js::ctypes::CClosure::ClosureStub (cif=0xe04a34c0,
result=0xc3f0, args=0xc390, userData=0x23)
at
/build/icedove-n9H_k3/icedove-24.4.0/mozilla/js/src/ctypes/CTypes.cpp:6114
cx = optimized out
autoCallback = {cx = 0x0, callback = 0xe1952780, endType =
3784648576}
thisObj = optimized out
rvSize = optimized out
ar = optimized out
ac = {cx_ = 0xe1952780, oldCompartment_ = 0x10010}
cinfo = 0x23
typeObj = optimized out
jsfnObj = optimized out
argv = {JS::AutoVectorRooterJS::Value = {JS::AutoGCRooter
= {down = 0xc03d42e0, tag_ = -436977664, stackTop = 0x0},
vector = {js::TempAllocPolicy = {cx_ = 0xe1952780},
static sElemIsPod = false, static sMaxInlineBytes = 1024, static
sInlineCapacity = 8,
static sInlineBytes = 64, mBegin = 0xf627c813
ReleaseData(void*, unsigned int)+13, mLength = 3857989632, mCapacity =
3784648576,
storage = {u = {
bytes =
\000\000\000\000Mm\002\365\220\303\377\377\200\022)\367p\336\264c\017\000\000\000\250+I\365\300'\225\341\037\000\000\000Mm\002\365\214\276\365\345\300'\225\341x\303\377\377\v\347\\366\214\276\365\345\300'\225,
incomplete sequence \341, _ = 17654793666725675008}},
static sMaxInlineStorage = optimized out}, vectorRoot =
{No data fields}}, No data fields}
#1 0xf7fd55ef in ?? () from /usr/lib/i386-linux-gnu/libffi.so.6
No symbol table info available.
#2 0xf7fd5b26 in ?? () from /usr/lib/i386-linux-gnu/libffi.so.6
No symbol table info available.
#3 0xf3aeb85e in gdk_event_apply_filters (filters=optimized out,
event=0xee7e3060, xevent=0xc520)
at /build/gtk+2.0-FpgWcq/gtk+2.0-2.24.22/gdk/x11/gdkevents-x11.c:356
filter = optimized out
tmp_list = 0xee64a1c0
result = optimized out
--- System information. ---
Architecture: i386
Kernel: Linux 3.12.12
Debian Release: jessie/sid
500 unstableftp.de.debian.org
500 testing ftp.de.debian.org
500 stable dl.google.com
1 experimentalftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
==-+-===
libc6 (= 2.4) | 2.18-4
Package's Recommends field is empty.
Package's Suggests field is empty.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742897: downgrade fixed gdm3 too
Hi, downgrading libffi version fixed being able to login from gdm too. thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742719: installation-reports: Network Manager fail to connect at wifi
Package: installation-reports Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: Boot method: Image version: Date: Date and time of the install Machine: Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7 (wheezy) - installer build 20130613+deb7u1+b1 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux Storm 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 16h Processor Root Complex [1022:1536] lspci -knn: Subsystem: Advanced Micro Devices [AMD] Family 16h Processor Root Complex [1022:1536] lspci -knn: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Device [1002:9834] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI Device [1002:9834] lspci -knn: 00:01.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Device [1002:9840] lspci -knn: Subsystem: Advanced Micro Devices [AMD] nee ATI Device [1002:9840] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:02.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 16h Processor Function 0 [1022:1538] lspci -knn: 00:02.3 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 16h Processor Functions 5:1 [1022:1439] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:02.4 PCI bridge [0604]: Advanced Micro Devices [AMD] Family 16h Processor Functions 5:1 [1022:1439] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:10.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB XHCI Controller [1022:7814] (rev 01) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: Kernel driver in use: xhci_hcd lspci -knn: 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] FCH SATA Controller [AHCI mode] [1022:7801] lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB OHCI Controller [1022:7807] (rev 39) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB EHCI Controller [1022:7808] (rev 39) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB OHCI Controller [1022:7807] (rev 39) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] FCH USB EHCI Controller [1022:7808] (rev 39) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] FCH SMBus Controller [1022:780b] (rev 3a) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] FCH Azalia Controller [1022:780d] (rev 02) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] FCH LPC Bridge [1022:780e] (rev 11) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:0834] lspci
Bug#741593: Support profiling of ramdisk (a.k.a. initramfs, initrd)
Hi Trent,
Il 19/03/2014 07:18, Trent W. Buck ha scritto:
I got it to work, but I had to be evil.
Nice!
sed -i /usr/share/initramfs-tools/init \
-e '\|/run/initramfs$|a/lib/bootchart/bootchart-collector ' \
-e '/^mount.*move.*proc$/ a mount -n -o move /lib/bootchart/tmpfs
${rootmnt}/lib/bootchart/tmpfs'
That is, it starts /lib/bootchart/bootchart-collector *after* /proc
and /dev are mounted (takes about 1s).
This also fixes the problem where bootchart-collector thought it was
run outside initrd -- because it does that by reading
/proc/self/mountinfo, so /proc must be mounted first.
Correct
I'm also moving /lib/bootchart/tmpfs inside the pivot.
I'm not sure if that's actually needed.
It should not be needed, if you can test it's not needed it would be helpful
Finally, bootchart-collector --dump needs to the real collector process,
so I had to stop banning ptrace with these:
$ cat /etc/sysctl.d/disable-ptrace.conf
kernel/yama/ptrace_scope=3
$ cat /proc/cmdline
[...] security=yama
Yes, ptrace is used to extract collection data from the other process
Attached is my first successful ramdisk trace.
Because I'm waiting for scripts/init to mount proc and dev,
I still lose a full second at the start.
But it works.
I *wasn't* passing rdinit or init at all.
I guess way to clean this up is similar to live-boot's strategy:
boot with boot=bootchart2 real_boot=local,
where /usr/share/initramfs-tools/bootchart2 goes something like
mountroot() { # -*- shell-script -*-
/lib/bootchart/bootchart-collector
# FIXME: parse /proc/cmdline here
# Chainload the real mountroot function.
. scripts/${real_boot:-local}
mountroot
# FIXME: is this needed?
mount -omove /lib/bootchart/tmpfs ${rootmnt}/lib/bootchart/tmpfs
}
I don't think the rdinit=/sbin/bootchartd approach will work well,
short of duplicating dozens of lines of code from initramfs-tools'
init.
If you have time to dedicate to that, care to post a patch?
Thanks a lot,
riccardo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741767: gretl: FTBFS: complete.c:129:41: error: 'CPPFunction' undeclared (first use in this function)
On Tue, 18 Mar 2014, Dirk Eddelbuettel wrote: On 16 March 2014 at 16:14, Allin Cottrell wrote: | On Sun, 16 Mar 2014, Dirk Eddelbuettel wrote: | | Here is a fresh Debian bug report. It looks like that the bleeding edge | changed things -- in this case readline apparently had and no longer has | CPPFunction defined. | | Yep, that disappeared in readline 6.3. Gretl CVS is already up to date | with the change. We should probably do a release before long. Or else direct me to / help me to a patch that does the same? Else gretl risk being tossed out of the archive for 'being unable to build' :-/ Possibly, the following may be enough; could you please check? --- complete.c 2007/08/22 15:10:47 1.12 +++ complete.c 2014/03/08 19:29:10 1.13 @@ -126,6 +126,6 @@ rl_readline_name = gretl; /* Tell the completer that we want a crack first. */ -rl_attempted_completion_function = (CPPFunction *) gretl_completion; +rl_attempted_completion_function = (rl_completion_func_t *) gretl_completion; } Release sounds good though. This should happen fairly soon, methinks. --- Riccardo (Jack) Lucchetti Dipartimento di Scienze Economiche e Sociali (DiSES) Università Politecnica delle Marche (formerly known as Università di Ancona) r.lucche...@univpm.it http://www2.econ.univpm.it/servizi/hpp/lucchetti ---
Bug#741593: Support profiling of ramdisk (a.k.a. initramfs, initrd)
Hi Trent, Il 14/03/2014 09:29, Trent W. Buck ha scritto: Package: bootchart2 Version: 0.14.4-3 Severity: wishlist Currently bootchart2 can be used to profile everything after init easily, by booting with init=/sbin/bootchartd. I have some netboot kiosks that spend about 10s in the ramdisk doing boot=live (live-initramfs-tools) and then another 10s or so in init. It would be really awesome if I could get pretty graphs of what is wasting all the time in the initramfs. I tried to do it myself with bootchart2, then with busybox's builtin bootchart applet[0], but I couldn't work it out. You can find an initramfs-tools hook here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603656#15 also please take a look at message #20 which have a correction to my instructions. thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733348: rhythmbox: Support custom file/folder naming conventions
Package: rhythmbox Version: 2.97-2.1 Severity: wishlist Tags: upstream In Preferences Folder Hierarchy, a limited number of choices are available, like Album, Artist or other combinations. None of them allow for putting all files at the root of the library; or more generally this system limits the user's choice. I propose that future versions of Rhythmbox have the ability to manually enter folder structure and file names using a placeholder system (like printf, strftime, ...). -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-0.bpo.3-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rhythmbox depends on: ii dbus 1.6.8-1+deb7u1 ii gnome-icon-theme 3.4.0-2 ii gstreamer0.10-plugins-base 0.10.36-1.1 ii gstreamer0.10-plugins-good 0.10.31-3+nmu1 ii gstreamer0.10-x 0.10.36-1.1 ii libatk1.0-0 2.4.0-2 ii libc62.13-38+deb7u1 ii libcairo-gobject21.12.2-3 ii libcairo21.12.2-3 ii libffi5 3.0.10-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgirepository-1.0-11.32.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgstreamer-plugins-base0.10-0 0.10.36-1.1 ii libgstreamer0.10-0 0.10.36-1.2 ii libgtk-3-0 3.4.2-7 ii libice6 2:1.0.8-2 ii libjson-glib-1.0-0 0.14.2-1 ii libpango1.0-01.30.0-1 ii libpeas-1.0-01.4.0-2 ii librhythmbox-core6 2.97-2.1 ii libsm6 2:1.2.1-2 ii libsoup-gnome2.4-1 2.38.1-2 ii libsoup2.4-1 2.38.1-2 ii libtdb1 1.2.10-2 ii libtotem-plparser17 3.4.2-1 ii libxml2 2.8.0+dfsg1-7+nmu2 ii media-player-info17-1 ii rhythmbox-data 2.97-2.1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages rhythmbox recommends: ii avahi-daemon0.6.31-2 ii gstreamer0.10-plugins-ugly 0.10.19-2+b2 ii gstreamer0.10-pulseaudio0.10.31-3+nmu1 ii gvfs-backends 1.12.3-4 ii notification-daemon 0.7.6-1 ii rhythmbox-plugins 2.97-2.1 ii yelp3.4.2-1+b1 Versions of packages rhythmbox suggests: pn gnome-codec-install none ii gnome-control-center 1:3.4.3.1-2 ii gstreamer0.10-plugins-bad0.10.23-7.1 ii rhythmbox-plugin-cdrecorder 2.97-2.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731259: [gcc-4.8] 3.12.6 boots fine compiled with 4.8.2-10
Package: gcc-4.8 Version: 4.8.2-10 --- Please enter the report below this line. --- 3.12.6 boots fine compiled with 4.8.2-10. Should we consider the issue fixed or want me to compile the same kernel of the report with newer gcc? --- System information. --- Architecture: i386 Kernel: Linux 3.12.6 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+-== cpp-4.8 (= 4.8.2-10) | 4.8.2-10 gcc-4.8-base(= 4.8.2-10) | 4.8.2-10 binutils (= 2.23.91.20131123) | 2.24-2 libgcc-4.8-dev (= 4.8.2-10) | 4.8.2-10 libc6 (= 2.11) | 2.17-97 libcloog-isl4 (= 0.17) | 0.18.1-3 libgmp10 | 2:5.1.3+dfsg-1 libisl10 (= 0.10) | 0.12.1-2 libmpc3 | 1.0.1-1 libmpfr4 (= 3.1.2) | 3.1.2-1 zlib1g (= 1:1.1.4) | 1:1.2.8.dfsg-1 Recommends (Version) | Installed ==-+- libc6-dev (= 2.13-5) | 2.17-97 Suggests (Version) | Installed ===-+-== gcc-4.8-multilib| gcc-4.8-doc(= 4.8) | gcc-4.8-locales(= 4.8) | libgcc1-dbg (= 1:4.8.2-10) | libgomp1-dbg (= 4.8.2-10) | libitm1-dbg (= 4.8.2-10) | libatomic1-dbg(= 4.8.2-10) | libasan0-dbg (= 4.8.2-10) | 4.8.2-10 libtsan0-dbg (= 4.8.2-10) | libbacktrace1-dbg (= 4.8.2-10) | libquadmath0-dbg (= 4.8.2-10) | binutils-gold (= 2.23.91.20131123) | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731259: [gcc-4.8] gcc-4.8 compiled 3.10.x kernel does not boot
Package: gcc-4.8 Version: 4.8.2-7 Severity: normal --- Please enter the report below this line. --- Compiling a 64bit kernel on my 32 bit host results on a kernel that does not boot and hangs while decompressing. Kernels compiled with gcc-4.7 works perfectly fine. I've uploaded both kernels here: http://people.freedesktop.org/~rm/gcc48/ The one compiled with gcc-4.8 is the .old one. $ gcc-4.8 -v Using built-in specs. COLLECT_GCC=gcc-4.8 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-linux-gnu/4.8/lto-wrapper Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-7' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-i386/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-i386 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-i386 --with-arch-directory=i386 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-targets=all --enable-multiarch --with-arch-32=i586 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu $ gcc-4.7 -v Using built-in specs. COLLECT_GCC=gcc-4.7 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-linux-gnu/4.7/lto-wrapper Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.3-9' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --enable-objc-gc --enable-targets=all --enable-multiarch --with-arch-32=i586 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.7.3 (Debian 4.7.3-9) --- System information. --- Architecture: i386 Kernel: Linux 3.10.21 Debian Release: jessie/sid 500 unstableftp.de.debian.org 500 stable dl.google.com 1 experimentalftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+-== cpp-4.8 (= 4.8.2-7) | 4.8.2-7 gcc-4.8-base (= 4.8.2-7) | 4.8.2-7 binutils (= 2.23.91.20131123) | 2.24-1 libgcc-4.8-dev (= 4.8.2-7) | 4.8.2-7 libc6 (= 2.11) | 2.17-97 libcloog-isl4 (= 0.17) | 0.18.1-3 libgmp10 | 2:5.1.2+dfsg-3 libisl10 (= 0.10) | 0.12.1-2 libmpc3 | 1.0.1-1 libmpfr4 (= 3.1.2) | 3.1.2-1 zlib1g (= 1:1.1.4) | 1:1.2.8.dfsg-1 Recommends (Version) | Installed ==-+- libc6-dev (= 2.13-5) | 2.17-97 Suggests (Version) | Installed ===-+-== gcc-4.8-multilib| gcc-4.8-doc(= 4.8) | gcc-4.8-locales(= 4.8) | libgcc1-dbg (= 1:4.8.2-7) | libgomp1-dbg (= 4.8.2-7) | libitm1-dbg(= 4.8.2-7) | libatomic1-dbg (= 4.8.2-7) | libasan0-dbg (= 4.8.2-7) | 4.8.2-7 libtsan0-dbg (= 4.8.2-7) | libbacktrace1-dbg (= 4.8.2-7) | libquadmath0-dbg (= 4.8.2-7) | binutils-gold (= 2.23.91.20131123) | -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728490: empathy: Avatar hard to set from webcam
Package: empathy Version: 3.8.4-2 Severity: normal Tags: upstream * Using GNOME 3, open Empathy [on a user profile that never used it, the window prompting to configure local network chatting pops up. Complete it] and end up at the Messaging and VoIP Accounts window. * Click on the [unset] profile photo, and in the file picker sheet click the webcam button. It is replaced by a camera output sheet. * Click the button to take a photo. The sheet disappears and the accounts window appears unresponsive. ** Pressing esc at this point flashes the animation of a sheet closing and gets Empathy running again. * The sheet with the crop-or-cancel controls was actually created behind the Accounts window, and being a sheet it automatically follows its parent. Dragging the accounts window outside the corners of the desktop partially uncovers the affected area (but surely requires creative thinking!). -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages empathy depends on: ii dbus-x11 1.6.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.18.0-1 ii empathy-common 3.8.4-2 ii geoclue 0.12.99-3 ii gnome-icon-theme 3.8.3-1 ii gsettings-desktop-schemas3.4.2-3 ii gstreamer1.0-pulseaudio 1.2.0-1 ii libc62.17-93 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libchamplain-0.12-0 0.12.5-1 ii libchamplain-gtk-0.12-0 0.12.5-1 ii libcheese-gtk23 3.8.3-1 ii libclutter-1.0-0 1.14.4-3 ii libclutter-gst-2.0-0 2.0.8-1 ii libclutter-gtk-1.0-0 1.4.4-3 ii libcogl121.14.0-3 ii libdbus-glib-1-2 0.100.2-1 ii libenchant1c2a 1.6.0-10 ii libfarstream-0.2-2 0.2.3-1 ii libfolks-telepathy25 0.9.2-2 ii libfolks25 0.9.2-2 ii libgcr-base-3-1 3.8.2-4 ii libgcr-ui-3-13.8.2-4 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgee-0.8-2 0.10.5-1 ii libgeoclue0 0.12.99-3 ii libgeocode-glib0 3.10.0-1 ii libglib2.0-0 2.36.4-1 ii libgnutls26 2.12.23-8 ii libgoa-1.0-0 3.8.3-2 ii libgstreamer-plugins-base1.0-0 1.2.0-1 ii libgstreamer1.0-01.2.0-1 ii libgtk-3-0 3.8.4-1 ii libgudev-1.0-0 204-5 ii libmission-control-plugins0 1:5.16.0-1 ii libnotify4 0.7.6-1 ii libpango-1.0-0 1.32.5-5+b1 ii libpulse-mainloop-glib0 4.0-6+b1 ii libpulse04.0-6+b1 ii libsecret-1-00.15-2 ii libsoup2.4-1 2.44.1-1 ii libtelepathy-farstream3 0.6.0-2 ii libtelepathy-glib0 0.22.0-1 ii libtelepathy-logger3 0.8.0-2 ii libwebkitgtk-3.0-0 2.2.0-2 ii libx11-6 2:1.6.2-1 ii libxml2 2.9.1+dfsg1-3 ii telepathy-logger 0.8.0-2 ii telepathy-mission-control-5 1:5.16.0-1 Versions of packages empathy recommends: ii gvfs-backends1.16.3-1+b1 pn nautilus-sendto-empathy none ii sound-theme-freedesktop 0.8-1 ii telepathy-gabble 0.18.1-1 ii telepathy-haze 0.8.0-1 ii telepathy-salut 0.8.1-1 Versions of packages empathy suggests: ii telepathy-idle 0.1.16-1 ii vino3.10.1-1 Versions of packages empathy is related to: ii telepathy-gabble [telepathy-connection-manager] 0.18.1-1 ii telepathy-haze [telepathy-connection-manager]0.8.0-1 ii telepathy-idle [telepathy-connection-manager]0.1.16-1 ii telepathy-salut [telepathy-connection-manager] 0.8.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726701: Fwd: Bug#726701: general: apt-get install bootchart pybootchartgui command marking important packages for removal
Hi Thomas, Il 21/10/2013 09:05, Thomas Waite ha scritto: Riccardo, Sorry for the late response, just checking email. Loaded a fresh install of Debian 7 Wheezy and ran a few tests. 1 - apt-get install pybootchartgui 2 - apt-get install bootchart2 3 - apt-get install bootchart2 pybootchartgui All of these tests installed these packages with no issues, at least no issues on install as I didn't go any further and test operation. 4 - apt-get install bootchart This would have caused an unbootable system if I continued with the installation. Thanks for testing, will try to forward the bug to bootchart. BTW probably it's time to ask for bootchart removal. thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726701: general: apt-get install bootchart pybootchartgui command marking important packages for removal
Hi tuck225, this was for you and not for Holger :) Il 19/10/2013 09:11, Riccardo Magliocchetti ha scritto: Hi Holger, are you sure it's not bootchart the one breaking? I think you want to install bootchart2 instead which is the one pybootchartgui is packaged from. Could you please try to just install pybootchartgui to sort out it's not bootchart? thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726701: general: apt-get install bootchart pybootchartgui command marking important packages for removal
Hi Holger, are you sure it's not bootchart the one breaking? I think you want to install bootchart2 instead which is the one pybootchartgui is packaged from. thanks, riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725427: pommed: Should be able to mute more or less than 2 channels
Package: pommed
Version: 1.39~dfsg-2+b1
Severity: normal
Tags: upstream
The volume control part of pommed is implemented by mapping the volume buttons
to the levels of one ALSA channel (ideally the master level) and the mute
button to the on/off status of two channels (in the default config, Speakers
and Headphones).
On a MacbookPro8,1 with a mostly clean base Wheezy + task-lxde-desktop, either
the Master channel has to be muted or all 3 of Headphones, Front Speaker
and Surround Speaker to completely disable sound output, neither of which
appears to be possible according to the configuration file.
In the meanwhile I remapped the headphone control to the woofer.
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pommed depends on:
ii eject 2.1.5+deb1+cvs20081104-13
ii libasound2 1.0.25-4
ii libaudiofile1 0.3.4-2
ii libc6 2.13-38
ii libconfuse02.7-4
ii libdbus-1-31.6.8-1+deb7u1
ii libpci31:3.1.9-6
Versions of packages pommed recommends:
ii dbus 1.6.8-1+deb7u1
pommed suggests no packages.
-- Configuration Files:
/etc/pommed.conf changed:
general {
# fnmode: functions keys first (no need to use fn) or last
# Value is either 1 or 2, effect is hardware-dependent
fnmode = 1
}
lcd_sysfs {
# The sysfs backlight control is a generic interface provided
# by the Linux kernel for backlight control on most graphic cards.
# The brightness range can differ depending on the hardware.
# initial backlight level [12] (0 - 15, -1 to disable)
init = 8
# step value (1 - 2)
step = 1
# backlight level when on battery [6] (1 - 15, 0 to disable)
on_batt = 6
}
lcd_x1600 {
# initial backlight level [200] (0 - 255, -1 to disable)
init = -1
# step value (1 - 127)
step = 10
# backlight level when on battery [80] (1 - 255, 0 to disable)
on_batt = 80
}
lcd_gma950 {
# initial backlight level [0x6f] (0x1f - 0x94 usually, -1 to disable)
init = -1
# step value (0x01 - 0x20)
step = 0x0f
# backlight level when on battery [0x40] (0x1f - 0x94 usually, 0 to
disable)
on_batt = 0x40
}
lcd_nv8600mgt {
# initial backlight level [12] (0 - 15, -1 to disable)
init = -1
# step value (1 - 2)
step = 1
# backlight level when on battery [6] (1 - 15, 0 to disable)
on_batt = 6
}
audio {
# disable audio support entirely
disabled = no
# Use amixer or alsamixer/alsamixergui to determine the sound card
# and the mixer elements to use here.
# sound card to use
card = default
# initial volume [80] (0 - 100%, -1 to disable)
init = -1
# step value (1 - 50%)
step = 10
# beep on volume change
beep = yes
# mixer element for volume adjustment
volume = Master
# mixer element for muting the speakers
speakers = Front Speaker
# mixer element for muting the headphones
headphones = Surround Speaker
}
kbd {
# default value for automatic backlight (0 - 255)
default = 100
# step value (1 - 127)
step = 20
# ambient light thresholds for automatic backlight (0 - 255)
on_threshold = 20
off_threshold = 40
# enable/disable automatic backlight
auto = no
# idle timer - fades keyboard backlight automatically (timeout in
seconds, -1 to disable)
idle_timer = -1
# idle level - level to fade keyboard to after idle_timer seconds.
Defaults to switching off.
# idle_level = 20
}
eject {
# enable/disable eject key
enabled = yes
# CD/DVD device
device = /dev/sr0
}
beep {
# enable/disable beeper
# automatically disabled if audio support disabled above
enabled = no
# WAV file to use (from pommed: goutte.wav or click.wav in
/usr/share/pommed)
beepfile = /usr/share/pommed/goutte.wav
}
appleir {
# enable/disable the appleir support
enabled = no
}
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724785: heimdall-flash-frontend: Package doesn't depend on heimdall-flash
Package: heimdall-flash-frontend Version: 1.4~rc1+dfsg-1 Severity: important I initially installed heimdall-flash-frontend only and ran the executable from a terminal. The software refused to do anything unless an executable found in heimdall-flash was found. Therefore, according to the definition of package relationships, a Depends: heimdall-flash line should be added to the control file. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages heimdall-flash-frontend depends on: ii libc6 2.17-93 ii libgcc1 1:4.8.1-10 ii libqt4-xml 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqtcore4 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libqtgui4 4:4.8.5+git121-g2a9ea11+dfsg-1 ii libstdc++6 4.8.1-10 ii zlib1g 1:1.2.8.dfsg-1 heimdall-flash-frontend recommends no packages. heimdall-flash-frontend suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721980: partman-base: Creates partitions with incorrect system ID on GPT disks
Package: partman-base Version: 165 Severity: minor Tags: d-i upstream upstream After creating two partitions (a 75 MB EFI partition and an ext4 one filling all remaining space) and installing Debian Sid, gdisk 0.8.7-1 prints the following list: Disk /dev/sda: 234441648 sectors, 111.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 890FDD03-1AB9-4DBC-8187-B3CA0F9BF507 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 234441614 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) 12048 155647 75.0 MiBEF00 EFI 2 155648 234441614 111.7 GiB 0700 Debian which implies that the second partition is a Microsoft Basic Data one; the more appropriate 8300 should be used. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719812: gnome-screensaver: Brightness keys are ignored
Package: gnome-screensaver Version: 3.4.1-1+b1 Severity: normal Tags: upstream Since GNOME 3 appears, in my experience, to lack a turn screen off now command such as ctrl+shift+eject in Mac OS, I often find myself turning the display and keyboard backlight all the way down to off when I'm not using the computer. However, if the system stays idle enough to engage the auto-lock (or even enter standby), the password prompt will have to be answered blindly, as the required function keys are ignored. The only workaround would be backspacing until you hear the alert sound (assuming, as per bug 429281, that the sound was on!), type your password, press Return, then try the brightness control hoping you got it right the first time. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-screensaver depends on: ii dbus-x11 1.6.12-1 ii gnome-icon-theme 3.8.2-2 ii gnome-session-bin 3.4.2.1-4 ii gsettings-desktop-schemas 3.4.2-3 ii libc6 2.17-92 ii libcairo2 1.12.14-4 ii libdbus-1-31.6.12-1 ii libdbus-glib-1-2 0.100.2-1 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-0 2.36.3-3 ii libgnome-desktop-3-2 3.4.2-2 ii libgnomekbd8 3.6.0-1 ii libgtk-3-0 3.8.2-3 ii libpam0g 1.1.3-9 ii libx11-6 2:1.6.0-1 ii libxext6 2:1.3.2-1 ii libxklavier16 5.2.1-1 ii libxxf86vm11:1.1.2-1+deb7u1 Versions of packages gnome-screensaver recommends: ii gnome-power-manager 3.8.2-1 ii libpam-gnome-keyring 3.8.2-2 gnome-screensaver suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710922: shotwell: Two clicks to rename event
Package: shotwell Version: 0.14.1-2 Severity: wishlist Tags: upstream The current only procedure to rename a Shotwell event is to right-click it and select Rename Event Most applications have the de-facto convention of being able to rename a file by clicking twice on its name, and I personally believe supporting this method would only improve usability through consistency. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages shotwell depends on: ii dbus-x111.6.10-1 ii libatk1.0-0 2.8.0-2 ii libc6 2.17-3 ii libcairo-gobject2 1.12.14-4 ii libcairo2 1.12.14-4 ii libexif12 0.6.21-1 ii libexiv2-12 0.23-1 ii libgdk-pixbuf2.0-0 2.28.1-1 ii libgee2 0.6.4-2 ii libgexiv2-2 0.6.1-2 ii libglib2.0-02.36.1-2build1 ii libgomp14.8.0-7 ii libgphoto2-22.4.14-2 ii libgphoto2-port02.4.14-2 ii libgstreamer-plugins-base1.0-0 1.0.7-1 ii libgstreamer1.0-0 1.0.7-1 ii libgtk-3-0 3.4.2-6 ii libgudev-1.0-0 175-7.2 ii libjavascriptcoregtk-3.0-0 1.8.1-3.4 ii libjson-glib-1.0-0 0.14.2-1 ii liblcms2-2 2.2+git20110628-2.2 ii libpango1.0-0 1.30.0-1 ii libraw5 0.14.7-2 ii librest-0.7-0 0.7.12-3 ii librsvg2-common 2.36.1-1 ii libsoup2.4-12.38.1-2 ii libsqlite3-03.7.17-1 ii libstdc++6 4.8.0-7 ii libwebkitgtk-3.0-0 1.8.1-3.4 ii libx11-62:1.5.0-1+deb7u1 ii libxml2 2.8.0+dfsg1-7+nmu1 ii shotwell-common 0.14.1-2 shotwell recommends no packages. shotwell suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710831: gnome-online-accounts: Doesn't support non-standard SMTP ports
Package: gnome-online-accounts
Version: 3.8.2-1
Severity: normal
While adding a new account of IMAP and SMTP type, the following option is
shown:
Encryption: {none | STARTTLS after connecting | SSL on a dedicated port}
Not only its wording may falsely suggest the ability to choose an arbitrary
port (despite its intent to opposite how TLS encrypts an existing plaintext
connection), but more generally it's absolutely impossible to manually select a
port, not even after a significant time required for the attempt to time out.
Being therefore unable to add my SMTP server, I would like to request an option
to manually select a port.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-online-accounts depends on:
ii libc6 2.17-3
ii libgcr-3-1 3.4.1-3
ii libglib2.0-0 2.36.1-2build1
ii libgoa-1.0-0 3.8.2-1
ii libkrb5-3 1.10.1+dfsg-6
ii librest-0.7-0 0.7.12-3
ii libsoup2.4-1 2.42.2-4
Versions of packages gnome-online-accounts recommends:
ii gnome-control-center 1:3.4.3.1-3
gnome-online-accounts suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709305: aptitude: Incorrect Italian translation of -aptitude update- output
Package: aptitude Version: 0.6.8.2-1 Severity: minor Tags: l10n Sample output of `aptitude update` with it_IT.UTF-8 locale: [...] Get: 28 http://debian.dynamica.it sid/main 2013-05-21-2016.39.pdiff [7665 B] Scaricato 384 kB in 1min 51s (3434 B/s) Stato attuale: 27 aggiornati [+27], 16 nuovi [+16]. The Scaricato (downloaded), being a plural quantity, should actually read Scaricati. Additionally, as in the deselected vs. unselected controversy in dpkg, aggiornati (updated/upgraded, those words are equivalent in Italian) implies that what is called upgrading packages has already taken place: as the message indicates a certain amount of upgradeable packages which may or may not be actually upgraded, that word should be chaged into aggiornabili (upgradeable). -- Package-specific info: $TERM not set. $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.8.2 compiled at Nov 5 2012 06:20:41 Compiler: g++ 4.7.2 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.2.10 Ept support enabled. Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20130504 cwidget version: 0.5.16 Apt version: 4.12.0 aptitude linkage: linux-gate.so.1 (0xb7766000) libapt-pkg.so.4.12 = /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12 (0xb71f5000) libncursesw.so.5 = /lib/i386-linux-gnu/libncursesw.so.5 (0xb71c2000) libtinfo.so.5 = /lib/i386-linux-gnu/libtinfo.so.5 (0xb71a1000) libsigc-2.0.so.0 = /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 (0xb719c000) libcwidget.so.3 = /usr/lib/libcwidget.so.3 (0xb709c000) libept.so.1.aptpkg4.12 = /usr/lib/libept.so.1.aptpkg4.12 (0xb7008000) libxapian.so.22 = /usr/lib/libxapian.so.22 (0xb6e22000) libz.so.1 = /lib/i386-linux-gnu/libz.so.1 (0xb6e09000) libsqlite3.so.0 = /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb6d56000) libboost_iostreams.so.1.49.0 = /usr/lib/libboost_iostreams.so.1.49.0 (0xb6d4) libpthread.so.0 = /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb6d24000) libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb6c36000) libm.so.6 = /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb6bf3000) libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xb6bd7000) libc.so.6 = /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb6a28000) libutil.so.1 = /lib/i386-linux-gnu/i686/cmov/libutil.so.1 (0xb6a23000) libdl.so.2 = /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb6a1e000) libbz2.so.1.0 = /lib/i386-linux-gnu/libbz2.so.1.0 (0xb6a0d000) libuuid.so.1 = /lib/i386-linux-gnu/libuuid.so.1 (0xb6a07000) librt.so.1 = /lib/i386-linux-gnu/i686/cmov/librt.so.1 (0xb69fe000) /lib/ld-linux.so.2 (0xb7767000) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.8-2-rt-686-pae (SMP w/1 CPU core; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptitude depends on: ii aptitude-common 0.6.8.2-1 ii libapt-pkg4.120.9.8.1 ii libboost-iostreams1.49.0 1.49.0-4 ii libc6 2.17-3 ii libcwidget3 0.5.16-3.4 ii libept1.4.12 1.0.9 ii libgcc1 1:4.8.0-7 ii libncursesw5 5.9+20130504-1 ii libsigc++-2.0-0c2a2.2.10-0.2 ii libsqlite3-0 3.7.16.2-1 ii libstdc++64.8.0-7 ii libtinfo5 5.9+20130504-1 ii libxapian22 1.2.15-1 ii zlib1g1:1.2.8.dfsg-1 Versions of packages aptitude recommends: pn apt-xapian-indexnone pn aptitude-doc-en | aptitude-doc none pn libparse-debianchangelog-perl none ii sensible-utils 0.0.7 Versions of packages aptitude suggests: ii debtags 1.10.2 ii tasksel 3.15 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709222: apt-listchanges: Poor grammar in Italian translation of a configuration question
Package: apt-listchanges Version: 2.85.11 Severity: minor Tags: l10n As I was reconfiguring apt-listchanges to set my actual user to receive a copy of changelogs, this dialog popped up: È possibile tener traccia dei cambiamenti già mostrate per evitare di mostrarle nuovamente in seguito. [...] apt-listchanges deve ignorare i cambiamenti già mostrate? This translation of the Should already seen changelogs be ignored? question has gender concordance issues, assuming changelogs are female. A correct phrase would be as follows: È possibile tener traccia dei cambiamenti già mostrati per evitare di mostrarle nuovamente in seguito. [...] apt-listchanges deve ignorare i cambiamenti già mostrati? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.8-2-rt-686-pae (SMP w/1 CPU core; PREEMPT) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-listchanges depends on: ii apt0.9.8.1 ii debconf [debconf-2.0] 1.5.50 ii debianutils4.3.4 ii python 2.7.3-5 ii python-apt 0.8.9 ii python-support 1.0.15 ii ucf3.0027 apt-listchanges recommends no packages. Versions of packages apt-listchanges suggests: ii chromium [www-browser] 26.0.1410.43-1 ii exim4-daemon-light [mail-transport-agent] 4.80-7 ii python-glade2 2.24.0-3+b1 ii python-gtk22.24.0-3+b1 ii w3m [www-browser] 0.5.3-8 ii xfce4-terminal [x-terminal-emulator] 0.4.8-1+b1 ii xterm [x-terminal-emulator]278-4 -- debconf information: * apt-listchanges/frontend: pager * apt-listchanges/confirm: false * apt-listchanges/which: news * apt-listchanges/email-address: riki * apt-listchanges/save-seen: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700073: repo moved
Moved repository to: https://github.com/gc3-uzh-ch/ganglia Regards, Riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703103: base: System boots to an apparently random tty
Package: base Severity: minor I've recently installed an AGP ATI Radeon 100 graphics card to get advantage of an high resolution console. (I believe this is relevant as the problem was nonexistant while using the integrated Intel i810 video): (lspci output: 00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02) [...] 02:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV100 QY [Radeon 7000/VE] ) I used `aptitude install linux-firmware-nonfree` to fix some warnings printed at early boot, but this problem was preexisting. In fact, the problem manifested immediately after installing Sid via a tutorial found on a popular Italian fansite (install stable base system, edit sources.list, apt-get update/upgrade/install apt dpkg aptitude, aptitude dist-upgrade). At this moment, the system is fully upgraded as the packages available at 2013-3-15 13:00 GMT were. After booting, the login prompt appears on an apparently random virtual console (most often tty3). While this isn't clearly correct behavior, it does not impair usability on a standard setup as all consoles are equal (this might not apply if inittab is edited to use autologin, but I haven't tried this scenario or any display manager). -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698165: uvesafb: HP Vectra VL400DT, unable to set console resolution
After a lot of experimentation, I succeeded in building a kernel that boots properly with that framebuffer driver. While it formally works (as highlighted by the Tux logo which I also enabled), custom fonts e.g. Fixed and Terminus revert to the standard one when the module is loaded; the only resolution accessible via `fbset` is VGA and the cursor looks like a glitchy block which starts out purple with some off-coloured dots in the bottom but eventually changes (apparently, after using programs with pseudo-graphic interfaces like `lynx-cur`)… On 15/gen/2013, at 02:18, Ben Hutchings b...@decadent.org.uk wrote: Have you tried the i810fb driver? Ben. smime.p7s Description: S/MIME cryptographic signature
Bug#700073: ganglia: new version 3.5.0 released
Source: ganglia Severity: wishlist Dear Maintainers, Ganglia version 3.5.0 has been released; the web frontend has been split from the main sources and is now at version 3.5.4. The current `.deb` packaging files work with version 3.5 with only minor modifications; I have done the repackaging for internal use at my workplace, the code is available from: https://github.com/riccardomurri/ganglia The repository has been cloned from the Debian one at git.debian.org, so it should be easy to pull my commits and start from there. (Alternatively, I can send the patches as attachment to this report.) Thanks for packaging Ganglia in Debian! Regards, Riccardo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
