Bug#791465: mysql-server-5.6: install of mysql-server-5.6 because /etc/init.d/mysql does not end with exit 0 in start case
Package: mysql-server-5.6 Version: 5.6.25-2 Severity: important If have been tracking a postinstall failure to discover that postintsall fails if: /bin/sh points to /bin/dash (not clear why but debian scripts are clearly bash ependent but do start with #!/bin/bash). Anyway this was not supposed to happen on my system /etc/init.d/mysql does not exit 0 in the case of start and this is checked by postins script. adding an exit 0 at the end of the file made instal; work. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.1.1 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages mysql-server-5.6 depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii init-system-helpers1.23 ii initscripts2.88dsf-59.2 ii libaio10.3.110-1 ii libc6 2.21-0experimental0 ii libdbi-perl1.633-1 ii libgcc11:5.1.1-21 ii libstdc++6 5.1.1-21 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13+nmu1 ii mysql-client-5.6 5.6.25-2 ii mysql-common 5.6.25-2 ii mysql-server-core-5.6 5.6.25-2 ii passwd 1:4.2-3 ii perl 5.20.2-6 ii psmisc 22.21-2 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages mysql-server-5.6 recommends: ii libhtml-template-perl 2.95-2 Versions of packages mysql-server-5.6 suggests: ii bsd-mailx [mailx] 8.1.2-0.20150408cvs-1 ii heirloom-mailx [mailx] 12.5-4 pn tinyca -- Configuration Files: /etc/init.d/mysql changed [not included] /etc/mysql/debian-start changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762386: Any comments?
If someone wants to debug x86 program he can install valgrind for x86. Why force amd64 valgrins users to install x86 libraries? -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768476: As it also break reportbug filling bug is complicated;-)
I found cmake was broken because curl was broken and discovered this bug. Trying to report the bug reportbug itself was broken! File "/usr/lib/python2.7/dist-packages/wstools/Utility.py", line 30, in from httplib import HTTPConnection, HTTPSConnection ImportError: cannot import name HTTPSConnection So please put a conflicts with libcurl at least to avoid upgrading! -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762291: libuv-dev: Doing apt-get update shows error on this package
Package: libuv-dev Version: 0.10.28-4 Severity: important apt-get update ... Lecture des listes de paquets... Fait W: Ignoring Provides line with DepCompareOp for package libuv-dev W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.3 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (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#758619: Why still not fixed!
It means almost nobody can report bug on unstable. A working patch is available -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762833: apt: Bad handling of external/non-debian package signature keys
Package: apt Version: 1.1~exp3 Severity: important apt-get update W: GPG error: http://download.virtualbox.org wheezy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54422A4B98AB5139 W: GPG error: http://dl.google.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A040830F7FAC5991 W: GPG error: http://dl.google.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A040830F7FAC5991 W: GPG error: http://dl.google.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A040830F7FAC5991 W: GPG error: http://www.deb-multimedia.org sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907 W: GPG error: http://www.deb-multimedia.org experimental InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907 apt-get install --reinstall deb-multimedia-keyring Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 0 B/14.4 kB of archives. After this operation, 0 B of additional disk space will be used. WARNING: The following packages cannot be authenticated! deb-multimedia-keyring Install these packages without verification? [y/N] y (Reading database ... 374059 files and directories currently installed.) Preparing to unpack .../deb-multimedia-keyring_2012.05.10-dmo4_all.deb ... Unpacking deb-multimedia-keyring (2012.05.10-dmo4) over (2012.05.10-dmo4) ... Setting up deb-multimedia-keyring (2012.05.10-dmo4) ... OK root@r-x-ceva6380:/home/ceva6380# apt-get install --reinstall deb-multimedia-keyring Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 0 B/14.4 kB of archives. After this operation, 0 B of additional disk space will be used. WARNING: The following packages cannot be authenticated! deb-multimedia-keyring Install these packages without verification? [y/N] ^C -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.3 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Versions of packages apt depends on: ii debian-archive-keyring 2014.1 ii gnupg 1.4.18-4 ii libapt-pkg4.13 1.1~exp3 ii libc6 2.19-11 ii libgcc1 1:4.9.1-15 ii libstdc++6 4.9.1-15 apt recommends no packages. Versions of packages apt suggests: pn apt-doc ii dpkg-dev1.17.13 ii python-apt 0.9.3.10 ii synaptic0.81.2 -- 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#762833: Even if I rerun apt-get update, I still get the error
Firsty, all the keys where already in. Then doing install and rerenning update leads to same behavior apt-get update ... W: Erreur de GPG : http://apt.jenslody.de testing InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY C96E627C6EEB25C9 W: Erreur de GPG : http://dl.google.com stable Release : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY A040830F7FAC5991 W: Erreur de GPG : http://dl.google.com stable Release : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY A040830F7FAC5991 W: Erreur de GPG : http://download.virtualbox.org wheezy InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 54422A4B98AB5139 W: Erreur de GPG : http://www.deb-multimedia.org unstable InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 07DC563D1F41B907 W: Erreur de GPG : http://www.deb-multimedia.org experimental InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 07DC563D1F41B907 apt-get install --reinstall deb-multimedia-keyring<=== ... Construction de l'arbre des dépendances Lecture des informations d'état... Fait Le paquet suivant a été installé automatiquement et n'est plus nécessaire : libopenjpeg6 Veuillez utiliser « apt-get autoremove » pour le supprimer. 0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 2 non mis à jour. Il est nécessaire de prendre 14,4 ko dans les archives. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. ATTENTION : les paquets suivants n'ont pas été authentifiés. deb-multimedia-keyring Faut-il installer ces paquets sans vérification ? [o/N] o Réception de : 1 http://www.deb-multimedia.org/ unstable/main deb-multimedia-keyring all 2012.05.10-dmo4 [14,4 kB] 14,4 ko réceptionnés en 0s (161 ko/s) (Lecture de la base de données... 346903 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../deb-multimedia-keyring_2012.05.10-dmo4_all.deb ... Dépaquetage de deb-multimedia-keyring (2012.05.10-dmo4) sur (2012.05.10-dmo4) ... tri-yann4:/home/valette# apt-get update<== Lecture des listes de paquets... Fait W: Erreur de GPG : http://www.deb-multimedia.org unstable InRelease : Les signatures <== suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 07DC563D1F41B907 W: Erreur de GPG : http://www.deb-multimedia.org experimental InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 07DC563D1F41B907 W: Erreur de GPG : http://apt.jenslody.de testing InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY C96E627C6EEB25C9 W: Erreur de GPG : http://dl.google.com stable Release : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY A040830F7FAC5991 W: Erreur de GPG : http://dl.google.com stable Release : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY A040830F7FAC5991 W: Erreur de GPG : http://download.virtualbox.org wheezy InRelease : Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 54422A4B98AB5139 -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762833: reopen
reopen #762833 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#758619: The fix was intended/verified for a non graphical useage
At least the fix, solves this use case (at least for me). And as the bug is in pygtk2 which is dead, maybe the bug should be reassigned. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762833: confirm this bug
On 10/01/2014 12:45 PM, Julian Andres Klode wrote: > On Wed, Oct 1, 2014 at 12:15 PM, Valery Mamonov > wrote: >> Problem solved by making /etc/apt/trusted.gpg world readable, but it's >> insecure workaround. >> >> 2014-09-30 17:01 GMT+04:00 Valery Mamonov : >>> >>> https://lists.debian.org/debian-user/2014/09/msg02346.html >>> >>> -- >>> >>> Best regards, >>> >>> Valery Mamonov. > > No, It's not insecure. Not at all. It's not an issue if your users > know which keys APT accepts. > > Oh, and it's the default setting. NO. I never changed this permission manually and this is not what I got. And if you do not want people to voice, you should be active instead of closing the bug without even trying to fix it. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762833: confirm this bug
On 10/01/2014 12:57 PM, Eric Valette wrote: > On 10/01/2014 12:45 PM, Julian Andres Klode wrote: > NO. I never changed this permission manually and this is not what I got. > And if you do not want people to voice, you should be active instead of > closing the bug without even trying to fix it. And, on the technical side, if the file is used only by apt, why not keep rw but for _apt instead of root ? -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#762833: confirm this bug
On 10/01/2014 01:03 PM, Eric Valette wrote: > On 10/01/2014 12:57 PM, Eric Valette wrote: >> On 10/01/2014 12:45 PM, Julian Andres Klode wrote: > >> NO. I never changed this permission manually and this is not what I got. >> And if you do not want people to voice, you should be active instead of >> closing the bug without even trying to fix it. > > And, on the technical side, if the file is used only by apt, why not > keep rw but for _apt instead of root ? I'm also a bit surpised, the open error when opening the file /etc/apt/trusted.gpg, did not rise an error as EACCES instead of ENOENT are not identical errors when opening a file. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764817: Bug confirmed and fixe validated
Thanks Laurent for posting the/a solution. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#804547: [nvidia-driver] Outdated nvidia drivers
On Thu, 4 Feb 2016 11:49:48 +0100 Andreas Beckmann wrote: On 2016-02-04 10:55, Nick T. wrote: > Hello Andreas, > > The 355.11-1 version is 7 months old already which is way outdated already for newer games(e.g. XCOM-2 comming out this Friday needs 355.63 and above) the newest version on nvidias website is 358.16. > And also according to #813565 the new driver is not compatible with sids X abi. With a reasonably recent driver in unstable and testing (352.79) experimental was finally free for testing upstream reorganization (new packages needed, new module build system, new kernel module), so at the moment experimental is actually experimental :-) The biggest problem is that the version uploaded to experimental cannot run with unstable : it does no even support abi-20 and forcing -ignoreABI just makes the drivers crash. So please at least put in experimental something that do work with unstable. It broke my system for a reason that the usual excuse cannot cover -- eric
Bug#813565: reopen
reopen #813585 This driver is not compatible officially compatible with abi 20. Xhy don't you package a newer driver instead of packaging this old one? --eric
Bug#813565: reopen
reopen 813585
Bug#815559: konsole: Konsole fails to use default font when selected font in profile becomes unavailable
Package: konsole Version: 4:15.12.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, In my konsole profile, I was using droid fonts that juts habe veen removed. So I started my konsole, got the screen but nothing was displayed at all. It should at least use a default (backup) font and print something to help user fixing the problem. To reprodure : define a profile witha font, then remove the font and restart. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages konsole depends on: ii konsole-kpart 4:15.12.1-1 ii libc6 2.22-0experimental1 ii libkf5completion5 5.16.0-1 ii libkf5configcore5 5.16.0-1 ii libkf5configgui55.16.0-1 ii libkf5configwidgets55.16.0-1 ii libkf5coreaddons5 5.16.0-1 ii libkf5i18n5 5.19.0-1 ii libkf5iconthemes5 5.16.0-1 ii libkf5kdelibs4support5 5.16.0-1 ii libkf5kiowidgets5 5.16.0-1 ii libkf5notifyconfig5 5.16.0-1 ii libkf5widgetsaddons55.16.0-1 ii libkf5windowsystem5 5.16.0-1 ii libkf5xmlgui5 5.16.0-1 ii libqt5core5a5.5.1+dfsg-14 ii libqt5gui5 5.5.1+dfsg-14 ii libqt5widgets5 5.5.1+dfsg-14 ii libstdc++6 5.3.1-9 konsole recommends no packages. konsole suggests no packages. -- no debconf information
Bug#815565: libreoffice: recreating table of content on existing documents, page are numbered using Capital Letter (C, D, ...)
Package: libreoffice Version: 1:5.1.1~rc1-1 Severity: normal Yesterday, I was updating a document with this new version and trying to update my table of content, it completely messed it. I found no way to make the page number be numbered as 1,2,3 instead of A,B,C. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libreoffice depends on: ii fonts-dejavu 2.35-1 ii fonts-sil-gentium-basic1.1-7 ii libreoffice-avmedia-backend-gstreamer 1:5.1.1~rc1-1 ii libreoffice-base 1:5.1.1~rc1-1 ii libreoffice-calc 1:5.1.1~rc1-1 ii libreoffice-core 1:5.1.1~rc1-1 ii libreoffice-draw 1:5.1.1~rc1-1 ii libreoffice-impress1:5.1.1~rc1-1 ii libreoffice-java-common1:5.1.1~rc1-1 ii libreoffice-math 1:5.1.1~rc1-1 ii libreoffice-report-builder-bin 1:5.1.1~rc1-1 ii libreoffice-writer 1:5.1.1~rc1-1 ii python3-uno1:5.1.1~rc1-1 Versions of packages libreoffice recommends: ii fonts-liberation 2.00.1-1 ii libpaper-utils1.1.24+nmu4 Versions of packages libreoffice suggests: ii cups-bsd2.1.3-1 ii default-jre [java5-runtime] 2:1.8-56 ii gcj-5-jre [java5-runtime] 5.3.1-9 ii gcj-jre [java5-runtime] 4:5.3.1-1 ii gstreamer1.0-libav 1:1.6.3-dmo1 ii gstreamer1.0-plugins-bad1:1.6.3-dmo2 ii gstreamer1.0-plugins-base 1.7.2-1 ii gstreamer1.0-plugins-good 1.7.2-1 ii gstreamer1.0-plugins-ugly 1.7.2-1 ii hunspell-en-us [hunspell-dictionary]20070829-6 ii hunspell-fr-classical [hunspell-dictionary] 1:5.5-1 ii hyphen-en-us [hyphen-hyphenation-patterns] 2.8.8-2 ii hyphen-fr [hyphen-hyphenation-patterns] 1:5.0.4-1 ii iceweasel 45.0~b5-1 ii imagemagick 8:6.9.2.10+dfsg-2 ii imagemagick-6.q16 [imagemagick] 8:6.9.2.10+dfsg-2 ii libgl1-mesa-glx [libgl1]11.1.2-1 ii libreoffice-help-en-us [libreoffice-help-5.1] 1:5.1.1~rc1-1 ii libreoffice-kde 1:5.1.1~rc1-1 pn libreoffice-l10n-5.1 ii libreoffice-lightproof-en [libreoffice-grammarchec 0.4.3+1.5+git20140515-2 pn libreoffice-officebean ii libsane 1.0.26~git20151121-1 ii libxrender1 1:0.9.9-2 pn myspell-dictionary ii mythes-en-us [mythes-thesaurus] 1:5.0.4-1 pn openclipart2-libreoffice | openclipart-libreoffice ii openjdk-7-jre [java5-runtime] 7u95-2.6.4-2 ii openjdk-8-jre [java5-runtime] 8u72-b15-2 ii pstoedit3.70-1 ii unixodbc2.3.1-4 Versions of packages libreoffice-core depends on: ii fontconfig2.11.0-6.3 ii fonts-opensymbol 2:102.7+LibO5.1.1~rc1-1 ii libboost-date-time1.58.0 1.58.0+dfsg-5+b1 ii libc6 2.22-0experimental1 ii libcairo2 1.14.6-1 ii libclucene-contribs1v52.3.3.4-4.1 ii libclucene-core1v52.3.3.4-4.1 ii libcmis-0.5-5v5 0.5.0-4 ii libcups2 2.1.3-1 ii libcurl3-gnutls 7.47.0-1 ii libdbus-1-3 1.11.0-1 ii libdbus-glib-1-2 0.106-1 ii libdconf1 0.24.0-2 ii libeot0 0.01-3 ii libexpat1 2.1.0-7 ii libexttextcat-2.0-0 3.4.4-1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.6.1-0.1 ii libgcc1 1:5.3.1-9 ii libgl1-mesa-glx [libgl1] 11.1.2-1 ii libglew1.13 1.13.0-2 ii libglib2.0-0 2.47.6-1 ii libgltf-0.0-0v5 0.0.2-4+b1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libgraphite2-31.3.5-1 ii libharfbuzz-icu0 1.0.1-1+b1 ii libharfbuzz0b 1.0.1-1+b1 ii libhunspell-1.3-0 1.3.3-3+b2 ii libhyphen02.8.8-2 ii libice6 2:1.0.9-1+b1 ii libicu55 55.1-7 ii libjpeg62-turbo 1:1.4.80-115-gfb907b2-1 ii liblangta
Bug#815679: dolphin: Dolphin enables to set additional acl permissions but is unable to display them
Package: dolphin Version: 4:15.12.1-1 Severity: normal Dear Maintainer, cat > toto.txt hello ACL Here I have only set regular permissions. Then I used dophin and selected the toto.txt file, thyen right click properties, permissions, advanced permissions, add entries I managed to give user clamav rwx permission on the file as shown below (note the + on the ls line) 3 r-x-ceva6380:~->ls -l toto.txt -rw-rwxr--+ 1 ceva6380 ceva6380 10 Feb 23 16:35 toto.txt 4 r-x-ceva6380:~->getfacl toto.txt # file: toto.txt # owner: ceva6380 # group: ceva6380 user::rw- user:clamav:rwx <= group::r-- mask::rwx other::r-- But if you quit dolphin, and redo the same stuff it does not show the user:clamav:rwx in the advanced permissions. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.2 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages dolphin depends on: ii libc6 2.22-0experimental1 ii libdolphinvcs5 4:15.12.1-1 ii libkf5baloo5 5.16.0-1 ii libkf5baloowidgets515.12.0-1 ii libkf5bookmarks5 5.16.0-1 ii libkf5codecs5 5.16.0-1 ii libkf5completion5 5.16.0-1 ii libkf5configcore5 5.16.0-1 ii libkf5configgui5 5.16.0-1 ii libkf5configwidgets5 5.16.0-1 ii libkf5coreaddons5 5.16.0-1 ii libkf5crash5 5.16.0-1 ii libkf5dbusaddons5 5.16.0-1 ii libkf5filemetadata35.19.0-1 ii libkf5i18n55.19.0-1 ii libkf5iconthemes5 5.16.0-1 ii libkf5itemviews5 5.16.0-1 ii libkf5jobwidgets5 5.16.0-1 ii libkf5kcmutils55.16.0-1 ii libkf5kiocore5 5.16.0-1 ii libkf5kiofilewidgets5 5.16.0-1 ii libkf5kiowidgets5 5.16.0-1 ii libkf5newstuff55.16.0-1 ii libkf5notifications5 5.16.0-1 ii libkf5parts5 5.16.0-1 ii libkf5service-bin 5.16.0-1 ii libkf5service5 5.16.0-1 ii libkf5solid5 5.16.0-1 ii libkf5textwidgets5 5.16.0-1 ii libkf5widgetsaddons5 5.16.0-1 ii libkf5windowsystem55.16.0-1 ii libkf5xmlgui5 5.16.0-1 ii libphonon4qt5-44:4.8.3-2 ii libqt5core5a 5.5.1+dfsg-14 ii libqt5dbus55.5.1+dfsg-14 ii libqt5gui5 5.5.1+dfsg-14 ii libqt5widgets5 5.5.1+dfsg-14 ii libqt5xml5 5.5.1+dfsg-14 ii libstdc++6 5.3.1-9 ii phonon4qt5 4:4.8.3-2 Versions of packages dolphin recommends: ii ruby 1:2.3~0 Versions of packages dolphin suggests: ii dolphin-plugins 4:15.12.0-1 -- no debconf information
Bug#813565: xserver-xorg-video-nvidia: This version is incompatible with the current unstable xserver abi
Package: xserver-xorg-video-nvidia Version: 355.11-1 Severity: critical Justification: breaks unrelated software sddm no more starts. starting xserverr manually via startx, nvidia driver report ABI incompatibilities and suggest to pass -ignoreABI. Doing this the xserver crash even before I can start my desktop. So it does not follow the experimental rules that it should work with unstable pacakges -- Package-specific info: uname -a: Linux tri-yann4 4.4.1 #13 SMP PREEMPT Sun Jan 31 23:22:15 CET 2016 x86_64 GNU/Linux /proc/version: Linux version 4.4.1 (valette@tri-yann4) (gcc version 5.3.1 20160121 (Debian 5.3.1-7) ) #13 SMP PREEMPT Sun Jan 31 23:22:15 CET 2016 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.11 Wed Aug 26 16:35:41 PDT 2015 GCC version: gcc version 5.3.1 20160121 (Debian 5.3.1-7) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology GK104 [GeForce GTX 670] [10b0:1189] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia_current dmesg: [0.00] Console: colour VGA+ 80x25 [0.265474] vgaarb: setting as boot device: PCI::01:00.0 [0.265476] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.265481] vgaarb: loaded [0.265482] vgaarb: bridge control possible :01:00.0 [0.359208] Linux agpgart interface v0.103 [1.038950] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input11 [1.039063] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input12 [1.039169] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input13 [1.039287] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input14 [1.998544] nvidia: module license 'NVIDIA' taints kernel. [2.007015] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [2.007407] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0 [2.007420] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 355.11 Wed Aug 26 16:35:41 PDT 2015 Device node permissions: crw-rw+ 1 root video 226, 0 Feb 3 08:12 /dev/dri/card0 video:x:44:valette,vdr,hts,sddm OpenGL and NVIDIA library files installed: -rw-r--r-- 1 valette valette 1722 Aug 20 2014 /etc/X11/xorg.conf lrwxrwxrwx 1 rootroot 15 Feb 2 18:16 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 rootroot 49 Sep 2 08:50 /etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so lrwxrwxrwx 1 rootroot 44 Feb 2 18:16 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 rootroot 48 Sep 2 08:50 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 rootroot 48 Sep 2 08:50 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 rootroot 43 Feb 2 18:16 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 rootroot 43 Feb 2 18:16 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 rootroot 50 Feb 2 18:16 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 rootroot 50 Feb 2 18:16 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 rootroot 52 Sep 2 08:50 /etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so lrwxrwxrwx 1 rootroot 52 Sep 2 08:50 /etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so lrwxrwxrwx 1 rootroot 47 Feb 2 18:16 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 rootroot 47 Feb 2 18:16 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 rootroot 51 Feb 2 18:16 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 rootroot 25 Feb 2 18:16 /etc/alternatives/glx--
Bug#813565: 358.16 is far more recent than the 355.11 witch is 7 month old. SO why was it uploaded to experimental?
looking at nvidia driver page I really wonder why someone decided to upload this old, not ABI 20 compatible driver to experimental! -- eric
Bug#814316: Why does it always takes multiples days when 0-day exploits are in the wild
This progams brings nothing if it is continuously lagging several days for critical bugs... update-flashplugin-nonfree --status Flash Player version installed on this system : 11.2.202.569 Flash Player version available on upstream site: 11.2.202.577 flash-mozilla.so - auto mode link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 -- eric
Bug#818293: kpartx: cannot be installed
Package: kpartx Version: 0.5.0+git1.656f8865-7 Severity: grave Justification: renders package unusable LANG=C; apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libavformat57 The following packages will be upgraded: kpartx 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/32.2 kB of archives. After this operation, 2048 B disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 387658 files and directories currently installed.) Preparing to unpack .../kpartx_0.5.0+git1.656f8865-7_amd64.deb ... Failed to stop multipathd.service: Unit multipathd.service not loaded. dpkg: warning: subprocess old pre-removal script returned error exit status 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64.deb (--unpack): there is no script in the new version of the package - giving up Failed to get unit file state for multipathd.service: No such file or directory multipathd.service is a disabled or a static unit, not starting it. Errors were encountered while processing: /var/cache/apt/archives/kpartx_0.5.0+git1.656f8865-7_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.5 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kpartx depends on: ii dmsetup 2:1.02.116-1+b1 ii libc6 2.23-0experimental0 ii libdevmapper1.02.1 2:1.02.116-1+b1 ii udev229-2 kpartx recommends no packages. kpartx suggests no packages. -- no debconf information
Bug#818653: sddm: reportbug still incompatible with kde/qt5 from experimental
Package: sddm Version: 0.13.0-1 Severity: normal LANG=C; apt-get -t experimental dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: accountsservice breeze-cursor-theme cracklib-runtime fonts-oxygen gcj-5-jre-lib ieee-data kate5-data kde-config-gtk-style kde-config-sddm kde-style-breeze kde-style-breeze-qt4 kde-style-oxygen-qt5 kmenuedit kwin-style-breeze kwrited libaccountsservice0 libanalitzaplot7 libanalitzawidgets7 libbotan-1.10-1 libcrack2 libgcj16 libgit2-23 libhttp-parser2.1 libkadm5clnt-mit9 libkadm5srv-mit9 libkf5calendarevents5 libkf5people-data libkf5people5 libkf5peoplebackend5 libkf5peoplewidgets5 liboxygenstyle5-5 liboxygenstyleconfig5-5 libpodofo0.9.3 libpowerdevilcore2 libpowerdevilui5 libpwquality-common libpwquality1 libqbscore1 libqbsqtprofilesetup1 libtommath0 libxcb-dpms0 libxcb-record0 oxygen-sounds powerdevil powerdevil-data python-apsw python-markdown python-yaml qml-module-qt-labs-folderlistmodel qml-module-qtwebkit qt5-doc qtbase5-doc qtconnectivity5-doc qtcreator-data qtcreator-doc qtdeclarative5-dev-tools qtdeclarative5-doc qtgraphicaleffects5-doc qtlocation5-doc qtmultimedia5-doc qtquickcontrols5-doc qtscript5-doc qtsensors5-doc qtserialport5-doc qtsvg5-doc qttools5-doc qtwebkit5-doc qtwebkit5-examples-doc qtwebsockets5-doc qtx11extras5-doc qtxmlpatterns5-dev-tools qtxmlpatterns5-doc user-manager Use 'apt autoremove' to remove them. The following packages will be REMOVED: akonadi-backend-sqlite breeze calibre calibre-bin kalgebra kalgebra-common kanagram kate kde-plasma-desktop kdesdk kinfocenter kscreen libqt5positioning5 libreadline6-dev marble marble-plugins milou plasma-desktop plasma-framework plasma-wallpapers-addons plasma-widgets-addons plasma-workspace python-pyqt5 python-pyqt5.qtsvg python-pyqt5.qtwebkit qml-module-org-kde-analitza qml-module-org-kde-kquickcontrols qml-module-qtquick-controls qml-module-qtquick-controls-styles-breeze qml-module-qtquick-dialogs qml-module-qtquick-layouts qml-module-qtquick-privatewidgets qtcreator sddm sddm-theme-breeze xserver-xorg-video-nvidia The following NEW packages will be installed: akonadi-backend-mysql cpp-6 g++-6 gcc-6 gcc-6-base gcj-6-jre-lib imagemagick-6-doc libasan3 libasn1-8-heimdal libgcc-6-dev libgcj17 libgssapi3-heimdal libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal libjs-bootstrap libkadm5clnt-mit10 libkadm5srv-mit10 libkf5calendarevents5 libkf5kdegames7 libkf5kiogui5 libkrb5-26-heimdal libmpx2 libqt5sql5-mysql libroken18-heimdal libstdc++-6-dev libtommath1 libwind0-heimdal libxapian-1.3-5 qt5-qmltooling-plugins xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware The following packages have been kept back: libavformat57 nvidia-legacy-check The following packages will be upgraded: cpp firebird3.0-common firebird3.0-common-doc frameworkintegration g++ gcc imagemagick-doc kactivities kded5 kded5-dev kdesignerplugin-data kgendesignerplugin kinit kinit-dev kio kio-dev kpackagelauncherqml kpackagetool5 krb5-multidev krb5-user kross kross-dev ktexteditor-data ktexteditor-katepart libatomic1 libcc1-0 libcilkrts5 libcuda1 libfbclient2 libgcc1 libgcj-bc libgfortran3 libgl1-nvidia-glx libgomp1 libgssapi-krb5-2 libgssrpc4 libitm1 libk5crypto3 libkdb5-8 libkf5activities5 libkf5auth-bin-dev libkf5auth-data libkf5auth-dev libkf5auth5 libkf5baloo5 libkf5balooengine5 libkf5bookmarks-data libkf5bookmarks-dev libkf5bookmarks5 libkf5codecs-data libkf5codecs-dev libkf5codecs5 libkf5completion-data libkf5completion-dev libkf5completion5 libkf5config-bin libkf5config-bin-dev libkf5config-data libkf5config-dev libkf5configcore5 libkf5configgui5 libkf5configwidgets-data libkf5configwidgets-dev libkf5configwidgets5 libkf5coreaddons-bin-dev libkf5coreaddons-data libkf5coreaddons-dev libkf5coreaddons5 libkf5crash-dev libkf5crash5 libkf5dbusaddons-bin libkf5dbusaddons-data libkf5dbusaddons-dev libkf5dbusaddons5 libkf5declarative-data libkf5declarative5 libkf5dnssd-data libkf5dnssd-dev libkf5dnssd5 libkf5emoticons-bin libkf5emoticons-data libkf5emoticons-dev libkf5emoticons5 libkf5globalaccel-bin libkf5globalaccel-data libkf5globalaccel-dev libkf5globalaccel5 libkf5globalaccelprivate5 libkf5iconthemes-bin libkf5iconthemes-data libkf5iconthemes-dev libkf5iconthemes5 libkf5itemviews-data libkf5itemviews-dev libkf5itemviews5 libkf5jobwidgets-data libkf5jobwidgets-dev libkf5jobwidgets5 libkf5kcmutils-data libkf5kcmutils-dev libkf5kcmutils5 libkf5kdegamesprivate1 libkf5kdelibs4support-data libkf5kdelibs4support-dev libkf5kdelibs4support5 libkf5kdelibs4support5
Bug#818653: Fine but when will we be able to test experimental
I intended the bug as whislist but my first one didn't get correctly out. The second time I forgot... The real question is that for months we are unable to have a working kde/experimental environment. So no test of qt 5.6 and newer kde... -- eric
Bug#818738: libopencv-dev: /usr/share/OpenCV/OpenCVModules.cmake contains reference to libopencv_shape library that is missing
Package: libopencv-dev Version: 3.0.0+dfsg-1~exp2+b1 Severity: important Trying to compile digikam5 with opencv3, I get this error at the very begining: First try at finding OpenCV... CMake Error at /usr/share/OpenCV/OpenCVModules.cmake:120 (message): The imported target "opencv_shape" references the file "/usr/lib/x86_64-linux-gnu/libopencv_shape.so.3.0.0" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/share/OpenCV/OpenCVModules.cmake" but not all the files it references. grep shape /usr/share/OpenCV/OpenCVModules.cmake foreach(_expectedTarget opencv_hal opencv_core opencv_flann opencv_imgproc opencv_ml opencv_photo opencv_video opencv_viz opencv_imgcodecs opencv_shape opencv_videoio opencv_highgui opencv_objdetect opencv_superres opencv_ts opencv_features2d opencv_calib3d opencv_java opencv_stitching opencv_videostab) # Create imported target opencv_shape add_library(opencv_shape SHARED IMPORTED) valette@tri-yann4:~/local/src/digikam$ dpkg -S opencv_shape dpkg-query: aucun chemin ne correspond à *opencv_shape* I have not this error when compiling openCV3 myslef -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.5 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopencv-dev depends on: ii libatomic15.3.1-12 ii libc6 2.23-0experimental0 ii libgcc1 1:5.3.1-12 ii libgl1-mesa-glx [libgl1] 11.2.0~rc3-1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libopencv-calib3d-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-calib3d3.0 3.0.0+dfsg-1~exp2+b1 ii libopencv-core-dev3.0.0+dfsg-1~exp2+b1 ii libopencv-core3.0 3.0.0+dfsg-1~exp2+b1 ii libopencv-features2d-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-features2d3.0 3.0.0+dfsg-1~exp2+b1 ii libopencv-flann-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-flann3.03.0.0+dfsg-1~exp2+b1 ii libopencv-hal-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-highgui-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-highgui3.0 3.0.0+dfsg-1~exp2+b1 ii libopencv-imgcodecs-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-imgcodecs3.03.0.0+dfsg-1~exp2+b1 ii libopencv-imgproc-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-imgproc3.0 3.0.0+dfsg-1~exp2+b1 ii libopencv-ml-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-ml3.0 3.0.0+dfsg-1~exp2+b1 ii libopencv-objdetect-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-objdetect3.03.0.0+dfsg-1~exp2+b1 ii libopencv-photo-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-stitching-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-superres-dev3.0.0+dfsg-1~exp2+b1 ii libopencv-ts-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-video-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-videoio-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-videoio3.0 3.0.0+dfsg-1~exp2+b1 ii libopencv-videostab-dev 3.0.0+dfsg-1~exp2+b1 ii libopencv-viz-dev 3.0.0+dfsg-1~exp2+b1 ii libstdc++65.3.1-12 ii libtbb2 4.3~20150611-1~exp3 ii pkg-config0.29-3 Versions of packages libopencv-dev recommends: ii opencv-data 3.0.0+dfsg-1~exp2 libopencv-dev suggests no packages. -- no debconf information
Bug#818739: opencv: Please package opencv 3.1
Source: opencv Version: 3.0 Severity: wishlist Its now out and working (tried manaul compil and use it compiling digikam 5) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.5 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#818653: Fine but when will we be able to test experimental
On 20/03/2016 15:06, Lisandro Damián Nicanor Pérez Meyer wrote: On Sunday 20 March 2016 10:08:07 Eric Valette wrote: I intended the bug as whislist but my first one didn't get correctly out. The second time I forgot... The real question is that for months we are unable to have a working kde/experimental environment. So no test of qt 5.6 and newer kde... Right, but I'm afraid it's not our problem. Tell KDE upstreams to avoid using Qt's private headers and that will become possible again. True but on the otehr hand you could rebuild the offending packages specifically for experimental using qt 4.6 dependencies. Because as it is you let the user with the choice of not updating or building the packages themselves... -- eric
Bug#819042: nvidia-graphics-drivers: Package uninstallable using unstable
Source: nvidia-graphics-drivers Version: 355.11-3 Severity: grave Tags: upstream Justification: renders package unusable Unstable provides for months an video abi 20 and the upstream package provide no support for it. Furthermore, the package is really old and much newer version supporting this abi and the new openGl packaging do exist. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.5 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#819042: nvidia-graphics-drivers: Package uninstallable using unstable
On 03/24/2016 03:51 PM, Luca Boccassi wrote: On 23 March 2016 at 07:59, Eric Valette wrote: Hi Eric, Hi, We have an upload with new binaries stuck in the NEW queue for a month now: https://ftp-master.debian.org/new/nvidia-graphics-drivers_355.11-3.html Until this gets in, we can't move on unfortunately. I know, but the problem is elsewhere : even if approved, this package cannot be installed on unstable + experimental because of video ABI dependency first and the fact that this upstream package is really incompatble with current unstable xorg video ABI. I started it manaully with -ignoreABI flags and it just crashed almost immediately so it is not only a matter of rebuilding the debian dependencies Please use the 352 series that's available in unstable - experimental will keep being wild for a while, as there are many new binary packages as a result of upstream changes (libglvnd etc). I do but I cannot test anything newer because of the original choice of selecting an outdated driver version... I think you should first package a version that supports the actual unstable video ABI -- eric
Bug#817017: libopencv-highgui-dev: Should not depend on libgtk2.0-dev
Package: libopencv-highgui-dev Version: 3.0.0+dfsg-1~exp2+b1 Severity: important LANG=C; apt-get -t experimental install libopencv-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libopencv-dev : Depends: libopencv-objdetect-dev (= 3.0.0+dfsg-1~exp2+b1) but it is not going to be installed Depends: libopencv-highgui-dev (= 3.0.0+dfsg-1~exp2+b1) but it is not going to be installed Depends: libopencv-calib3d-dev (= 3.0.0+dfsg-1~exp2+b1) but it is not going to be installed Depends: libopencv-features2d-dev (= 3.0.0+dfsg-1~exp2+b1) but it is not going to be installed Depends: libopencv-videostab-dev (= 3.0.0+dfsg-1~exp2+b1) but it is not going to be installed Depends: libopencv-stitching-dev (= 3.0.0+dfsg-1~exp2+b1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. tri-yann4:/home/valette# LANG=C; apt-get -t experimental install libopencv-highgui-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libopencv-highgui-dev : Depends: libgtk2.0-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.4 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopencv-highgui-dev depends on: ii libavcodec-dev 10:3.0-dmo3 ii libavformat-dev10:3.0-dmo3 ii libdc1394-22-dev 2.2.4-1 pn libgtk2.0-dev ii libjasper-dev 1.900.1-debian1-2.4 ii libjpeg-dev1:1.4.80-115-gfb907b2-1 ii libjpeg62-turbo-dev [libjpeg-dev] 1:1.4.80-115-gfb907b2-1 pn libopencv-highgui2.3 ii libopencv-imgproc-dev 3.0.0+dfsg-1~exp2+b1 ii libopenexr-dev 2.2.0-10 ii libpng12-dev 1.2.54-4 ii libraw1394-dev 2.1.1-2 ii libswscale-dev 10:3.0-dmo3 pn libtiff4-dev ii pkg-config 0.29-3 libopencv-highgui-dev recommends no packages. libopencv-highgui-dev suggests no packages.
Bug#808904: sleepd: Now that USE_UPOWER is forced in rules, the package should depend on upower package
Package: sleepd Version: 2.09 Severity: normal Trying to debug pm-suspend problem on a NAS that is configured to go to sleep based on ethernet tx,rx packet activity, I have trouble making it reliably on 4.1.15 kernel (in fact anything older than 3.14.x). It kinda works for some time and then I get kernel error saying it is unable to freeze some tasks, upowerd being one that appears frequently. So I decided to suppress upower on my system and nothing prevented me to do so, including sleepd. Tried pm-suspend manually several time, and as it worked I let the nas run imagaining sleepd would suspe,d the system This morning the NAS was running, and checking the daemon log, sleepd barks because it does find upower and exit. => a dependency is needed. The good point checking the makefiles (rules), it that I can remove the dependcy manually. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.1.15 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages sleepd depends on: ii libapm1 3.2.2-15 ii libc62.22-0experimental1 ii libdbus-1-3 1.11.0-1 pn libhal1 ii lsb-base 9.20150917 Versions of packages sleepd recommends: ii apmd 3.2.2-15 pn hal ii pm-utils 1.4.1-15 sleepd suggests no packages.
Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key
Package: pcscd Version: 1.8.15-1 Severity: critical Justification: breaks unrelated software Twice in two days, I noticed my laptop fan was going carsy allthough I was only doing many mail activity. Twice I found that pcscd was eating a complete CPU and remembered that each time I had inserted a regular mass storage USB key (two different keys) not my crypto key. - top - 12:56:25 up 3:14, 5 users, load average: 2.03, 1.56, 1.31 Tasks: 242 total, 2 running, 239 sleeping, 0 stopped, 1 zombie %Cpu(s): 34.1 us, 21.1 sy, 0.0 ni, 44.8 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 8219052 total, 3472188 free, 2336828 used, 2410036 buff/cache KiB Swap: 16383996 total, 16383996 free,0 used. 5812264 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1687 root 20 0 394560 2916 2120 S 100.3 0.0 147:37.75 pcscd 14477 ceva6380 20 0 424288 57364 37792 R 99.7 0.7 2:59.83 konsole 2921 ceva6380 20 0 1410776 448992 87860 S 15.9 5.5 6:48.46 icedove 4463 ceva6380 20 0 1435116 363080 97112 S 1.7 4.4 4:12.69 iceweasel -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages pcscd depends on: ii init-system-helpers 1.25 ii libc6 2.22-0experimental1 ii libccid [pcsc-ifd-handler] 1.4.22-1 ii libpcsclite11.8.15-1 ii libudev1228-4 ii lsb-base9.20160110 pcscd recommends no packages. Versions of packages pcscd suggests: ii systemd 228-4 -- no debconf information
Bug#812087: pcscd takes 100 % cpu each time I insert a mass storage USB key
>> You can identify a process using PC/SC using: >> $ sudo fuser /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 > sudo fuser /usr/lib/x86_64-linux-gnu/libpcsclite.so.1 > [sudo] password for ceva6380: > /usr/lib/x86_64-linux-gnu/libpcsclite.so.1.0.0: 14662m > 19 r-x-ceva6380:~->ps ax | grep 14662 > 14662 ?Sl11:53 /usr/bin/iceweasel > 22156 pts/5S+ 0:00 grep 14662 > > > Quite strange!!! Not strange the fact that is may use pcscd, but that it polls at this high frequence. I indeed added my PKI via oppropriate library to both FF and TB... Will try to downgrade libusb do when back at work. -- eric
Bug#812423: dansguardian is a dead project, please update to e2guardian that is an alive fork
Package: dansguardian Version: 2.10.1.1-5.1+b1 Severity: wishlist http://e2guardian.org/cms/ https://github.com/e2guardian/e2guardian -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages dansguardian depends on: ii adduser 3.113+nmu3 pn clamav ii libbz2-1.0 1.0.6-8 ii libc62.22-0experimental1 pn libclamav6 ii libgcc1 1:5.3.1-7 ii libpcre3 2:8.38-1 ii libstdc++6 5.3.1-7 ii libtommath0 0.42.0-1.2 ii perl 5.22.1-4 ii zlib1g 1:1.2.8.dfsg-2+b1 dansguardian recommends no packages. Versions of packages dansguardian suggests: pn clamav-freshclam pn squid
Bug#771652: systemd: system 217 breaks config not using initrd and /usr and / different
Package: systemd Version: 217-1 Severity: critical Justification: breaks the whole system After upgrading to 217, I had a crash because init was unable to load libapparmor1. After seraching it is located in /usr that in my system is not yet mounted. copying manually libraries to /lib solves the boot problem (but still breaks X11/kde) -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17.4 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-7 ii mount 2.25.2-3 ii sysv-rc 2.88dsf-58 ii udev217-1 ii util-linux 2.25.2-3 Versions of packages systemd recommends: ii dbus1.9.4-1 ii libpam-systemd 215-7 Versions of packages systemd suggests: pn systemd-ui -- 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
Package: systemd Version: 217-1 Severity: critical Justification: breaks unrelated software After fixing the libapparmor in /usr bug, I managed to boot but kdm was not started. loging as root and using startx lauch a session without problem where I have mouse. Loggin as a normal user via startx breaks mouse and keyboard. Does apparmor mandate new kernel configuration? New user space setup? -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17.4 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-7 ii mount 2.25.2-3 ii sysv-rc 2.88dsf-58 ii udev217-1 ii util-linux 2.25.2-3 Versions of packages systemd recommends: ii dbus1.9.4-1 ii libpam-systemd 215-7 Versions of packages systemd suggests: pn systemd-ui -- 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 12/01/2014 11:47 AM, intrigeri wrote: > Control: tag -1 + moreinfo > > Hi, > > Eric Valette wrote (01 Dec 2014 09:11:32 GMT) : >> After fixing the libapparmor in /usr bug, I managed to boot but kdm was >> not started. loging as root and using startx lauch a session without >> problem where I have mouse. Loggin as a normal user via startx breaks >> mouse and keyboard. > >> Does apparmor mandate new kernel configuration? New user space setup? > > Can you reproduce this with AppArmor disabled? What I can say is that downgrading back to systemd 215 makes the problem vanish. I just saw that systemd217 requires libapparmor1 but as I use my own kernel I have no clue whether its really enabled or not. I have no clue on apparmor useage so tell me how to try (but anyway libapparmor1 being installed in /usr/lib and my /usr not being mounted at boot, I doub with its actual config apparmor hs any chnce to work (copied the lib in /lib and did a ldconfig to manage to boot but still...) -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 12/01/2014 12:58 PM, Martin Pitt wrote: > Hello Eric, > > Eric Valette [2014-12-01 10:11 +0100]: >> After fixing the libapparmor in /usr bug, I managed to boot but kdm was >> not started. loging as root and using startx lauch a session without >> problem where I have mouse. Loggin as a normal user via startx breaks >> mouse and keyboard. > > Please show me the output of > > systemctl status -l kdm.service > > (as root) to see what's going wrong. It might be named slightly > differently -- check "systemctl --failed" for which units didn't > start, kdm should be amongst them. > >> Does apparmor mandate new kernel configuration? New user space setup? > > No, that should be unrelated. If AppArmor isn't available it won't be > used, unless you have a unit with AppArmorProfile=. X server stop voluntarily without any obvious error message (I have an (EE) at the end). Will do the trace when back home but frankly reinstalling before the /usr/lib vs /lib is fixed is annoying. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771652: systemd: system 217 breaks config not using initrd and /usr and / different
On 12/01/2014 12:55 PM, Martin Pitt wrote: > Hello Eric, > > Eric Valette [2014-12-01 10:06 +0100]: >> After upgrading to 217, I had a crash because init was unable to load >> libapparmor1. After seraching it is located in /usr that in my system >> is not yet mounted. >> >> copying manually libraries to /lib solves the boot problem (but still breaks >> X11/kde) > > Argh, indeed. I filed https://bugs.debian.org/771667 about this, > asking for moving the library to /lib. Until that I'll disable this in > Debian again. At least rise the severity to critical now ;-) -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 01/12/2014 15:08, Martin Pitt wrote: Hello again, Eric Valette [2014-12-01 10:11 +0100]: After fixing the libapparmor in /usr bug, I managed to boot but kdm was not started. This is most likely due to Didier's new generator to read /etc/X11/default-display-manager and only start that one. What does that file contain on your system? more /etc/X11/default-display-manager /usr/bin/kdm --eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 08:16, Didier Roche wrote: Do you mind showing the output (as root) of: systemctl status kdm.service systemctl status display-manger.service I think you are chasing a ghost: even if I log in and restart kdm manually I get no X. And downgrading does solve the problem. Attached is the Xorg.0.log with systemd 215 and Xorg.0.log.ko with 217 . [13.027] _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 [13.027] _XSERVTransOpen: transport open failed for inet6/tri-yann4:0 [13.027] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 [13.029] X.Org X Server 1.16.1.901 (1.16.2 RC 1) Release Date: 2014-11-02 [13.029] X Protocol Version 11, Revision 0 [13.029] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian [13.029] Current Operating System: Linux tri-yann4 3.17.4 #14 SMP PREEMPT Sat Nov 22 10:02:43 CET 2014 x86_64 [13.029] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.17.4 root=/dev/sdb5 ro rootfstype=ext4 memmap=4K$0x00031db35000 quiet [13.029] Build Date: 03 November 2014 09:44:08PM [13.029] xorg-server 2:1.16.1.901-1 (http://www.debian.org/support) [13.029] Current version of pixman: 0.32.6 [13.029]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [13.029] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [13.029] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 2 08:39:39 2014 [13.030] (==) Using config file: "/etc/X11/xorg.conf" [13.030] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [13.032] (==) ServerLayout "Default Layout" [13.032] (**) |-->Screen "Screen0" (0) [13.032] (**) | |-->Monitor "Monitor0" [13.032] (**) | |-->Device "Device0" [13.032] (**) |-->Input Device "Keyboard0" [13.032] (**) |-->Input Device "Logitech USB Receiver" [13.032] (**) Option "Xinerama" "0" [13.032] (==) Automatically adding devices [13.032] (==) Automatically enabling devices [13.032] (==) Automatically adding GPU devices [13.041] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [13.041] (==) ModulePath set to "/usr/lib/xorg/modules" [13.041] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [13.041] (WW) Disabling Keyboard0 [13.041] (II) Loader magic: 0x7f0d8e6f7d80 [13.041] (II) Module ABI versions: [13.041]X.Org ANSI C Emulation: 0.4 [13.041]X.Org Video Driver: 18.0 [13.041]X.Org XInput driver : 21.0 [13.041]X.Org Server Extension : 8.0 [13.041] (II) xfree86: Adding drm device (/dev/dri/card0) [13.044] (--) PCI:*(0:1:0:0) 10de:1189:10b0:1189 rev 161, Mem @ 0xfa00/16777216, 0xf000/134217728, 0xf800/33554432, I/O @ 0xe000/128, BIOS @ 0x/524288 [13.045] (II) LoadModule: "glx" [13.047] (II) Loading /usr/lib/xorg/modules/linux/libglx.so [13.157] (II) Module glx: vendor="NVIDIA Corporation" [13.157]compiled for 4.0.2, module version = 1.0.0 [13.157]Module class: X.Org Server Extension [13.158] (II) NVIDIA GLX Module 343.22 Thu Sep 11 15:55:13 PDT 2014 [13.159] (II) LoadModule: "nvidia" [13.160] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so [13.169] (II) Module nvidia: vendor="NVIDIA Corporation" [13.169]compiled for 4.0.2, module version = 1.0.0 [13.169]Module class: X.Org Video Driver [13.170] (II) LoadModule: "evdev" [13.171] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [13.178] (II) Module evdev: vendor="X.Org Foundation" [13.178]compiled for 1.16.0, module version = 2.9.0 [13.178]Module class: X.Org XInput Driver [13.178]ABI class: X.Org XInput driver, version 21.0 [13.178] (II) NVIDIA dlloader X Driver 343.22 Thu Sep 11 15:34:47 PDT 2014 [13.178] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [13.179] (++) using VT number 7 [13.191] (II) Loading sub module "fb" [13.191] (II) LoadModule: "fb" [13.191] (II) Loading /usr/lib/xorg/modules/libfb.so [13.194] (II) Module fb: vendor="X.Org Foundation" [13.194]compiled for 1.16.1.901, module version = 1.0.0 [13.194]ABI class: X.Org ANSI C Emulation, version 0.4 [13.194] (II) Loading sub module "wfb" [13.194] (II) LoadModule: "wfb" [13.195] (II) Loading /usr/lib/xorg/modules/libwfb.so [13.197] (II) Module wfb: vendor="X.Org Foundation" [13.197]compiled for 1.16.1.901, module version
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them from console :-() -- eric ● kdm.service Loaded: masked (/dev/null) Active: inactive (dead) Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended. ● display-manager.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 09:01, Eric Valette wrote: On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them from console :-() -- eric The reload message seems to imply that the kdm.service is generated too late for the system (my system is high end quadri core (8 cpus) I7 16G RAM, fast ssd). For the display-manager.service not found, I have no clue except if you gave me a wrong name. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 09:13, Didier Roche wrote: anks! Are you really sure that /etc/X11/default-display-manager exists on this machine (you didn't paste from any other) and points to a kdm binary? Yes. Double checked! cat /etc/X11/default-display-manager /usr/bin/kdm valette@tri-yann4:~$ type /usr/bin/kdm /usr/bin/kdm est /usr/bin/kdm valette@tri-yann4:~$ file /usr/bin/kdm /usr/bin/kdm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=e0e10507ede6d64eab115388829af4e23f8938c5, stripped If so, do you mind if I give you a debug version of a binary (you can revert to previous systemd meanwhile), so that I can get the needed informations to know what happens (I would need to know your machine architecture then). Note that /usr is not mounted at the beginning of the boot for me (no initrd, and / and /usr on a diffrent file system) -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 12/02/2014 09:32 AM, Didier Roche wrote: > Ok, everything looks fine. I doubt about the /usr separation to be the > cause for that one as the generator doesn't use any file there. > > Last try before sending you a debug binary: > cat -e /etc/X11/default-display-manager > > (even if I treat trailing spaces, \n and so on, let's see…) > > and: > ls -l /etc/systemd/system/ > ls -l /run/systemd/generator* Will do but must wait until I'm back home. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 09:32, Didier Roche wrote: Ok, everything looks fine. I doubt about the /usr separation to be the cause for that one as the generator doesn't use any file there. Last try before sending you a debug binary: cat -e /etc/X11/default-display-manager (even if I treat trailing spaces, \n and so on, let's see…) and: ls -l /etc/systemd/system/ ls -l /run/systemd/generator* Find attached. Note you don't see the command only the result. Tell me if you want something else/more --eric /usr/bin/kdm$ total 28 lrwxrwxrwx 1 root root 40 déc. 8 2013 dbus-org.freedesktop.Avahi.service -> /lib/systemd/system/avahi-daemon.service drwxr-xr-x 2 root root 4096 août 25 08:57 getty.target.wants drwxr-xr-x 2 root root 4096 mars 20 2014 local-fs.target.wants drwxr-xr-x 2 root root 4096 nov. 17 19:27 multi-user.target.wants drwxr-xr-x 2 root root 4096 nov. 9 11:03 paths.target.wants drwxr-xr-x 2 root root 4096 févr. 25 2014 printer.target.wants drwxr-xr-x 2 root root 4096 oct. 18 10:29 shutdown.target.wants drwxr-xr-x 2 root root 4096 août 29 17:21 sockets.target.wants lrwxrwxrwx 1 root root 31 mars 6 2014 sshd.service -> /lib/systemd/system/ssh.service lrwxrwxrwx 1 root root 35 juin 28 2013 syslog.service -> /lib/systemd/system/rsyslog.service /run/systemd/generator: total 52 -rw-r--r-- 1 root root 220 déc. 2 18:52 dev-disk-by\x2duuid-b27f8ff4\x2dab80\x2d459b\x2dadc4\x2df4b3aae3ad0f.swap -rw-r--r-- 1 root root 388 déc. 2 18:52 home.mount -rw-r--r-- 1 root root 376 déc. 2 18:52 home-valette-local.mount drwxr-xr-x 2 root root 60 déc. 2 18:52 hwclock.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 kdm.service.d drwxr-xr-x 2 root root 200 déc. 2 18:52 local-fs.target.requires drwxr-xr-x 2 root root 60 déc. 2 18:52 local-fs.target.wants -rw-r--r-- 1 root root 236 déc. 2 18:52 media-backup.mount -rw-r--r-- 1 root root 221 déc. 2 18:52 media-cdrom0.mount -rw-r--r-- 1 root root 268 déc. 2 18:52 -.mount drwxr-xr-x 2 root root 60 déc. 2 18:52 mountall-bootclean.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 mountall.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 mountnfs-bootclean.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 mountnfs.service.d -rw-r--r-- 1 root root 289 déc. 2 18:52 multimedia.mount drwxr-xr-x 2 root root 60 déc. 2 18:52 multi-user.target.wants drwxr-xr-x 2 root root 60 déc. 2 18:52 networking.service.d drwxr-xr-x 2 root root 40 déc. 2 18:52 openvpn.service.wants drwxr-xr-x 2 root root 60 déc. 2 18:52 remote-fs.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 rpcbind.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 rpcbind.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 sendsigs.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 swap.target.wants drwxr-xr-x 2 root root 60 déc. 2 18:52 umountfs.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 umountnfs.service.d -rw-r--r-- 1 root root 408 déc. 2 18:52 usr-local.mount -rw-r--r-- 1 root root 384 déc. 2 18:52 usr.mount -rw-r--r-- 1 root root 408 déc. 2 18:52 var-cache.mount -rw-r--r-- 1 root root 384 déc. 2 18:52 var.mount -rw-r--r-- 1 root root 273 déc. 2 18:52 windowsData.mount -rw-r--r-- 1 root root 268 déc. 2 18:52 windows.mount drwxr-xr-x 2 root root 80 déc. 2 18:52 x-display-manager.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 xdm.service.d drwxr-xr-x 2 root root 80 déc. 2 18:52 x-font-server.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 xfs.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 xfstt.service.d /run/systemd/generator.early: total 0 lrwxrwxrwx 1 root root 9 déc. 2 18:52 kdm.service -> /dev/null lrwxrwxrwx 1 root root 9 déc. 2 18:52 xdm.service -> /dev/null /run/systemd/generator.late: total 180 -rw-r--r-- 1 root root 632 déc. 2 18:52 apache2.service -rw-r--r-- 1 root root 447 déc. 2 18:52 console-screen.service -rw-r--r-- 1 root root 510 déc. 2 18:52 console-setup.service -rw-r--r-- 1 root root 525 déc. 2 18:52 cpufrequtils.service -rw-r--r-- 1 root root 483 déc. 2 18:52 etc-setserial.service -rw-r--r-- 1 root root 725 déc. 2 18:52 exim4.service -rw-r--r-- 1 root root 532 déc. 2 18:52 gdomap.service -rw-r--r-- 1 root root 500 déc. 2 18:52 gpm.service -rw-r--r-- 1 root root 456 déc. 2 18:52 hdparm.service -rw-r--r-- 1 root root 389 déc. 2 18:52 kbd.service -rw-r--r-- 1 root root 601 déc. 2 18:52 kdm.service -rw-r--r-- 1 root root 531 déc. 2 18:52 keyboard-setup.service -rw-r--r-- 1 root root 446 déc. 2 18:52 keymap.service -rw-r--r-- 1 root root 537 déc. 2 18:52 lirc.service -rw-r--r-- 1 root root 514 déc. 2 18:52 loadcpufreq.service -rw-r--r-- 1 root root 503 déc. 2 18:52 lpd.service -rw-r--r-- 1 root root 449 déc. 2 18:52 minidlna.dpkg-dist.service -rw-r--r-- 1 root root 636 déc. 2 18:52 mysql.service -rw-r--r-- 1 root root 538 déc. 2 18:52 networking.service -rw-r--r-- 1 root root 497 déc. 2 18:52 nfs-common.service -rw-r--r-- 1 root root 633 déc. 2 18:52 nf
Bug#864524: e2guardian: Please package e2guardian 4.1.0 which is rewrite in c++
Package: e2guardian Version: 3.4.0.3-1 Severity: wishlist See https://github.com/e2guardian/e2guardian/releases -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.31 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages e2guardian depends on: ii adduser 3.115 pn clamav ii libc6 2.24-11 ii libgcc1 1:6.3.0-18 ii libpcre32:8.39-3 ii libstdc++6 6.3.0-18 ii perl5.24.1-3 ii zlib1g 1:1.2.8.dfsg-5 e2guardian recommends no packages. Versions of packages e2guardian suggests: pn clamav-freshclam pn squid
Bug#865543: digikam: Please package digikam 5.6
Package: digikam Version: 4:5.3.0-1 Severity: wishlist See : https://www.digikam.org/news/2017-06-21-5.6.0-release-announcement/ -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.33 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages digikam depends on: ii digikam-data 4:5.3.0-1 ii digikam-private-libs 4:5.3.0-1 ii kipi-plugins 4:5.3.0-1 ii libc6 2.24-12 ii libgcc1 1:7.1.0-7 ii libkf5configcore5 5.28.0-2 ii libkf5coreaddons5 5.28.0-2 ii libkf5filemetadata3 5.28.0-1+b2 ii libkf5i18n5 5.28.0-2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5sql55.7.1+dfsg-3+b1 ii libqt5sql5-mysql 5.7.1+dfsg-3+b1 ii libqt5sql5-sqlite 5.7.1+dfsg-3+b1 ii libqt5widgets55.7.1+dfsg-3+b1 ii libstdc++67.1.0-7 ii perl 5.24.1-4 Versions of packages digikam recommends: ii ffmpegthumbs4:16.08.3-1 ii firefox-esr [www-browser] 52.2.0esr-1 ii google-chrome-stable [www-browser] 59.0.3071.109-1 ii konqueror [www-browser] 4:16.08.3-1 ii links2 [www-browser]2.14-2+b1 ii lynx [www-browser] 2.8.9dev14-2 ii w3m [www-browser] 0.5.3-34 Versions of packages digikam suggests: pn digikam-doc ii systemsettings 4:5.8.7-1 -- no debconf information
debian-bugs-dist@lists.debian.org
Package: ktorrent Version: 5.1.0-2 Severity: normal Here is a sample of what I get on konsole when starting via ktorrent & ven. sept. 15 19:22:24 2017: Initiating connection to 90.76.245.215 via (TCP) ven. sept. 15 19:22:24 2017: PEX: found 5 peers ven. sept. 15 19:22:24 2017: Chunk 8020 downloaded ven. sept. 15 19:22:24 2017: Chunk 5497 downloaded ven. sept. 15 19:22:24 2017: Chunk 1097 downloaded ven. sept. 15 19:22:24 2017: Chunk 7685 downloaded ven. sept. 15 19:22:25 2017: Chunk 8081 downloaded ven. sept. 15 19:22:25 2017: Chunk 3633 downloaded ven. sept. 15 19:22:25 2017: Chunk 2628 downloaded ven. sept. 15 19:22:25 2017: Chunk 5087 downloaded ven. sept. 15 19:22:25 2017: Chunk 1871 downloaded ven. sept. 15 19:22:26 2017: Chunk 1883 downloaded ven. sept. 15 19:22:26 2017: Chunk 2947 downloaded ven. sept. 15 19:22:26 2017: Chunk 3928 downloaded ven. sept. 15 19:22:26 2017: Request timed out 5298 16384 16384 µTorrent 3.4.2 ven. sept. 1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.50 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ktorrent depends on: ii kio5.37.0-2 ii ktorrent-data 5.1.0-2 ii libc6 2.25-0experimental3 ii libgcc11:7.2.0-4 ii libgeoip1 1.6.11-2 ii libkf5archive5 5.37.0-2 ii libkf5completion5 5.37.0-2 ii libkf5configcore5 5.37.0-2 ii libkf5configgui5 5.37.0-2 ii libkf5configwidgets5 5.37.0-2 ii libkf5coreaddons5 5.37.0-2 ii libkf5crash5 5.37.0-2 ii libkf5dbusaddons5 5.37.0-2 ii libkf5dnssd5 5.37.0-2 ii libkf5i18n55.37.0-2 ii libkf5iconthemes5 5.37.0-2 ii libkf5itemviews5 5.37.0-2 ii libkf5kcmutils55.37.0-2 ii libkf5kiocore5 5.37.0-2 ii libkf5kiofilewidgets5 5.37.0-2 ii libkf5kiowidgets5 5.37.0-2 ii libkf5krosscore5 5.37.0-2 ii libkf5notifications5 5.37.0-2 ii libkf5notifyconfig55.37.0-2 ii libkf5parts5 5.37.0-2 ii libkf5plotting55.37.0-2 ii libkf5service-bin 5.37.0-2 ii libkf5service5 5.37.0-2 ii libkf5syndication5 16.04.2-1 ii libkf5textwidgets5 5.37.0-2 ii libkf5torrent6 2.1-2 ii libkf5webkit5 5.37.0-2 ii libkf5widgetsaddons5 5.37.0-2 ii libkf5windowsystem55.37.0-2 ii libkf5xmlgui5 5.37.0-2 ii libktorrent-l10n 2.1-2 ii libphonon4qt5-44:4.9.1-1 ii libqt5core5a 5.9.1+dfsg-9 ii libqt5dbus55.9.1+dfsg-9 ii libqt5gui5 5.9.1+dfsg-9 ii libqt5network5 5.9.1+dfsg-9 ii libqt5webkit5 5.212.0~alpha2-1 ii libqt5widgets5 5.9.1+dfsg-9 ii libqt5xml5 5.9.1+dfsg-9 ii libstdc++6 7.2.0-4 ii libtag1v5 1.11.1+dfsg.1-0.1 ii phonon4qt5 4:4.9.1-1 ktorrent recommends no packages. Versions of packages ktorrent suggests: ii geoip-database 20170912-1 ii krosspython 4:16.08.0-1 -- no debconf information
Bug#876070: libavahi-core7: Does not install
Package: libavahi-core7 Version: 0.7-1 Severity: grave Justification: renders package unusable apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libavahi-core7 The following packages will be upgraded: libavahi-core7 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 33 not fully installed or removed. Need to get 0 B/114 kB of archives. After this operation, 3072 B disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 147923 files and directories currently installed.) Preparing to unpack .../libavahi-core7_0.7-1_amd64.deb ... Unpacking libavahi-core7:amd64 (0.7-1) over (0.6.32-2) ... dpkg: error processing archive /var/cache/apt/archives/libavahi-core7_0.7-1_amd64.deb (--unpack): unable to install (supposed) new info file '/var/lib/dpkg/tmp.ci/shlibs': Structure needs cleaning Errors were encountered while processing: /var/cache/apt/archives/libavahi-core7_0.7-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.50 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libavahi-core7 depends on: ii libavahi-common3 0.7-1 ii libc6 2.25-0experimental3 libavahi-core7 recommends no packages. libavahi-core7 suggests no packages. -- no debconf information
Bug#876070: My bad : the var file system was indeed broken. Bug can be closed
I never saw this message before either... And creating the failing file manually was possible. But a e2fsck -f -y DEV(/var) was indeed necessary. And after that package did install correctly. -- eric
Bug#871629: confirmed here also
Used several theme including default one : no chnage. Unusable... --eric
Bug#845640: Nvidia released 340.101 today with Xorg 1.19 support
See http://www.nvidia.com/download/driverResults.aspx/112998/en-us -- eric
Bug#841500: gcc-6: Unable to compile upstream kernel with previous .config
On Thu, 27 Oct 2016 06:25:00 + Niels Thykier wrote: Control: forcemerge 841438 841500 Hi Eric, Sorry to hear you ran into issues with gcc-6. On Fri, 21 Oct 2016 10:40:47 +0200 Eric Valette wrote: > [...] > > Entering directory '/usr/src/linux-dell' > GEN ./Makefile > scripts/kconfig/conf --oldconfig Kconfig > # > # configuration written to .config > # > [...] > /usr/src/linux-4.4/scripts/mod/empty.c:1:0: error: code model kernel does not support PIC mode This error suggests that your issue is a duplicate of #841419, which is that the compiler enables PIE by default (which is basically a variant of PIC). I have merged your bug into #841419 accordingly. I believe it is possible to compile the kernel with gcc-5. I hope you will consider that an acceptable workaround for you in the interim while we solve #841419. I have reverted to 6.2.0-6 anyway using testing as a source for the gcc package. But that will work as long as the "broken for kernel" gcc does not enter testing. So please find a way to prevent this compiler entering testing until this is resolved. Downloading from shapshots is way more painfull. And I wuld also like to know if various stacprotector options are broken for other user space or not because many people use this for hardening critical apps. If it is a problem, grave for security reason should stay. Ther are indeed two bugs (stackprotector and pie) to solve. But as fixing thsi properly requires upstream fixes, that could have been done for long if other distro have already switched, I'm dubious this will be fixed anytime soon, especially because the same flaw of bugs have already happened for Ubuntu and nothing changed. -- eric
Bug#841500: gcc-6: Unable to compile upstream kernel with previous .config
On Thu, 27 Oct 2016 01:23:14 -0700 Andres Freund wrote:
On 2016-10-27 06:25:00 +, Niels Thykier wrote:
> I believe it is possible to compile the kernel with gcc-5. I hope you
> will consider that an acceptable workaround for you in the interim while
> we solve #841419.
It's quite possible to compile the kernel with a newer gcc as well, you
just need to add the necessary CFLAGs. In my build script I've adjusted
things to:
time make -j8 KCPPFLAGS="-fno-pic -Wno-pointer-sign"
and the kernel compiles and runs normally again.
Thanks.
Does this patch solve also the stack-protector compilation issue? And
why is -Wno-pointer-sign needed?
Attached is the upstream currently proposed patch (borrowed from LKML).
WFM !
--eric
--- linux/Makefile~ 2016-10-27 21:59:02.777575151 +0200
+++ linux/Makefile 2016-10-27 22:00:46.014577729 +0200
@@ -615,6 +615,7 @@
ARCH_CFLAGS :=
include arch/$(SRCARCH)/Makefile
+KBUILD_CFLAGS += $(call cc-option,-fno-pie,)
KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks,)
KBUILD_CFLAGS += $(call cc-disable-warning,maybe-uninitialized,)
--- linux/scripts/gcc-x86_64-has-stack-protector.sh~2016-06-24
19:18:38.0 +0200
+++ linux/scripts/gcc-x86_64-has-stack-protector.sh 2016-10-27
22:01:36.685581816 +0200
@@ -1,6 +1,6 @@
#!/bin/sh
-echo "int foo(void) { char X[200]; return 3; }" | $* -S -x c -c -O0
-mcmodel=kernel -fstack-protector - -o - 2> /dev/null | grep -q "%gs"
+echo "int foo(void) { char X[200]; return 3; }" | $* -S -x c -c -O0
-mcmodel=kernel -fno-pie -fstack-protector - -o - 2> /dev/null | grep -q "%gs"
if [ "$?" -eq "0" ] ; then
echo y
else
Bug#823330: I upgraded this morning to the fixed version and it does not work with my tsocks
I reinstalled the version I regenrated using the configure witout the --enable-hostnames and it works again. Did you check the patch is actually working? I just removed the --enable-hostnames from the configure command in debian/rules on my side. -- eric
Bug#845000: nvidia-graphics-drivers: Please package 375.20 in experimental
Source: nvidia-graphics-drivers Version: 370.28-1 Severity: wishlist The 375.20 officially supports Xorg 1.19 which landed in experimental already. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.32 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#845000: nvidia-graphics-drivers: Please package 375.20 in experimental
On 19/11/2016 12:21, Luca Boccassi wrote: On Sat, 2016-11-19 at 11:08 +0100, Eric Valette wrote: Source: nvidia-graphics-drivers Version: 370.28-1 Severity: wishlist The 375.20 officially supports Xorg 1.19 which landed in experimental already. Hi, (round bug number, whoo!) Did I win someting :-) As I wrote yesterday on the list it's being worked on and it's in SVN: https://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-November/013663.html There's the glvendorized EGL library to take care of, and basic testing. Good. Thanks for the info. -- eric
Bug#845690: Same problem here!
Screwed up my NAS updating the kernel. Kernel panic just after init. gcc : 6.2.1-1 kernel = upstream 4.4.35 reverting to my own compiled 4.4.33 fixed the problem. --eric
Bug#845690: Same problem here!
On Sat, 26 Nov 2016 21:50:37 +0100 Eric Valette wrote: Screwed up my NAS updating the kernel. Kernel panic just after init. gcc : 6.2.1-1 kernel = upstream 4.4.35 reverting to my own compiled 4.4.33 fixed the problem. Ooops gcc= 6.2.1-5 and kernel is x86-64 -- eric
Bug#846030: xserver-xorg-video-nvidia: Cannot be co-installed with unstable 1.19 (xserver-xorg-core (<< 2:1.18.99))
Package: xserver-xorg-video-nvidia Version: 375.20-1 Severity: important I did put xserver-xorg-core on hold because the nvidia driver was not ready. Now the driver is ready, but the Depends line forbids to co-install with unstable version. -- Package-specific info: uname -a: Linux tri-yann4 4.4.33 #38 SMP PREEMPT Sat Nov 19 17:54:40 CET 2016 x86_64 GNU/Linux /proc/version: Linux version 4.4.33 (valette@tri-yann4) (gcc version 6.2.1 20161118 (Debian 6.2.1-3) ) #38 SMP PREEMPT Sat Nov 19 17:54:40 CET 2016 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 370.28 Thu Sep 1 19:45:04 PDT 2016 GCC version: gcc version 6.2.1 20161118 (Debian 6.2.1-3) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology GK104 [GeForce GTX 670] [10b0:1189] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia_current_drm, nvidia_current dmesg: [0.00] Console: colour VGA+ 80x25 [0.266309] vgaarb: setting as boot device: PCI::01:00.0 [0.266310] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.266315] vgaarb: loaded [0.266316] vgaarb: bridge control possible :01:00.0 [0.359878] Linux agpgart interface v0.103 [1.048686] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input3 [1.048890] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input4 [1.049041] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input5 [1.049163] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci:00/:00:02.0/:01:00.1/sound/card1/input6 [2.424642] nvidia: module license 'NVIDIA' taints kernel. [2.443322] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [2.443414] nvidia-nvlink: Nvlink Core is being initialized, major device number 247 [2.443444] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 370.28 Thu Sep 1 19:45:04 PDT 2016 [2.450374] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 370.28 Thu Sep 1 19:18:48 PDT 2016 [2.451517] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver [ 20.146415] nvidia-modeset: Allocated GPU:0 (GPU-3ae49403-ead2-114d-863b-ff3072d039b6) @ PCI::01:00.0 Device node permissions: crw-rw+ 1 root video 226, 0 Nov 27 18:58 /dev/dri/card0 crw-rw+ 1 root video 226, 128 Nov 27 18:58 /dev/dri/renderD128 crw-rw-rw- 1 root root 195, 254 Nov 27 18:58 /dev/nvidia-modeset crw-rw-rw- 1 root root 195, 0 Nov 27 18:58 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Nov 27 18:58 /dev/nvidiactl video:x:44:valette,vdr,hts,sddm OpenGL and NVIDIA library files installed: -rw-r--r-- 1 valette valette 1722 Aug 20 2014 /etc/X11/xorg.conf lrwxrwxrwx 1 rootroot 15 Nov 28 00:11 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 rootroot 49 Mar 30 2016 /etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so lrwxrwxrwx 1 rootroot 44 Nov 28 00:11 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1 lrwxrwxrwx 1 rootroot 48 Mar 30 2016 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 rootroot 48 Mar 30 2016 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 rootroot 43 Nov 28 00:11 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 rootroot 43 Nov 28 00:11 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 rootroot 50 Nov 28 00:11 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 rootroot 50 Nov 28 00:11 /etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1 lrwxrwxrwx 1 rootroot 47 Nov 28 00:11 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 rootroot 47 Nov 28 00:11 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2 lrwxrwxrwx 1 rootroot 51 Nov 28 00:11 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu
Bug#839995: g++-6: g++6 fails to compile files that include /usr/include/c++/6/bits/locale_conv.h
Package: g++-6 Version: 6.2.0-5 Severity: important Tags: upstream Dear Maintainer, Trying to compile libgtop11dotnet-2.2.0.12 for a gemalto pki, i have a build error that has nothing to do with the packages itself but with the content of /usr/include/c++/6/bits/locale_conv.h and especially the __out temporary variable used in some of its inline. It is not related to libgtop11dotnet-2.2.0.13 code epr se as I have found complains for the same problem on various c++ code with g++ 6. I will attach a standalone file that shows the problem and a possible fix. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.23 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages g++-6 depends on: ii gcc-66.2.0-5 ii gcc-6-base 6.2.0-5 ii libc62.24-3 ii libgmp10 2:6.1.1+dfsg-1 ii libisl15 0.17.1-1 ii libmpc3 1.0.3-1 ii libmpfr4 3.1.5-1 ii libstdc++-6-dev 6.2.0-5 ii zlib1g 1:1.2.8.dfsg-2+b1 g++-6 recommends no packages. Versions of packages g++-6 suggests: pn g++-6-multilib pn gcc-6-doc pn libstdc++6-6-dbg -- no debconf information
Bug#834359: This bug is gone for me with kwin 5.8.0
It could probably be closed if others affected and migrated confirm. -- eric
Bug#797999: We are now more than one year later and this critical bug is not fixed
On 10/10/2016 11:48 AM, Maximiliano Curia wrote: What happens if you use the maui sddm theme? The same : a black screen with external monitor led going off. If I press ctlr-alt-f1, led goes back up and I can login on console. I switch back to kdm via dpkg-reconfigure and reboot. kdm knows how to proceed with external monitor when sddm does not. Period. So its a bug that for me render sddm totally unusable. xrandr (once launched via kdm) Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 connected (normal left inverted right x axis y axis) 1440x900 59.96 + 39.96 DP-4 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 59.88 1920x1080 60.00 59.94 50.00 23.97 60.05 60.00 50.04 1600x1200 60.00 1280x1024 75.02 60.02 1280x720 60.00 59.94 50.00 1152x864 75.00 1024x768 75.03 60.00 800x600 75.00 60.32 720x576 50.00 50.08 720x480 59.94 60.05 640x480 75.00 59.94 59.93 # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 295.20 (pbuilder@cake) Wed Feb 15 20:18:16 UTC 2012 # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 (buildmeister@builder75) Fri Mar 12 01:42:27 PST 2010 Section "ServerLayout" #InputDevice"Mouse0" "CorePointer" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "SendCoreEvent" Option "Xinerama" "0" #Option"AutoAddDevices" "false" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "evdev" Option "Name" "CHICONY HP Basic USB Keyboard" #Option"Device" "/dev/input/by-id/usb-CHICONY_HP_Basic_USB_Keyboard-event-kbd" EndSection Section "InputClass" Identifier "touchpad catchall" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Driver "synaptics" Option "LeftEdge" "100" Option "RightEdge" "1750" Option "TopEdge""100" Option "BottomEdge" "1250" Option "FingerLow" "12" Option "FingerHigh" "14" Option "FingerPress""127" Option "MaxTapTime" "180" Option "MaxTapMove" "107" Option "MaxDoubleTapTime" "180" Option "SingleTapTimeout" "180" Option "ClickTime" "100" Option "FastTaps" "0" Option "EmulateMidButtonTime" "75" Option "EmulateTwoFingerMinZ" "139" Option "EmulateTwoFingerMinW" "7" Option "VertScrollDelta""44" Option "HorizScrollDelta" "44" Option "VertEdgeScroll" "1" Option "HorizEdgeScroll""1" Option "CornerCoasting" "0" Option "VertTwoFingerScroll""0" Option "HorizTwoFingerScroll" "0" Option "MinSpeed" "1" Option "MaxSpeed" "1.75" Option "AccelFactor""0.0075" Option "TrackstickSpeed"
Bug#797999: We are now more than one year later and this critical bug is not fixed
On 10/10/2016 01:43 PM, Maximiliano Curia wrote: ¡Hola Eric! El 2016-10-10 a las 13:22 +0200, Eric Valette escribió: The same : a black screen with external monitor led going off. If I press ctlr-alt-f1, led goes back up and I can login on console. I switch back to kdm via dpkg-reconfigure and reboot. Interesting. kdm knows how to proceed with external monitor when sddm does not. Period. So its a bug that for me render sddm totally unusable. kdm and sddm are completely different beasts, but afaik neither have specific code for handling an external monitor. Also, this nagging about kdm is not productive, if you don't care about working on this issue, please switch to a different display manager. When you say its a bug in the nvidia driver that is also counter productive and annoying for me because without external monitor, the same drivers, same version same everything (except as said external monitor) works well with sddm on other laptop. I use kdm example just to say that the driver is not at fault. I just want to have sddm working but see no progress and on my side, there is not much I can do as I have no graphical environment at all as soon as I switch to sddm as a launcher. xrandr (once launched via kdm) Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 connected (normal left inverted right x axis y axis)1440x900 59.96 + 39.96 DP-4 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm1920x1200 59.95*+ 59.88 1920x1080 60.0059.9450.0023.9760.0560.00 50.04 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.0050.08 720x480 59.9460.05 640x480 75.0059.9459.93 It would be interesting to compare it with the xrandr report of a running sddm. I cant' : I probably have no X session running. I have a black screen remember... Can try specifying display explicitly on console. Can try to open the lid to see if anything is there but I doubt. -- eric
Bug#797999: We are now more than one year later and this critical bug is not fixed
On 10/10/2016 01:43 PM, Maximiliano Curia wrote: ¡Hola Eric! It would be interesting to compare it with the xrandr report of a running sddm. I did this in the meantime : cut -c14- /var/log/Xorg.0.log.old > failing_Xorg.0.log cut -c14- /var/log/Xorg.0.log > working_Xorg.0.log Just to surpsed the timing information: diff working_Xorg.0.log failing_Xorg.0.log Will double check the file /var/log/Xorg.0.log.old was really created when failing... > (--) Log file renamed from "/var/log/Xorg.pid-1448.log" to "/var/log/Xorg.0.log" 16c17 < (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 10 13:09:42 2016 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 10 13:04:16 2016 48c49 < (II) Loader magic: 0x55e29c553dc0 --- > (II) Loader magic: 0x5608e2a4adc0 279c280 < (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event10) --- > (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event8) 282c283 < (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event11) --- > (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event9) 285c286 < (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event12) --- > (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event6) 288c289 < (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13) --- > (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event7) 330c331 < (II) config/udev: Adding input device HDA Intel MID Dock Line Out (/dev/input/event8) --- > (II) config/udev: Adding input device HDA Intel MID Dock Mic (/dev/input/event10) 333c334 < (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event9) --- > (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event11) 336c337 < (II) config/udev: Adding input device HDA Intel MID Dock Mic (/dev/input/event6) --- > (II) config/udev: Adding input device HDA Intel MID Dock Line Out (/dev/input/event12) 339c340 < (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event7) --- > (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event13) 473a475,491 > (II) UnloadModule: "synaptics" > (II) evdev: AlpsPS/2 ALPS DualPoint Stick: Close > (II) UnloadModule: "evdev" > (II) evdev: AT Translated Set 2 keyboard: Close > (II) UnloadModule: "evdev" > (II) evdev: Logitech Logitech USB Optical Mouse: Close > (II) UnloadModule: "evdev" > (II) evdev: CHICONY HP Basic USB Keyboard: Close > (II) UnloadModule: "evdev" > (II) evdev: Sleep Button: Close > (II) UnloadModule: "evdev" > (II) evdev: Power Button: Close > (II) UnloadModule: "evdev" > (II) evdev: Power Button: Close > (II) UnloadModule: "evdev" > (II) NVIDIA(GPU-0): Deleting GPU-0 > (II) Server terminated successfully (0). Closing log file.
Bug#797999: We are now more than one year later and this critical bug is not fixed
On 10/10/2016 02:02 PM, Eric Valette wrote: On 10/10/2016 01:43 PM, Maximiliano Curia wrote: ¡Hola Eric! It would be interesting to compare it with the xrandr report of a running sddm. I did this in the meantime : cut -c14- /var/log/Xorg.0.log.old > failing_Xorg.0.log cut -c14- /var/log/Xorg.0.log > working_Xorg.0.log Just to surpsed the timing information: diff working_Xorg.0.log failing_Xorg.0.log Will double check the file /var/log/Xorg.0.log.old was really created when failing... Yes the Xorg.0.log is created and there is no difference compared to working one and DP4 is correctly selected with th correct resolution. Attached is the sddm log file when it fails I tried to do an xrandr on tty1 console using xranrd -d :0 but it fails both with sddm or kdm so I'm not sure how to have it. [14:31:11.090] (EE) GREETER: QXcbConnection: Could not connect to display :0 [14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/fvwm-crystal.desktop" [14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/fvwm.desktop" [14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop" [14:31:40.775] (II) GREETER: Reading from "/usr/share/xsessions/twm.desktop" [14:31:40.776] (II) GREETER: Reading from "/usr/share/xsessions/failsafe.desktop" [14:31:40.776] (EE) GREETER: Socket error: "QLocalSocket::connectToServer: Invalid name" [14:31:41.461] (WW) GREETER: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [14:34:19.417] (II) GREETER: Reading from "/usr/share/xsessions/fvwm-crystal.desktop" [14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/fvwm.desktop" [14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/plasma.desktop" [14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/twm.desktop" [14:34:19.418] (II) GREETER: Reading from "/usr/share/xsessions/failsafe.desktop" [14:34:19.418] (EE) GREETER: Socket error: "QLocalSocket::connectToServer: Invalid name" [14:34:19.998] (WW) GREETER: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [14:34:30.045] (II) GREETER: Reading from "/usr/share/xsessions/fvwm-crystal.desktop" [14:34:30.045] (WW) GREETER: QIODevice::write: device not open
Bug#797999: We are now more than one year later and this critical bug is not fixed
On 10/10/2016 02:50 PM, Maximiliano Curia wrote: ¡Hola Eric! El 2016-10-10 a las 13:54 +0200, Eric Valette escribió: I cant' : I probably have no X session running. I have a black screen remember... Can try specifying display explicitly on console. Can try to open the lid to see if anything is there but I doubt. After seeing the sddm blank screen switch to a tty (ctrl-alt-f2) and as root, or as the sddm user run: XAUTHORITY=/var/run/sddm/* DISPLAY=:0 xrandr It worked indeed. Result attached. Identical to kdm case 2 r-x-ceva6380:~->xrandr > xrandr_kdm 2>&1 3 r-x-ceva6380:~->diff xrandr_kdm xrandr_sddm 4 r-x-ceva6380:~-> Consistent with the fact that Xorg.0.log reports the same display and all nvidia traces are also identical beween kdm launch and sddm launch. So X selects correctly the right display (and I have the small drawing on the screen after switching X on that show a displayport icon as when I start kdm) before evrything goes dark and monitor led turns off. So I bet sddm or the sddm greeter greeter is at fault. What else can I do to help fixing? --eric Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 connected (normal left inverted right x axis y axis) 1440x900 59.96 + 39.96 DP-4 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 59.88 1920x1080 60.0059.9450.0023.9760.0560.0050.04 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.0050.08 720x480 59.9460.05 640x480 75.0059.9459.93
Bug#797999: We are now more than one year later and this critical bug is not fixed
On 10/11/2016 04:10 PM, Dominique Dumont wrote: On Monday, 10 October 2016 11:59:59 CEST eric2.vale...@orange.com wrote: First of all, the bug is not critical because it only affects a very specific setup for a particular video driver. A docked station using a nvidia driver is not that uncommon I guess... For the record, this setup is working on my system: my laptop has lid closed and the external screen is working (kde, sddm, nvidia driver) May be because I've manually swtiched off the laptop screen with "system settings", i.e. the screen was blank before I closed the lid. Could you try that on your side ? I can do the test but I never open the lid when docked so this will not be my use case and this means also modifying my xorg.conf. -- eric
Bug#797999: We are now more than one year later and this critical bug is not fixed
On 10/11/2016 04:22 PM, Eric Valette wrote: On 10/11/2016 04:10 PM, Dominique Dumont wrote: Could you try that on your side ? I can do the test but I never open the lid when docked so this will not be my use case and this means also modifying my xorg.conf. Once session is initialized with kdm, in system settings-> display and monitor, I have DP4 on at 1920x1200 (as reported by xrandr even when failing) and DP3 off. --eric
Bug#797999: more debug info
On 10/12/2016 10:57 AM, Eric Valette wrote: On 10/11/2016 04:22 PM, Eric Valette wrote: On 10/11/2016 04:10 PM, Dominique Dumont wrote: Could you try that on your side ? I can do the test but I never open the lid when docked so this will not be my use case and this means also modifying my xorg.conf. Once session is initialized with kdm, in system settings-> display and monitor, I have DP4 on at 1920x1200 (as reported by xrandr even when failing) and DP3 off. I tried to let the lid open with my actual xorg.conf and rebooted, both screen go black. I can still switch to laptop lid in text mode using ctrl-alt-f1. I loged to my accound, killed sddm service and did a startx, and the kde session shows up correctly on the external monitor and laptop screen goes black. Could you try to use nvidia-settings to disable your laptop screen, via the X Server Display Configuration menu and use save X configuration file (in /tmp/xorg.conf) back up you actual /etx/X11/xorg.conf if you have one and then replace your working dual screen conf by the /tmp/xorg.conf NB : actually the xorg.conf file generated is not perfect it misses the config for the second monitor, and still use the laptop screen identifier in the Screen section while adding the external monitor config dpkg -s nvidia-settings-legacy-340xx Package: nvidia-settings-legacy-340xx Status: install ok installed Priority: optional Section: contrib/x11 Installed-Size: 1861 Maintainer: Debian NVIDIA Maintainers Architecture: amd64 Version: 340.93-1 Depends: pkg-config, nvidia-legacy-340xx-alternative, libc6 (>= 2.14), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.12.0), libgtk2.0-0 (>= 2.8.0), libjansson4 (>= 2.3), libpango-1.0-0 (>= 1.14.0), libx11-6 (>= 2:1.4.99.1), libxext6, libxxf86vm1 Pre-Depends: nvidia-installer-cleanup Recommends: libgl1-nvidia-legacy-340xx-glx Breaks: nvidia-alternative (<< 313.30-2), nvidia-alternative-legacy-173xx (<< 173.14.37), nvidia-alternative-legacy-96xx (<< 96.43.23-4) Description: tool for configuring the NVIDIA graphics driver (340xx legacy version) The nvidia-settings utility is a tool for configuring the NVIDIA Linux graphics driver. It operates by communicating with the NVIDIA X driver, querying and updating state as appropriate. This communication is done with the NV-CONTROL X extension. . Values such as brightness and gamma, XVideo attributes, temperature, and OpenGL settings can be queried and configured via nvidia-settings. Homepage: ftp://download.nvidia.com/XFree86/nvidia-settings/
Bug#797999: more debug info
On 10/12/2016 11:44 AM, Eric Valette wrote: On 10/12/2016 10:57 AM, Eric Valette wrote: On 10/11/2016 04:22 PM, Eric Valette wrote: On 10/11/2016 04:10 PM, Dominique Dumont wrote: Could you try that on your side ? I can do the test but I never open the lid when docked so this will not be my use case and this means also modifying my xorg.conf. Once session is initialized with kdm, in system settings-> display and monitor, I have DP4 on at 1920x1200 (as reported by xrandr even when failing) and DP3 off. I tried to let the lid open with my actual xorg.conf and rebooted, both screen go black. I can still switch to laptop lid in text mode using ctrl-alt-f1. I loged to my accound, killed sddm service and did a startx, and the kde session shows up correctly on the external monitor and laptop screen goes black. I was in a meeting so undocked my laptop and by curiosity completely removed the xorg.conf and tried sddm. Even in this simpliest config it fails and the screen goes black after displaying the Nvidia logo (usually I use the No Logo option but as xorg.conf was empty). I got sddm errors in /var/run/sddm.log. It says the greeter can't open the display. So probably the problem is not the docking and the external monitor. Compared to other working setup with same software stack (legacy 340 nvidia driver), the only thing I can see that differs is the fact that the laptop lid is wired via DisplayPort versus HDMI. xrandr on this config when started via kdm Screen 0: minimum 8 x 8, current 1440 x 900, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 304mm x 190mm 1440x900 59.96*+ 39.96 DP-4 disconnected (normal left inverted right x axis y axis) --eric
Bug#836002: gupnp-tools: gupnp-av-cp.desktop is totally wrong (points to gupnp-universal-cp), wrong icons path, ...
Package: gupnp-tools Version: 0.8.12-1 Severity: important Have a lot at its content and see how wro,g it is. As a result, under KDE, you cannot find the application and the dektop icon just shows its name. No icons. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.19 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gupnp-tools depends on: ii libc6 2.24-0experimental1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-02.49.5-2 ii libgssdp-1.0-3 0.14.16-1 ii libgtk-3-0 3.21.4-1 ii libgtksourceview-3.0-1 3.21.5-1 ii libgupnp-1.0-4 0.20.18-1 ii libgupnp-av-1.0-2 0.12.8-2 ii libsoup2.4-12.54.1-1 ii libxml2 2.9.4+dfsg1-1+b1 gupnp-tools recommends no packages. gupnp-tools suggests no packages. -- no debconf information
Bug#836608: BTW clang 3.6 is the only thing that prevent me to remove gcc5 entirely from my system
So this also makes à lot of sens to avoid to use several gcc compiler. -- eric
Bug#834359: Libc6 2.24 is now default in unstable so question whether or not it is caused by this new version is not that relevant
As far as bug reproduction goes, I have systematic once crash when I launch thunderbird/icedove in two machines. Seems to be related to gtk application emulation as I never got it when launching kde apps. -- eric
Bug#834359: kwin-x11: Kwin crashes when launching thunderbird or firefox almost each time.
On 14/08/2016 22:00, Diederik de Haas wrote: On zondag 14 augustus 2016 21:29:22 CEST valette wrote: ii libc6 2.24-0experimental0 Does the problem also occur with libc6 from testing/sid? from backtrace it crashes with SIGSEGV qt5 qml somewhere so I would be surprised if it is relevant but can try although not now. --eric
Bug#841368: Same error here plus another one
Same problem with upstream kernel + "code model kernel does not support PIC mode" That is brand new. GEN ./Makefile scripts/kconfig/conf --silentoldconfig Kconfig arch/x86/Makefile:133: stack-protector enabled but compiler support broken /usr/src/linux-4.4/Makefile:668: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h HOSTCC scripts/basic/bin2c CHK include/config/kernel.release UPD include/config/kernel.release SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_32_ia32.h GEN ./Makefile SYSHDR arch/x86/entry/syscalls/../../include/generated/asm/unistd_64_x32.h WRAP arch/x86/include/generated/asm/clkdev.h WRAP arch/x86/include/generated/asm/cputime.h WRAP arch/x86/include/generated/asm/dma-contiguous.h WRAP arch/x86/include/generated/asm/early_ioremap.h WRAP arch/x86/include/generated/asm/mcs_spinlock.h WRAP arch/x86/include/generated/asm/mm-arch-hooks.h SYSTBL arch/x86/entry/syscalls/../../include/generated/asm/syscalls_64.h CHK include/generated/uapi/linux/version.h UPD include/generated/uapi/linux/version.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h HOSTCC scripts/genksyms/genksyms.o SYSHDR arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_x32.h SHIPPED scripts/genksyms/parse.tab.c CC scripts/mod/empty.o /usr/src/linux-4.4/scripts/mod/empty.c:1:0: error: code model kernel does not support PIC mode /* empty file to figure out endianness / word size */ /usr/src/linux-4.4/scripts/Makefile.build:258: recipe for target 'scripts/mod/empty.o' failed make[3]: *** [scripts/mod/empty.o] Error 1 /usr/src/linux-4.4/scripts/Makefile.build:403: recipe for target 'scripts/mod' failed
Bug#841438: This is agcc bug : upstream kernel irself fails to build with this gcc so reassigne to gcc-6
I never use debian kernel and connaot compile upstream kernel with gcc-6 now. --eric
Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
On 10/21/2016 01:45 AM, Konstantin Demin wrote: 2016-10-21 1:49 GMT+03:00 Ben Hutchings : It's a bug when a compiler fails to compile valid code. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. Dear Ben, there are no actual bug in compiler, just a caveat to work with it. Some time ago i had experience to build fully hardened nginx build, and I was forced to build shared libraries with -fPIC but not -fPIE due to linker errors. Solution was to separate build to executable only and shared-libraries only; this is semi-true: executable is successfully linked with -fPIC flag, but it's not used in packaging because of executable already built with -fPIE. This bug report is just another round of game with compiler/linker flags. In my turn, I would rather define protective flags to provide backward and forward compatibility. I disagree: you fix debian code but upstream kernel is also affected. I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. Please revert. -- eric
Bug#841500: gcc-6: Unable to compile upstream kernel with previous .config
Package: gcc-6 Version: 6.2.0-9 Severity: grave Justification: renders package unusable Wanted to patch my upstream kernel for the COW vulenraibilty. Applied incremental patch, started the rebuild with same .config: Entering directory '/usr/src/linux-dell' GEN ./Makefile scripts/kconfig/conf --oldconfig Kconfig # # configuration written to .config # make[1]: Leaving directory '/usr/src/linux-dell' make[1]: Entering directory '/usr/src/linux-dell' arch/x86/Makefile:133: stack-protector enabled but compiler support broken /usr/src/linux-4.4/Makefile:668: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler GEN ./Makefile scripts/kconfig/conf --silentoldconfig Kconfig arch/x86/Makefile:133: stack-protector enabled but compiler support broken /usr/src/linux-4.4/Makefile:668: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler CHK include/config/kernel.release GEN ./Makefile CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CC scripts/mod/empty.o /usr/src/linux-4.4/scripts/mod/empty.c:1:0: error: code model kernel does not support PIC mode /* empty file to figure out endianness / word size */ /usr/src/linux-4.4/scripts/Makefile.build:258: recipe for target 'scripts/mod/empty.o' failed make[3]: *** [scripts/mod/empty.o] Error 1 /usr/src/linux-4.4/scripts/Makefile.build:403: recipe for target 'scripts/mod' failed make[2]: *** [scripts/mod] Error 2 /usr/src/linux-4.4/Makefile:555: recipe for target 'scripts' failed make[1]: *** [scripts] Error 2 make[1]: Leaving directory '/usr/src/linux-dell' Makefile:150: recipe for target 'sub-make' failed make: *** [sub-make] Error 2 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.25 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages gcc-6 depends on: ii binutils 2.27-9 ii cpp-6 6.2.0-9 ii gcc-6-base6.2.0-9 ii libc6 2.24-5 ii libcc1-0 6.2.0-9 ii libgcc-6-dev 6.2.0-9 ii libgcc1 1:6.2.0-9 ii libgmp10 2:6.1.1+dfsg-1 ii libisl15 0.17.1-1 ii libmpc3 1.0.3-1 ii libmpfr4 3.1.5-1 ii libstdc++66.2.0-9 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages gcc-6 recommends: ii libc6-dev 2.24-5 Versions of packages gcc-6 suggests: pn gcc-6-doc pn gcc-6-locales pn gcc-6-multilib pn libasan3-dbg pn libatomic1-dbg pn libcilkrts5-dbg pn libgcc1-dbg pn libgomp1-dbg pn libitm1-dbg pn liblsan0-dbg pn libmpx2-dbg pn libquadmath0-dbg pn libtsan0-dbg pn libubsan0-dbg -- no debconf information
Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
On 10/21/2016 11:40 AM, Konstantin Demin wrote: I disagree: you fix debian code but upstream kernel is also affected. I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. Please revert. $ rmadison linux linux | 4.5.5-1 | unstable| source linux | 4.5.5-1 | unstable-debug | source linux | 4.6.4-1 | unstable| source linux | 4.6.4-1 | unstable-debug | source linux | 4.7.5-1~bpo8+2 | jessie-backports| source linux | 4.7.5-1 | unstable| source linux | 4.7.6-1 | testing | source linux | 4.7.8-1~bpo8+1 | buildd-jessie-backports | source linux | 4.7.8-1~bpo8+1 | jessie-backports| source linux | 4.7.8-1 | buildd-unstable | source linux | 4.7.8-1 | unstable| source linux | 4.7.8-1 | unstable-debug | source You should be noted that building kernel from vanilla source isn't good idea in Debian. Except I have been doing this for nearly 10 years... I don't see any 4.4 branch in Debian sources, but you may use git tag "debian/4.4.6-1" as base for your own work/fork. I'm not using debian kernel nor want to use them. I want a compiler able to compile upstream code without modifications. And I want LTS kernel to get fixes as soon as they appear without being forced to move to non LTS versions. -- eric
Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
On 21/10/2016 16:36, Ben Hutchings wrote: On Fri, 2016-10-21 at 12:40 +0300, Konstantin Demin wrote: I disagree: you fix debian code but upstream kernel is also affected. I wanted to compile the upstream 4.4.26 for the COW fixe and cannot. Please revert. It is absolutely supported (so long as you enable the necessary features) and is common practice. However, any bugs in some other version of the kernel should not be assigned to src:linux. Thanks Ben. BTW : I was originally arguing against the move to linux:src for a bug I opened on gcc because I was compiling upstream vanilla kernel code. (I never open a bug in linux:src as I barely use it except at first install). I also dislike, gcc advocates forcibly merging bugs people have discovered rebuilding debian kernel from source and bug discovered compiling upstream vanilla kernel from source not even flagging them "upstream". Nice game : they broke gcc with their patches (even if for possible good technical security reasons), and then, when bug are detected, even if bug report (like mine) explicitly specified upstream vanilla kernel code they reaffect it to linux:src asking for someone else to clean up the mess. I do think (like you wrote elsewhere) that fixing debian kernel build is not a solution: until the needed patches are applied upstream, tagged for stable and have been propagated to the various LTS kernel,theses patches needs to be reverted. -- eric
Bug#840841: No its no more installable
digikam-private-libs : Dépend: libmarblewidget-qt5-24 put now its at libmarblewidget-qt5-25 -- eric
Bug#841533: The problem is not only with the kernel : gcc testsuite have also multiple tests failing
So probably, the bug title should be changed : See: https://lists.debian.org/debian-gcc/2016/10/msg00156.html -- eric
Bug#841533: The problem is not only with the kernel : gcc testsuite have also multiple tests failing
On 25/10/2016 18:27, Matthias Klose wrote: On 24.10.2016 13:13, Eric Valette wrote: So probably, the bug title should be changed : See: https://lists.debian.org/debian-gcc/2016/10/msg00156.html no, unless you show that there are regressions. The GCC tests never completely pass. I was Reading the number of unexpected errors... -- eric
Bug#837883: mysql-server-5.7: Please upgrade to 5.7.15+ to fix recently discovered security issues
Package: mysql-server-5.7 Version: 5.7.13-1~exp1 Severity: grave Tags: upstream security Justification: user security hole CVE-2016-6662 -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.20 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mysql-server-5.7 depends on: ii adduser3.115 ii bsdutils 1:2.28.2-1 ii debconf [debconf-2.0] 1.5.59 ii init-system-helpers1.44 ii libc6 2.24-2 ii libgcc11:6.2.0-3 ii libmecab2 0.996-2 ii libstdc++6 6.2.0-3 ii lsb-base 9.20160629 ii mysql-client-5.7 5.7.13-1~exp1 ii mysql-common 5.8+1.0.0 ii mysql-server-core-5.7 5.7.13-1~exp1 ii passwd 1:4.2-3.1 ii perl 5.22.2-5 ii psmisc 22.21-2.1+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages mysql-server-5.7 recommends: ii libhtml-template-perl 2.95-2 Versions of packages mysql-server-5.7 suggests: ii bsd-mailx [mailx] 8.1.2-0.20160123cvs-3 ii s-nail [mailx] 14.8.10-1 pn tinyca -- debconf information: mysql-server-5.7/postrm_remove_databases: false mysql-server-5.7/start_on_boot: true mysql-server/no_upgrade_when_using_ndb: mysql-server-5.7/nis_warning: mysql-server-5.7/really_downgrade: false mysql-server/password_mismatch:
Bug#834359: The crash occurs while opening credential popups
I managed to duplicate the bug reliably on firefox : go on a page where you must enter stored credential. As I have a master password, I get the first popup to ask for it and when it prompt for the second popup with the credential themselves, it crashes. In TB as, I have tree popups (bug as it ask for the master password tree times) for different email accounts, it crashes also when opening the second one, once the main TB window is open (the first one appears before the main window in my case). -- eric
Bug#819810: There is now and AR release of 2016.2.22
ntfs-3g_ntfsprogs-2016.2.22AR.1.tgz --eric
Bug#830912: fakeroot complains about missing acl_* symbols
Package: fakeroot Version: 1.21-1 Severity: normal fakeroot dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_get_fd dlsym(acl_get_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_get_file dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_set_fd dlsym(acl_set_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_set_file dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_get_fd dlsym(acl_get_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_get_file dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_set_fd dlsym(acl_set_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_set_file dlsym(acl_get_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_get_fd dlsym(acl_get_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_get_file dlsym(acl_set_fd): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_set_fd dlsym(acl_set_file): /usr/lib/x86_64-linux-gnu/libfakeroot/libfakeroot-sysv.so: undefined symbol: acl_set_file -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.14 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fakeroot depends on: ii libc62.23.90+20160711.c10f90d-1 ii libfakeroot 1.21-1 fakeroot recommends no packages. fakeroot suggests no packages. -- no debconf information
Bug#1065349: libsmbclient0: Actually breaks part of t64 transition
Package: libsmbclient0 Version: 2:4.19.5+dfsg-3 Severity: grave Justification: renders package unusable the control file should contain: Provides: libsmbclient (= 2:4.19.5+dfsg-3) Otherwyse as many package depends on libsmbclient it cannot be removed and the replace is not sufficient. I checked how other pachage manage their transitions and it is done this way. Here is my manually modified config file. dpkg -s libsmbclient0 Package: libsmbclient0 Status: install ok installed Priority: optional Section: libs Installed-Size: 240 Maintainer: Debian Samba Maintainers Architecture: amd64 Multi-Arch: same Source: samba Version: 2:4.19.5+dfsg-3 Provides: libsmbclient (= 2:4.19.5+dfsg-3) Depends: samba-libs (= 2:4.19.5+dfsg-3), libbsd0 (>= 0.0), libc6 (>= 2.25), libndr3 (>= 2:4.17.2), libtalloc2 (>= 2.4.1~), libtevent0t64 (>= 0.15.0) Breaks: libsmbclient (<< 2:4.19.5+dfsg-3) Description: shared library for communication with SMB/CIFS servers This package provides a shared library that enables client applications to talk to Microsoft Windows and Samba servers using the SMB/CIFS protocol. Homepage: https://www.samba.org -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (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 libsmbclient0 depends on: ii libbsd0 0.12.1-1 ii libc6 2.38-6 ii libtalloc22.4.2-1 ii libtevent0t64 0.16.1-2 ii samba-libs [libndr3] 2:4.19.5+dfsg-3 libsmbclient0 recommends no packages. libsmbclient0 suggests no packages. -- no debconf information
Bug#1065349: [Pkg-samba-maint] Bug#1065349: libsmbclient0: Actually breaks part of t64 transition
On 03/03/2024 14:50, Michael Tokarev wrote: Control: severity -1 important 03.03.2024 13:21, Eric Valette : Package: libsmbclient0 Version: 2:4.19.5+dfsg-3 Severity: grave Justification: renders package unusable This is wrong, in my opinion. The effect of this bug on platforms unaffected by time64_t transition is exactly the same as on platforms affected by the transition. apt download libsmbclient0 Réception de :1 http://ftp.de.debian.org/debian unstable/main amd64 libsmbclient0 amd64 2:4.19.5+dfsg-3 [86,5 kB] 86,5 ko réceptionnés en 0s (418 ko/s) valette@tri-yann5:/tmp$ dpkg-deb -R libsmbclient0_2%3a4.19.5+dfsg-3_amd64.deb libsmbclient valette@tri-yann5:/tmp$ cd libsmbclient/ valette@tri-yann5:/tmp/libsmbclient$ more DEBIAN/control Package: libsmbclient0 Source: samba Version: 2:4.19.5+dfsg-3 Architecture: amd64 Maintainer: Debian Samba Maintainers Installed-Size: 240 Depends: samba-libs (= 2:4.19.5+dfsg-3), libbsd0 (>= 0.0), libc6 (>= 2.25), libndr3 (>= 2:4.17.2), libtalloc2 (>= 2.4.1~), libtevent0t64 (>= 0.15.0) Breaks: libsmbclient (<< 2:4.19.5+dfsg-3) Replaces: libsmbclient Section: libs Priority: optional Multi-Arch: same Homepage: https://www.samba.org Description: shared library for communication with SMB/CIFS servers This package provides a shared library that enables client applications to talk to Microsoft Windows and Samba servers using the SMB/CIFS protocol. So Although I'm not a debian developer, I read this control file as: You cannot install libsmbclient0 without breaking libsmbclient if the version of libsmbclient is not at least 2:4.19.5+dfsg-3. It will then replace libsmbclient. BUT the package libsmbclient 2:4.19.5+dfsg-3 is never going to be generated nor latter versions unless the names change back to libsmbclient. So the condition will never happen. The Provides directive give a way to provide libsmbclient 2:4.19.5+dfsg-3 And as you state, if the time_t type is already 64 bits why should package depending on libsmbclient need to be regenerated? --eric
Bug#1065015: the control file for the akonadi libraries are palin wrong
The transition is completed but the package cannot install because of Breaks: in the control file And I second that the abi provided should be without t64libkf5akonadisearchpim5-22.12 I managed to install removing the breaks in the package name and modifying the abi provided So nothing to do with transition. And You are not alone to make mistake in control files. -- eric
Bug#1065388: libqt5core5t64: control files are wrong for all t64 qt libraries
Package: libqt5core5t64 Version: 5.15.10+dfsg-7.1 Severity: grave Justification: renders package unusable Package: libqt5core5t64 Source: qtbase-opensource-src Version: 5.15.10+dfsg-7.1 Architecture: amd64 Maintainer: Debian Qt/KDE Maintainers Installed-Size: 6061 Depends: shared-mime-info, libc6 (>= 2.35), libdouble-conversion3 (>= 2.0.0), libgcc-s1 (>= 3.4), libglib2.0-0t64 (>= 2.22.0), libicu72 (>= 72.1~rc-1~), libpcre2-16-0 (>= 10.22), libstdc++6 (>= 11), libzstd1 (>= 1.5.5), zlib1g (>= 1:1.1.4) Recommends: qttranslations5-l10n Suggests: libthai0 Breaks: libqt5core5a (<< 5.15.10+dfsg-7.1) Replaces: libqt5core5a Provides: libqt5core5a (= 5.15.10+dfsg-7.1), qtbase-abi-5-15-10 Section: libs Priority: optional Multi-Arch: same Homepage: https://www.qt.io/developers/ Description: Qt 5 core module Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. . The QtCore module contains core non-GUI functionality. The Breaks: makes apt to search for a libqt5core5a >= 5.15.10+dfsg-7.1 but it will never exist as long as the package is not FIRST replaced by the t64 version. Removing the Breaks: make it installable and the provides expose the libqt5core5a as present. It has been stuck for 5 days already and I do not think this is due to the transition (except many package are uninstalable due to various error in control files). -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (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 libqt5core5t64 depends on: ii libc6 2.38-6 ii libdouble-conversion3 3.3.0-1+b1 ii libgcc-s1 14-20240221-2.1 ii libglib2.0-0t642.78.4-2.1+b1 ii libicu72 72.1-4+b1 ii libpcre2-16-0 10.42-4+b1 ii libstdc++6 14-20240221-2.1 ii libzstd1 1.5.5+dfsg2-2 ii shared-mime-info 2.4-1 ii zlib1g 1:1.3.dfsg-3.1 Versions of packages libqt5core5t64 recommends: ii qttranslations5-l10n 5.15.10-2 Versions of packages libqt5core5t64 suggests: ii libthai0 0.1.29-2
Bug#1065015: the control file for the akonadi libraries are palin wrong
On Mon, 04 Mar 2024 05:41:21 +0100 Sune Stolborg Vuorela wrote: On Sunday, March 3, 2024 6:16:23 PM CET Eric Valette wrote: > The transition is completed but the package cannot install because of > Breaks: in the control file The transition is still on going. This is in absolute number of packages the biggest one ever. If it it wasn't for all of the newish languages like node/ js, go and rust it would also in the relative numbers be the biggest one ever. This remains the only packages I cannot install due to transition on all machines. apt install libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5akonadisearchcore5t64 libkf5akonadisearchpim5t64 libkf5akonadisearchxapian5t64 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: kaddressbook-data kdepim-themeeditors kirigami-addons-data libkf5eventviews5abi1 libkf5ksieveui5 libkf5mailimporter5 libkf5mailimporterakonadi5 libkf5templateparser5 libkpimaddressbookimportexport5 libqt5location5-plugins libqt5positioning5-plugins pim-sieve-editor qml-module-org-kde-kirigami-addons-labs-mobileform qml-module-qtlocation qml-module-qtpositioning Use 'apt autoremove' to remove them. The following packages will be REMOVED: akonadiconsole kaddressbook kalendar kde-standard kmail knotes korganizer libkf5akonadisearchcore5 libkf5akonadisearchpim5 libkf5akonadisearchxapian5 libkf5incidenceeditor5abi1 libkf5mailcommon5abi2 libkf5messagecomposer5abi1 libkf5messagelist5abi1 libkf5pimcommonakonadi5abi1 mbox-importer pim-data-exporter The following packages will be upgraded: libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5akonadisearchcore5t64 libkf5akonadisearchpim5t64 libkf5akonadisearchxapian5t64 5 upgraded, 0 newly installed, 17 to remove and 3 not upgraded. Need to get 277 kB of archives. After this operation, 59.5 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. And apt install libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5akonadisearchcore5t64 libkf5akonadisearchpim5t64 libkf5akonadisearchxapian5t64 akonadiconsole kaddressbook kalendar Reading package lists... Done Building dependency tree... Done Reading state information... Done akonadiconsole is already the newest version (4:22.12.3-1). kaddressbook is already the newest version (4:22.12.3-1+b1). kalendar is already the newest version (22.12.3-2). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: akonadiconsole : Depends: libkf5akonadisearchcore5-22.12 Depends: libkf5akonadisearchxapian5-22.12 libkf5messagelist5abi1 : Depends: libkf5akonadisearchpim5-22.12 libkf5pimcommonakonadi5abi1 : Depends: libkf5akonadisearchpim5-22.12 E: Unable to correct problems, you have held broken packages.
Bug#1065015: reopen unti I can install the packages
reopen 1065015
Bug#1075969: python3-fitz: error when launching pymupdf
Package: python3-fitz Version: 1.24.2+ds1-2 Severity: grave Justification: renders package unusable /usr/bin/pymupdf Traceback (most recent call last): File "/usr/bin/pymupdf", line 5, in from fitz.__main__ import main ModuleNotFoundError: No module named 'fitz' dpkg -L python3-fitz /. /usr /usr/bin /usr/bin/pymupdf /usr/lib /usr/lib/python3 /usr/lib/python3/dist-packages /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/INSTALLER /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/METADATA /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/README.md /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/WHEEL /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/entry_points.txt /usr/lib/python3/dist-packages/fitz_old /usr/lib/python3/dist-packages/fitz_old/__init__.py /usr/lib/python3/dist-packages/fitz_old/__main__.py /usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-311-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-312-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/fitz_old/fitz_old.py /usr/lib/python3/dist-packages/fitz_old/table.py /usr/lib/python3/dist-packages/fitz_old/utils.py -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.37 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-fitz depends on: ii libc62.39-3.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libgumbo20.12.0+dfsg-2+b1 ii libharfbuzz0b8.3.0-2+b1 ii libjbig2dec0 0.20-1+b2 ii libjpeg62-turbo 1:2.1.5-3 ii libmujs3 1.3.3-3+b2 ii libopenjp2-7 2.5.0-2+b3 ii python3 3.12.2-1 python3-fitz recommends no packages. python3-fitz suggests no packages. -- no debconf information
Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update
On Mon, 20 Nov 2023 21:17:40 +0100 Michael Biebl wrote: I will add a versioned Breaks isc-dhcp-client (<< 4.4.3-P1-5) to network-manager, assuming the next version fixing this issue will be 4.4.3-P1-5. Btw, the AppArmor policy also references /usr/lib/NetworkManager/nm-dhcp-client.action This binary is long gone. You can just remove any traces of it. Is is allowed to put a versioned break on a non existing version? Result is that I cannot upgrade as I still need dhcp. -- eric
Bug#1072187: Not fixed even in rc3-6 when following the apt-changelist mask command system does still not boot
So I have tmp in /etc/fstab I followed the advice to perfrom systemctl mask tmp.mount I have a strange message about binfmt and grub-common failing and the reasons is that / is still ro If I remove the /tmp entry from fstab and do systemctl unmask tmp.mount and reboot the boot is correct. -- Eric Valette
Bug#1072187: Checked again uncommenting /tmp in /etc/fstab and doing the mask again => no boot
Very annoying. I have no link in /etc/systemd/system/tmp.mount -- Eric Valette
