Bug#424676: ri-li: does not react on any input - same behavior
Hi Chaps, I got exacly the same result, a screen displaying a rotating train without any reaction. Tracing system calls with strace shows a endless loop on an open file with FD 4: read(4, 0x9e5c534, 4096) = -1 EAGAIN (Resource temporarily unavailable) This file is a socket (lsof -p pid): ri-li pid jim4u unix 0xf513ae40 13378 socket Jim - j...@jabber.belnet.be http://jim.brubel.net/ http://twitter.com/JimleVert - 1 personne sur 10 comprend le binaire. L'autre pas. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#463860: any chance to see this fixed in 2.6.26 ?
Hello everybody, 2 things: - I think this other bug report talks about the same bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524132 Is it a good idea to group them together ? - I read this and if I understanded well, this will never be fixed and we have to wait for the next version of the kernel containing a ath5k driver without bug ? If I can help, I encountered the same problem and tried to locate it (dmesg, strace ifup ath0, ...). Just tell me. Jean-Marc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660769: unmet dependencies when migrating to libreoffice
Package: libreoffice Version: 1:3.4.3-3~bpo60+1 Severity: normal When trying to migrate from OpenOffice 1:3.2.1-11+squeeze4 to libreoffice 1:3.4.3-3~bpo60+1 using the Debian way, (see also http://www.debian.org/News/2011/20110623.fr.html), I always got error messages about unmet dependencies. See log: jim@server:~$ sudo apt-get install -t squeeze-backports libreoffice 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: libreoffice : Depends: libreoffice-core (= 1:3.4.3-3~bpo60+1) but it is not going to be installed Depends: libreoffice-writer but it is not going to be installed Depends: libreoffice-calc but it is not going to be installed Depends: libreoffice-impress but it is not going to be installed Depends: libreoffice-draw but it is not going to be installed Depends: libreoffice-math but it is not going to be installed Depends: libreoffice-base but it is not going to be installed Depends: libreoffice-report-builder-bin but it is not going to be installed Depends: libreoffice-filter-mobiledev but it is not going to be installed Depends: libreoffice-java-common (= 1:3.4.3~) but it is not going to be installed E: Broken packages My /etc/apt/sources.list: deb http://ftp.debian.skynet.be/ftp/debian/ squeeze main contrib non-free deb-src http://ftp.debian.skynet.be/ftp/debian/ squeeze main contrib non-free deb http://security.debian.org/ squeeze/updates main contrib non-free deb-src http://security.debian.org/ squeeze/updates main contrib non-free # dépôts Backport deb http://backports.debian.org/debian-backports squeeze-backports main -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717099: problem seems to be solved
Hi guys, I updated my system today and the problem seems to be solved. I can start gnome-control-center without getting the message free(): invalid pointer: 0x7fe4b00ae000 anymore. Jean-Marc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717099: I made a diff of packages' list after the update
, 4.6.3-6), libqt4-script:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2), gtk2-engines-pixbuf:amd64 (2.24.18-1, 2.24.20-1), libgtk2.0-bin:amd64 (2.24.18-1, 2.24.20-1), libgtk2.0-common:amd64 (2.24.18-1, 2.24.20-1), postgresql-client-9.1:amd64 (9.1.9-2, 9.1.9-2+b1), libqt4-designer:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2), libqtdbus4:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2), libgtk2.0-0:amd64 (2.24.18-1, 2.24.20-1), libqt4-test:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2), libapr1:amd64 (1.4.6-4, 1.4.8-1), libqt4-scripttools:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2), media-player-info:amd64 (17-1, 18-1), libqtgui4:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2), libpq5:amd64 (9.1.9-2, 9.1.9-2+b1), libqt4-declarative:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2), libgail-common:amd64 (2.24.18-1, 2.24.20-1), rsyslog:amd64 (7.4.0-1, 7.4.2-1), libqt4-help:amd64 (4.8.4+dfsg-4, 4.8.5+dfsg-2) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2013-07-16 07:11:04 Start-Date: 2013-07-18 18:00:49 Commandline: apt-get dist-upgrade Upgrade: parallel:amd64 (20120422-1, 20130622-1), xterm:amd64 (293-1, 295-1), libexpat1:amd64 (2.1.0-3, 2.1.0-4) End-Date: 2013-07-18 18:01:12 Start-Date: 2013-07-20 00:09:17 Commandline: apt-get dist-upgrade Upgrade: libdatetime-timezone-perl:amd64 (1.59-1+2013c, 1.60-1+2013d), seabios:amd64 (1.7.2-3, 1.7.3-1) End-Date: 2013-07-20 00:09:26 Start-Date: 2013-07-20 21:16:00 Commandline: apt-get dist-upgrade Install: libwireshark3:amd64 (1.10.0-2, automatic), libwiretap3:amd64 (1.10.0-2, automatic), libwsutil3:amd64 (1.10.0-2, automatic) Upgrade: gnustep-common:amd64 (2.6.2-2, 2.6.2-2.1), libwireshark-data:amd64 (1.8.7-1, 1.10.0-2), wireshark-common:amd64 (1.8.7-1, 1.10.0-2), libzephyr4:amd64 (3.0.2-2, 3.1~beta0-1), wireshark:amd64 (1.8.7-1, 1.10.0-2), libbsd0:amd64 (0.5.2-1, 0.6.0-1), libpth20:amd64 (2.0.7-16, 2.0.7-19) End-Date: 2013-07-20 21:16:30 Start-Date: 2013-07-21 10:11:16 Commandline: apt-get dist-upgrade Upgrade: libvisio-0.0-0:amd64 (0.0.28-1, 0.0.30-1), libmhash2:amd64 (0.9.9.9-1.1, 0.9.9.9-2), python-tagpy:amd64 (0.94.8-4, 2013.1-2), libwbclient0:amd64 (3.6.16-1, 3.6.16-2), libsmbclient:amd64 (3.6.16-1, 3.6.16-2) End-Date: 2013-07-21 10:11:29 Start-Date: 2013-07-22 20:37:51 Commandline: apt-get dist-upgrade Install: libfluidsynth1:amd64 (1.1.6-2, automatic), libraw9:amd64 (0.15.3-1, automatic) Upgrade: geoip-database:amd64 (20130610-1, 20130711-2), install-info:amd64 (5.1.dfsg.1-3, 5.1.dfsg.1-4), libtry-tiny-perl:amd64 (0.12-1, 0.16-1), libjavascriptcoregtk-3.0-0:amd64 (1.8.1-3.4, 1.8.1-4), libwebkitgtk-1.0-0:amd64 (1.8.1-3.4, 1.8.1-4), gir1.2-javascriptcoregtk-3.0:amd64 (1.8.1-3.4, 1.8.1-4), libsdl-mixer1.2:amd64 (1.2.12-5, 1.2.12-6), shotwell-common:amd64 (0.14.1-2, 0.14.1-3), packagekit:amd64 (0.8.9-2, 0.8.9-3), shotwell:amd64 (0.14.1-2, 0.14.1-3), packagekit-tools:amd64 (0.8.9-2, 0.8.9-3), libwebkitgtk-3.0-0:amd64 (1.8.1-3.4, 1.8.1-4), python3-packagekit:amd64 (0.8.9-2, 0.8.9-3), libwebkitgtk-3.0-common:amd64 (1.8.1-3.4, 1.8.1-4), libappstream0:amd64 (0.2.0-2, 0.3.1-3), packagekit-backend-aptcc:amd64 (0.8.9-2, 0.8.9-3), libwebkitgtk-1.0-common:amd64 (1.8.1-3.4, 1.8.1-4), info:amd64 (5.1.dfsg.1-3, 5.1.dfsg.1-4), libjavascriptcoregtk-1.0-0:amd64 (1.8.1-3.4, 1.8.1-4), libpackagekit-glib2-16:amd64 (0.8.9-2, 0.8.9-3), gir1.2-webkit-3.0:amd64 (1.8.1-3.4, 1.8.1-4), texinfo:amd64 (5.1.dfsg.1-3, 5.1.dfsg.1-4), appstream-index:amd64 (0.2.0-2, 0.3.1-3) End-Date: 2013-07-22 20:38:49 I hope this will help. Best regards, Jean-Marc - j...@jabber.belnet.be http://jim.brubel.net/ http://identi.ca/jimlevert http://twitter.com/JimleVert - 1 personne sur 10 comprend le binaire. L'autre pas. J'utilise DuckDuckGo (https://duckduckgo.com/). Et toi ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#717920: gnome-control-center user-accounts - clicking on username to switch to editmode freezes Gnome3
Package: gnome-control-center Version: 1:3.4.3.1-5 Severity: normal Dear Maintainer, When you click on the user name to switch to editmode, the label is highlighted, but subsequently and quite magically the font size of that label increases stepwise, until the whole screen is filled and an error screen pops up. Jean-Marc -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.34-1 ii apg2.2.3.dfsg.1-2 ii desktop-file-utils 0.21-1 ii gnome-control-center-data 1:3.4.3.1-5 ii gnome-desktop3-data3.4.2-2 ii gnome-icon-theme 3.8.2-2 ii gnome-icon-theme-symbolic 3.8.2.2-2 ii gnome-menus3.8.0-2 ii gnome-settings-daemon 3.4.2+git20121218.7c1322-6+b1 ii gsettings-desktop-schemas 3.4.2-3 ii libatk1.0-02.8.0-2 ii libc6 2.17-7 ii libcairo-gobject2 1.12.14-4 ii libcairo2 1.12.14-4 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libcheese-gtk213.4.2-2 ii libcheese3 3.4.2-2 ii libclutter-1.0-0 1.10.8-2 ii libcogl-pango0 1.10.2-7 ii libcogl9 1.10.2-7 ii libcolord1 1.0.1-1 ii libcomerr2 1.42.5-1.1 ii libcups2 1.6.2-10 ii libdbus-1-31.6.12-1 ii libdbus-glib-1-2 0.100.2-1 ii libfontconfig1 2.10.2-2 ii libgcrypt111.5.2-3 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-0 2.36.3-3 ii libgnome-bluetooth11 3.8.1-2 ii libgnome-desktop-3-2 3.4.2-2 ii libgnome-menu-3-0 3.8.0-2 ii libgnomekbd7 3.4.0.2-1 ii libgnutls262.12.23-5 ii libgoa-1.0-0 3.8.2-1 ii libgssapi-krb5-2 1.10.1+dfsg-6.1 ii libgstreamer0.10-0 0.10.36-1.2 ii libgtk-3-0 3.8.2-3 ii libgtop2-7 2.28.4-3 ii libjson-glib-1.0-0 0.16.0-1 ii libk5crypto3 1.10.1+dfsg-6.1 ii libkrb5-3 1.10.1+dfsg-6.1 ii libnm-glib40.9.8.0-5 ii libnm-gtk0 0.9.8.2-1+b1 ii libnm-util20.9.8.0-5 ii libnotify4 0.7.5-2 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-01.32.5-5+b1 ii libpolkit-gobject-1-0 0.105-3 ii libpulse-mainloop-glib02.0-6.1 ii libpulse0 2.0-6.1 ii libsocialweb-client2 0.25.20-6 ii libupower-glib10.9.20-2 ii libwacom2 0.6-1 ii libx11-6 2:1.6.0-1 ii libxcomposite1 1:0.4.4-1 ii libxdamage11:1.1.4-1 ii libxext6 2:1.3.2-1 ii libxfixes3 1:5.0.1-1 ii libxi6 2:1.7.1.901-1 ii libxklavier16 5.2.1-1 ii libxml22.9.1+dfsg1-2 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages gnome-control-center recommends: ii cups-pk-helper 0.2.5-1 ii gnome-online-accounts 3.8.2-1 ii gnome-session 3.4.2.1-4 ii gnome-user-guide 3.8.2-1 ii iso-codes 3.44-1 ii mesa-utils 8.0.1-2+b3 ii mousetweaks3.8.0-1 ii policykit-1-gnome 0.105-2 Versions of packages gnome-control-center suggests: ii gnome-screensaver 3.4.1-1 ii gstreamer0.10-pulseaudio 0.10.31-3+nmu1 ii libcanberra-gtk-module0.30-2 ii x11-xserver-utils 7.7~3 ii xscreensaver 5.15-3 -- 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#707110: some info about this wrong configuration
In the config' /etc/nginx/sites-enabled/default, the directives listen are like this: listen 80; listen [::]:80 default_server; But I found this in the nginx doc' (http://wiki.nginx.org/HttpCoreModule#listen), When you enable the address [::]:80, binding port 80 using IPv6, in the listen directive, in Linux, by default, the IPv4 port 80 is also enabled. Meaning that nginx listens for both IPv4 and IPv6 incoming traffic. Therefore if you erroneously specify also a IPv4 address you'll get an already bind address error when reloading nginx configuration. SOLUTION 1 - remove directive liste 80;, (pay attentioon if you need to set up a second virtual host, you will have to separate IPv4 and IPv6 stacks; see solutions 2 and 3) SOLUTION 2: - separate IPv4 and v6 stacks using net.ipv6.bindv6only and set its value to 1. SOLUTION 3: - separate IPv4 and v6 stacks using the ipv6only option and replace this line: - listen [::]:80 default_server; + listen [::]:80 default_server ipv6only=on; I personnaly use the third solution. -- Jean-Marc jean-m...@6jf.be pgpPietrvErAU.pgp Description: PGP signature
Bug#717099: gnome-control-center gives error free(): invalid pointer when starting
Package: gnome-control-center Version: 1:3.4.3.1-5 Severity: normal Hi guys, Trying to start gnome-control-center always gives me an error: *** Error in `gnome-control-center': free(): invalid pointer: 0x7fe4b00ae000 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7aa26)[0x7fe4b8bbaa26] /lib/x86_64-linux-gnu/libc.so.6(+0x7b7a3)[0x7fe4b8bbb7a3] /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x195d25)[0x7fe494ec4d25] /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x206322)[0x7fe494f35322] /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0xc953a)[0x7fe494df853a] /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x115678)[0x7fe494e44678] /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0x115781)[0x7fe494e44781] /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0xdc247)[0x7fe494e0b247] /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so(+0xdc917)[0x7fe494e0b917] /usr/lib/x86_64-linux-gnu/libcogl.so.9(+0x18b2c)[0x7fe496a6db2c] /usr/lib/x86_64-linux-gnu/libcogl.so.9(+0x6361a)[0x7fe496ab861a] /usr/lib/x86_64-linux-gnu/libcogl.so.9(cogl_context_new+0x10b)[0x7fe496a762bb] /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0(+0x65333)[0x7fe496f4f333] /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0(+0x7c2b3)[0x7fe496f662b3] /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0(+0x87cda)[0x7fe496f71cda] /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0(+0x87f0b)[0x7fe496f71f0b] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_option_context_parse+0x3c7)[0x7fe4b9499117] /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0(clutter_init+0xd2)[0x7fe496f721d2] /usr/lib/x86_64-linux-gnu/libcheese-gtk.so.21(cheese_gtk_init+0x24)[0x7fe497433e34] /usr/lib/control-center-1/panels/libuser-accounts.so(g_io_module_load+0x33)[0x7fe4978744e3] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x58516)[0x7fe4b99ed516] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_type_module_use+0x81)[0x7fe4b9777fe1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_io_modules_load_all_in_directory_with_scope+0xa5)[0x7fe4b99ed8f5] gnome-control-center[0x40a98a] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_type_create_instance+0x19c)[0x7fe4b9774f4c] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x14a58)[0x7fe4b9759a58] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_newv+0x751)[0x7fe4b975b4d1] /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_new+0xec)[0x7fe4b975bb2c] gnome-control-center(main+0x72)[0x408d82] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fe4b8b61995] gnome-control-center[0x408e31] === Memory map: 0040-00413000 r-xp 09:0a 1854957 /usr/bin/gnome-control-center 00612000-00613000 r--p 00012000 09:0a 1854957 /usr/bin/gnome-control-center 00613000-00614000 rw-p 00013000 09:0a 1854957 /usr/bin/gnome-control-center 00bce000-01567000 rw-p 00:00 0 [heap] 7fe492b85000-7fe492bb7000 r-xp 09:0a 1847754 /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0.0.0 7fe492bb7000-7fe492db6000 ---p 00032000 09:0a 1847754 /usr/lib/x86_64-linux-gnu/libtxc_dxtn_s2tc.so.0.0.0 [...] I do not use extension or other stuffs And I have no idea what to do. Same behavior when I tried to start the Network Parms UI or any other parms UI of Gnome. Jean-Marc -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-control-center depends on: ii accountsservice0.6.34-1 ii apg2.2.3.dfsg.1-2 ii desktop-file-utils 0.21-1 ii gnome-control-center-data 1:3.4.3.1-5 ii gnome-desktop3-data3.4.2-2 ii gnome-icon-theme 3.8.2-2 ii gnome-icon-theme-symbolic 3.8.2.2-2 ii gnome-menus3.8.0-2 ii gnome-settings-daemon 3.4.2+git20121218.7c1322-6+b1 ii gsettings-desktop-schemas 3.4.2-3 ii libatk1.0-02.8.0-2 ii libc6 2.17-7 ii libcairo-gobject2 1.12.14-4 ii libcairo2 1.12.14-4 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libcheese-gtk213.4.2-2 ii libcheese3 3.4.2-2 ii libclutter-1.0-0 1.10.8-2 ii libcogl-pango0 1.10.2-7 ii libcogl9 1.10.2-7 ii libcolord1 1.0.1-1 ii libcomerr2 1.42.5-1.1 ii libcups2 1.6.2-10 ii libdbus-1-31.6.12-1 ii libdbus-glib-1-2 0.100.2-1 ii libfontconfig1 2.10.2-2 ii libgcrypt111.5.2-3 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-0 2.36.3-3 ii libgnome-bluetooth11 3.8.1-2 ii libgnome-desktop-3-2 3.4.2-2 ii libgnome-menu
Bug#723936: systemd: fails to upgrade - same behavior
Hi, I got exactly the same problem. dist-upgrade contained systemd/204-4; getting errors and impossible to invoke a start of pcscd and bluez. I rebooted because the kernel 3.10-3 also came with the upgrade. And systemd did not start properly hanging and failing in timedout after a while. I checked mounted FS but none of my LVM FS were there. I tried to boot with previous versions of the kernel with the same result. I switched back to initd to recover. If I can help, tell me. Jean-Marc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723936: [Pkg-systemd-maintainers] Bug#723936: systemd: fails to upgrade - same behavior
On Tue, 24 Sep 2013 12:45:32 +0200, Michael Biebl bi...@debian.org wrote: Am 24.09.2013 12:01, schrieb Jean-Marc: Hi, [SNIP] The upgrade failure and the LVM problem sound like different issue not related to each other. Your LVM issue is most likely the same as [1] OK. As for the upgrade failure: Did running apt-get a second time successfully complete the upgrade? Unfortunately, when I ran apt-get the second time, I have started my system using initd, the only way I found to make it started. And it worked, meaning the 2 (re)starts were OK. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718190#85 P.S. I am not used to send bug reports; Do I have to reply to you, to the bug tracking system or to both ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723936: [Pkg-systemd-maintainers] Bug#723936: systemd: fails to upgrade - same behavior
On Tue, 24 Sep 2013 13:53:18 +0200, Michael Biebl bi...@debian.org wrote: Am 24.09.2013 13:27, schrieb Jean-Marc: On Tue, 24 Sep 2013 12:45:32 +0200, Michael Biebl bi...@debian.org wrote: Am 24.09.2013 12:01, schrieb Jean-Marc: Hi, [SNIP] The upgrade failure and the LVM problem sound like different issue not related to each other. Your LVM issue is most likely the same as [1] OK. You could try the packages posted there and see if they fix your LVM issue (assuming you use the amd64 architecture) I took a look at this but I have no issue with systemd/LVM. The problem is systemd never reached the step where it mounts FS's. It hangs before and timedouts asking for root password or ctrl-D. As for the upgrade failure: Did running apt-get a second time successfully complete the upgrade? Unfortunately, when I ran apt-get the second time, I have started my system using initd, the only way I found to make it started. Do you have an backup from before the upgrade so we have a chance of reproducing the issue? No, no backup But I am sure there is a problem with systemd. The last version installed on my system is not able to start it anymore. And I can reproduce this. Do you want the output of journalctl -xb ? Or other logs ? Michael Jean-Marc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763291: cheese only displays There was an error playing video from the webcam
Package: cheese Version: 3.12.2-1 Severity: normal Dear Maintainer, I tried to start up cheese and I just got a complete grayed-out interface just displaying There was an error playing video from the webcam. Starting cheese from a terminal gives this message: =-=-=-= $ cheese (cheese:2726): cheese-WARNING **: Failed to allocate required memory.: gstv4l2src.c(478): gst_v4l2src_decide_allocation (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin28/GstV4l2Src:video_source: Buffer pool activation failed =-=-=-= I do not know if it matters: I use a Logitech, Inc. QuickCam Communicate STX (ID 046d:08ad). Jean-Marc -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cheese depends on: ii cheese-common 3.12.2-1 ii gnome-video-effects0.4.1-2 ii libc6 2.19-11 ii libcanberra-gtk3-0 0.30-2.1 ii libcheese-gtk233.12.2-1 ii libcheese7 3.12.2-1 ii libclutter-1.0-0 1.18.4-2 ii libclutter-gtk-1.0-0 1.6.0-1 ii libgdk-pixbuf2.0-0 2.30.8-1 ii libglib2.0-0 2.40.0-5 ii libgnome-desktop-3-10 3.14.0-1 ii libgstreamer1.0-0 1.4.1-1 ii libgtk-3-0 3.12.2-3+b1 Versions of packages cheese recommends: ii gnome-icon-theme3.12.0-1 ii gvfs1.20.3-1 ii hicolor-icon-theme 0.13-1 ii nautilus-sendto 3.8.1-1+b1 ii yelp3.12.0-1 Versions of packages cheese suggests: pn gnome-video-effects-frei0r none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781337: xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend
Sat, 28 Mar 2015 08:10:09 +0100 Sven Joachim svenj...@gmx.de écrivait : I think this is the same problem as #781359, happening on very similar hardware (GeForce 8600M GT). I got exactly the same problem using kernel 3.19 from linux-image-3.19.0-trunk-amd64 package. So, consider this as not solved in 3.19. Jean-Marc jean-m...@6jf.be pgp4GJxkqRlC_.pgp Description: PGP signature
Bug#781337: xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend
Package: xserver-xorg-video-nouveau Version: 1:1.0.11-1 Severity: important Dear Maintainer, I get on a regular basis problems resuming from suspend. (sometimes very serious needing a hard reset). The problem is the following: Instead of resuming, the system partially hangs and the screen displays black and white rectangles. Switching to the console is not always possible. If I can switch to it, I get messages repetitively flooding it: kernel: [ 2723.298937] nouveau E[ PGRAPH][:02:00.0] PGRAPH_VSTATUS0: 0x00145b4d CCACHE kernel: [ 2723.298939] nouveau E[ PGRAPH][:02:00.0] PGRAPH_VSTATUS1: 0x002d kernel: [ 2723.298941] nouveau E[ PGRAPH][:02:00.0] PGRAPH_VSTATUS2: 0x0034db40 ENG2D ROP kernel: [ 2725.298350] nouveau E[ PGRAPH][:02:00.0] PGRAPH TLB flush idle timeout fail kernel: [ 2725.298355] nouveau E[ PGRAPH][:02:00.0] PGRAPH_STATUS : 0x011fde03 BUSY DISPATCH VFETCH CCACHE_PREGEOM STRMOUT_VATTR_POSTGEOM VCLIP TRAST CLIPID ZCULL ENG2D RMASK TPC_RAST TPC_PROP ROP If I can switch to the console, I can blindly type some commands to reboot. It worked like this since I upgrade to 3.14 kernel I think. I also noticed other people suffer the same problem solved by upgrading to experimental kernel 3.19. See https://bugs.freedesktop.org/show_bug.cgi?id=89186. Apparently, the reportbug does its job very well. If you need more info, feel free to get in touch. Jean-Marc. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 19 2013 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2401376 Feb 11 01:35 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. KMS configuration files: /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) Xorg X server log files on system: -- -rw-r--r-- 1 root root 8851 Jun 12 2014 /var/log/Xorg.3.log -rw-r--r-- 1 root root 8851 Jun 12 2014 /var/log/Xorg.4.log -rw-r--r-- 1 root root 8851 Jun 12 2014 /var/log/Xorg.5.log -rw-r--r-- 1 root root 36984 Mar 10 17:49 /var/log/Xorg.2.log -rw-r--r-- 1 root root 36787 Mar 25 11:36 /var/log/Xorg.1.log -rw-r--r-- 1 root root 45354 Mar 27 18:46 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [20.533] X.Org X Server 1.16.4 Release Date: 2014-12-20 [20.533] X Protocol Version 11, Revision 0 [20.533] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [20.533] Current Operating System: Linux Cunegonde 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) x86_64 [20.533] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=f763cefc-7dc7-47b1-b9f4-4600778e0176 ro quiet [20.533] Build Date: 11 February 2015 12:32:02AM [20.533] xorg-server 2:1.16.4-1 (http://www.debian.org/support) [20.533] Current version of pixman: 0.32.6 [20.533]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [20.533] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [20.533] (==) Log file: /var/log/Xorg.0.log, Time: Fri Mar 27 18:06:06 2015 [20.664] (==) Using system config directory /usr/share/X11/xorg.conf.d [20.895] (==) No Layout section. Using the first Screen section. [20.895] (==) No screen section available. Using defaults. [20.895] (**) |--Screen Default Screen Section (0) [20.895] (**) | |--Monitor default monitor [20.908] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [20.908] (==) Automatically adding devices [20.908] (==) Automatically enabling devices [20.908] (==) Automatically adding GPU devices [21.269] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [21.276]Entry deleted from font path. [21.430] (==) FontPath set to: /usr/share/fonts/X11/misc, /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 [21.430] (==) ModulePath set to /usr/lib/xorg/modules [21.430] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev
Bug#781337: xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend
le Fri, 27 Mar 2015 20:58:02 +0100 Sven Joachim svenj...@gmx.de écrivait : hi Sven, On 2015-03-27 19:17 +0100, Jean-Marc wrote: I get on a regular basis problems resuming from suspend. (sometimes very serious needing a hard reset). That's a kernel problem. OK. Can you re-assign the bug ? [...] Well, have _you_ tried a 3.19 kernel yet? If not, please do so. OK? I'll try it and let you know. But I have a question: - will 3.16 the official kernel of the next stable ? - will this problem possibly affect all machine with G8 nvidia cards ? [...] This is for G86, but you have a G84 card - similar but not the same. Cheers, Cheers, Sven Jean-Marc jean-m...@6jf.be pgpUceFMECSqq.pgp Description: PGP signature
Bug#781337: xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend
Fri, 27 Mar 2015 20:58:02 +0100 Sven Joachim svenj...@gmx.de écrivait : hi Sven, That's a kernel problem. I installed linux-image-3.19.0-trunk-amd64 from experimental. I'll keep you posted if it solved the problem. Jean-Marc jean-m...@6jf.be pgp2akpjog8Pn.pgp Description: PGP signature
Bug#779796: same behavior trying to get http://mentors.debian.net/login
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I tried to GET the page http://mentors.debian.net/login multiple times. I always got a segfault. See also the discussion here: https://lists.debian.org/debian-user-french/2015/05/msg00278.html -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVWlwRAAoJEECwQOvthjrRLTUQANoFWfKM4QyLZRnT0PwVxBRf OiEVBLivmWnTIcej33agjNPirqXozHif+HkjqY8KoOo+bs5t3AXvIo2le1UrPrKB BFPcQVroiYsX0hG72eCJg7r8J+xqhtZFF6vmgLF7cH0Qd59xXuErTfSXsAzvtOxR lYyugMDm8f1t/iuzCzCNABHKj9fzdUbwj9RxUvdW1+ybcgAImnXk32uwKE1IspKa +8/YpTsv9xFHfI6e9Rv7bha1ityHra0hGmPbBpFNRpSRgbvCAItNOTmZ6hsQ723l uRwAb2qlyH5PqAfKk0IbVCscs0HWvbDwDIhSIWc9dJ+UyxrsGKrMe0IEAXASZILw /CHZIiBANlQCVoGK1cT4hHPcR912ja9UMjgA6Xrv9vvP6BkQ1uINU7JGzFelPdXt X+E4vQNDn58tMG59XIEm460UcLI1T+zuNY86MrUwRnPV3IhrOevxB2QhxYvYPVA2 cUtwmRNl7QybFmQKXSDvyLcjyn+V6BQqGXj2S31fPPtiIInKAaxws4dJB3gA94fl EdlohdjW687amdqGrt/tPa55mOfculFtRLxYTwW0zTngYHWSh99RmwG2vZkDyEbw jr2d/DtUm7+mdmi1OJYy4WXXRLV5FFVPD73NAxxJdJFnfTxe4ZHsYYhbKYutaf2l h6kPwql0P04Ws+fmtvGO =TWIW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779796: I forgot to mention my config
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Linux 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux iceweasel: Installed: 38.0-2 unstable/main amd64 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVWmZnAAoJEECwQOvthjrRWBQQAOo3U9104HHYoZCy2+t7IzIL MS+jQZJSrMqYziagKs12LA3iTATV7SF/BOHQjH6T3uj9lpcti9S6XmZF+aWth6FH BgfjBfMxgasCLSPNlBI53jhjqP70dI3D8TBoYX8++Z/PvgUpO0VuwIq3aUw2T3EE SzZGF9xtdJgb6yG3toMKjs/RKO1ABLolXf9hJVen3enuQc02z+7WHjQVazWdpVL5 GKwWKRaGY5pH6MKKuYularL0I1cIfhpt9zWRPBUk4Bbb/OIy9nndS2icOJ7LO/JO Ho6acvxcKClRvX++TxuuYyRUiCiAxY8KHYUUMfPvM6TOCE6ydPDCIVjfrnSMCpMI FjEds4z/hQCClTies9OuXi849BBBHU2gMXJxR7QENrijYHUuAnF/0ygX6woAU9Xc CLRVEAe3kOyQKbpb/4ScRGzAfexS+/a4DayYdTBOaX6XQGpoxgkysOYpCTtuvUDT 3t4QqRZ7Sv2Ot89ZHN6mSF5Qpqc/AMeg2lciIxgnJHYBDJeW2jxBJNzCav6m8RNL PvnvMmPEMTagutPdTRDr2VzY1xSupJCCafHiYbzAAU1lNmLdx6SGpV80s6RD0Sz3 KzYtv7WulMGn5F0qgE1NDyvvtjIVXx5Z4su/mNayCbaQewgLyLTI1sAOEk9ftQpP FxoDDCEbFcauBD1yTexQ =UyvJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781337: xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend
Wed, 08 Apr 2015 19:33:59 +0200 Sven Joachim svenj...@gmx.de écrivait : hi Sven, Report it upstream, please see http://nouveau.freedesktop.org/wiki/Bugs/ for instructions. I got some time to report it upstream after a new incident. See https://bugs.freedesktop.org/show_bug.cgi?id=90092 Cheers, Sven Cheers, Jean-Marc jean-m...@6jf.be pgphbY7qGOhTq.pgp Description: PGP signature
Bug#781337: xserver-xorg-video-nouveau: Screen Hangs Displaying Black and White Rectangles After Resuming from Suspend
Sat, 28 Mar 2015 08:10:09 +0100 Sven Joachim svenj...@gmx.de écrivait : hi Sven, Control: reassign -1 src:linux Control: merge 781359 -1 I think this is the same problem as #781359, happening on very similar hardware (GeForce 8600M GT). Can I do something to help ? Jean-Marc jean-m...@6jf.be pgpmV8ykPd1Cu.pgp Description: PGP signature
Bug#789725: gnome-settings-daemon: Super+L shortcut does not work since last upgrade
Package: gnome-settings-daemon
Version: 3.16.2-3
Severity: normal
Dear Maintainer,
Since the last upgrade (3.14.2-3 - 3.16.2-3), the shortcut Super+L does not
work anymore.
When I use it, it does not lock the screen as expected.
And it generates this message in /var/log/message:
gnome-session[...]: (gnome-settings-daemon:8272): GLib-GIO-WARNING **: Dropping
signal AcceleratorActivated of type (uuu) since the type from the expected
interface is (ua{sv})
Jean-Marc
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-settings-daemon depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2
ii gsettings-desktop-schemas3.16.1-1
ii libc62.19-18
ii libcairo21.14.2-2
ii libcanberra-gtk3-0 0.30-2.1
ii libcanberra0 0.30-2.1
ii libcolord2 1.2.1-1+b2
ii libcups2 1.7.5-12
ii libfontconfig1 2.11.0-6.3
ii libgdk-pixbuf2.0-0 2.31.4-2
ii libgeocode-glib0 3.16.2-1
ii libglib2.0-0 2.44.1-1
ii libgnome-desktop-3-103.16.2-2
ii libgtk-3-0 3.16.4-2
ii libgudev-1.0-0 230-1
ii libgweather-3-6 3.16.1-1
ii liblcms2-2 2.6-3+b3
ii libnm-glib4 1.0.2-2
ii libnm-util2 1.0.2-2
ii libnotify4 0.7.6-2
ii libnspr4 2:4.10.8-2
ii libnspr4-0d 2:4.10.8-2
ii libnss3 2:3.19.1-2
ii libnss3-1d 2:3.19.1-2
ii libpackagekit-glib2-18 1.0.6-1
ii libpam-systemd 215-18
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libpolkit-gobject-1-00.105-8
ii libpulse-mainloop-glib0 6.0-2
ii libpulse06.0-2
ii librsvg2-2 2.40.9-2
ii libupower-glib3 0.99.3-1+b1
ii libwacom20.8-1
ii libwayland-client0 1.8.1-1
ii libx11-6 2:1.6.3-1
ii libxext6 2:1.3.3-1
ii libxi6 2:1.7.4-1+b2
ii libxtst6 2:1.2.2-1+b1
ii nautilus-data3.14.2-1
Versions of packages gnome-settings-daemon recommends:
ii pulseaudio 6.0-2
Versions of packages gnome-settings-daemon suggests:
ii e17 [x-window-manager] 0.17.6-1
ii fluxbox [x-window-manager] 1.3.5-2
ii gnome-screensaver3.6.1-4
ii metacity [x-window-manager] 1:3.14.3-1
ii mutter [x-window-manager]3.14.4-2+b1
ii openbox [x-window-manager] 3.5.2-8
ii x11-xserver-utils7.7+4
ii xfwm4 [x-window-manager] 4.12.3-1
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789725: Shortcuts - additional information
I tried other shortcuts. Mute, changing speakers' volume, changing screen brightness do not work neither on my laptop running the same version. Same error messages in /var/log/message. Cheers, Jean-Marc jean-m...@6jf.be pgpOl6EEXRlSe.pgp Description: PGP signature
Bug#789474: #789474: gnome-settings-daemon: Keyboard shortcuts do not work after update to version 3.16.2-3
hi Emilio,
I think you can also close these three bugs related to the same problem:
#789725 [n| | ] [gnome-settings-daemon] gnome-settings-daemon: Super+L
shortcut does not work since last upgrade
#789866 [n| | ] [gnome-settings-daemon] gnome-settings-daemon: Keyboard media
keys not working after upgrading gnome-settings-daemon
#789891 [n| | ] [gnome-settings-daemon] gnome-settings-daemon: Shortcuts
can't work, syslogs say'gnome-session[1180]: (gnome-settings-daemon:1280):
GLib-GIO-WARNING **: Dropping signal AcceleratorActivated of type (uuu) since
the type from the expected interface is (ua{sv})'
Regards,
Jean-Marc jean-m...@6jf.be
pgpD8MARCeJXu.pgp
Description: PGP signature
Bug#794769: gnome-control-center uses Lock Screen as Background wallpaper
Package: gnome-control-center Version: 1:3.16.3-1 Severity: normal Dear Maintainer, gnome-control-center uses Lock Screen as Background wallpaper when you choose to use the default Debian Jessie theme. Actually, everything goes right the first time you will log in. But the second time and all the logins after, it uses the Lock Screen image instead of the Background one. If you start gnome-control-center and go to Background definition, the setting is OK. I also noticed if you use another wallpaper, everything goes right. Jean-Marc -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-control-center depends on: ii accountsservice0.6.40-2 ii apg2.2.3.dfsg.1-2 ii colord 1.2.1-1+b2 ii desktop-file-utils 0.22-1 ii gnome-control-center-data 1:3.16.3-1 ii gnome-desktop3-data3.16.2-2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-settings-daemon 3.16.3-1 ii gsettings-desktop-schemas 3.16.1-1 ii libaccountsservice00.6.40-2 ii libatk1.0-02.16.0-2 ii libc6 2.19-19 ii libcairo-gobject2 1.14.2-2 ii libcairo2 1.14.2-2 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libcheese-gtk233.16.1-1 ii libcheese7 3.16.1-1 ii libclutter-1.0-0 1.22.4-1 ii libclutter-gtk-1.0-0 1.6.2-1 ii libcolord-gtk1 0.1.25-1.1+b1 ii libcolord2 1.2.1-1+b2 ii libcups2 2.0.3-10 ii libdbus-glib-1-2 0.102-1 ii libfontconfig1 2.11.0-6.3 ii libgdk-pixbuf2.0-0 2.31.5-1 ii libgl1-mesa-glx [libgl1] 10.6.3-1 ii libglib2.0-0 2.44.1-1.1 ii libgnome-bluetooth13 3.16.1-1 ii libgnome-desktop-3-10 3.16.2-2 ii libgoa-1.0-0b 3.16.3-1 ii libgoa-backend-1.0-1 3.16.3-1 ii libgrilo-0.2-1 0.2.12-2 ii libgtk-3-0 3.16.6-1 ii libgtop-2.0-10 2.30.0-3 ii libgudev-1.0-0 230-2 ii libibus-1.0-5 1.5.10-1 ii libkrb5-3 1.12.1+dfsg-20 ii libmm-glib01.4.10-1 ii libnm-glib-vpn11.0.2-2 ii libnm-glib41.0.2-2 ii libnm-gtk0 1.0.4-1 ii libnm-util21.0.2-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libpolkit-gobject-1-0 0.105-11 ii libpulse-mainloop-glib06.0-2 ii libpulse0 6.0-2 ii libpwquality1 1.2.3-1 ii libsmbclient 2:4.1.17+dfsg-4 ii libsoup2.4-1 2.50.0-2 ii libupower-glib30.99.3-1+b2 ii libwacom2 0.8-1 ii libx11-6 2:1.6.3-1 ii libxi6 2:1.7.4-1+b2 ii libxml22.9.1+dfsg1-5 Versions of packages gnome-control-center recommends: ii cracklib-runtime 2.9.2-1 ii cups-pk-helper 0.2.5-2+b1 ii gkbd-capplet 3.6.0-1 ii gnome-online-accounts 3.16.3-1 ii gnome-user-guide 3.16.1-1 ii gnome-user-share 3.14.2-1 ii iso-codes 3.59-1 ii libnss-myhostname 222-2 ii lxsession [policykit-1-gnome] 0.5.1-2 ii mesa-utils 8.2.0-1 ii mousetweaks3.12.0-1 ii network-manager-gnome 1.0.4-1 ii policykit-1-gnome 0.105-2 ii realmd 0.16.1-1 ii rygel 0.26.1-3 ii rygel-tracker 0.26.1-3 ii system-config-printer 1.4.6-1 Versions of packages gnome-control-center suggests: ii gstreamer1.0-pulseaudio 1.4.5-2+b1 ii libcanberra-gtk-module 0.30-2.1 ii libcanberra-gtk3-module 0.30-2.1 ii x11-xserver-utils7.7+4 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#794766: abiword always automatically starts at login
Package: abiword Version: 3.0.1-4 Severity: normal Dear Maintainer, Everytime I log in and start a gnome session, abiword starts. I checked ~/.config/autostart and /etc/xdg/autostart but I found nothing related to abiword in these directories. Jean-Marc -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages abiword depends on: ii abiword-common 3.0.1-4 ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 ii libabiword-3.0 3.0.1-4 ii libc6 2.19-19 ii libdbus-1-3 1.8.20-1 ii libdbus-glib-1-20.102-1 ii libgcc1 1:5.1.1-14 ii libgcrypt20 1.6.3-2 ii libglib2.0-02.44.1-1.1 ii libgnutls-deb0-28 3.3.16-1 ii libgoffice-0.10-10 0.10.18-1 ii libgsf-1-1141.14.33-1 ii libgtk-3-0 3.16.6-1 ii libjpeg62-turbo 1:1.4.1-1 ii libloudmouth1-0 1.4.3-12 ii libots0 0.5.0-2.1 ii libpng12-0 1.2.50-2+b2 ii librdf0 1.0.17-1+b1 ii libreadline66.3-8+b3 ii librevenge-0.0-00.0.2-2 ii libsoup2.4-12.50.0-2 ii libstdc++6 5.1.1-14 ii libtelepathy-glib0 0.24.1-1 ii libtidy-0.99-0 20091223cvs-1.5 ii libwmf0.2-7 0.2.8.4-10.4 ii libwpd-0.10-10 0.10.0-2+b1 ii libwpg-0.3-30.3.0-3 ii libwps-0.4-40.4.0-2 ii libxml2 2.9.1+dfsg1-5 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages abiword recommends: ii abiword-plugin-grammar 3.0.1-4 ii aspell-en [aspell-dictionary] 7.1-0-1.1 ii aspell-fr [aspell-dictionary] 0.50-3-7 ii fonts-liberation 1.07.4-1 ii poppler-utils 0.26.5-3 abiword suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#826153: xserver-xorg-input-synaptics: TouchPad does't work on GNOME with version 1.8.3-2
On Thu, 02 Jun 2016 20:53:31 +0200 Dino Trevisani <ctrl4ltc...@libero.it> wrote: > Package: xserver-xorg-input-synaptics > Version: 1.8.3-2 > Severity: normal > > Dear Maintainer, > > Synaptic Driver and Libinput Driver are usually installed simultaneously on > the system in standard Debian clean install. Last version of GNOME uses only > Libinput Driver and accordingly touchpad does not work on GNOME because of > change implemented in version 1.8.3-2 of Synaptic Driver > > * Cherry-pick upstream commit 59e5db, Which renames 50-synaptics.conf > to 70-synaptics.conf. This means the synaptic will be used driver > instead of the driver libinput When both are installed. In the comment, you can see they renamed 50-synaptics.conf in 70-synaptics.conf because "When specifically installed by the user, the synaptics driver should override the system default." (dixit). But I think they are always installed both in Debian. It means to make Gnome works, I had to rename 70-synaptics.conf file. I tried to purge xserver-xorg-input-synaptics but xserver-xorg-input-all depends on it. > [...] Jean-Marc <jean-m...@6jf.be> pgpwnbEPnUtmO.pgp Description: PGP signature
Bug#818410: glpi: GLPI does not provide nginx configuration examples
Package: glpi
Version: 0.84.8+dfsg.1-1
Severity: wishlist
Dear Maintainer,
I installed GLPI on a Jessie system and try to make it run with nginx,
one of the httpd Debian server.
But there are no nginx configuration examples.
And GLPI needs nginx paases some specific parameters to php-fpm (i.e.
SERVER_NAME).
I got some help from GLPI DEV and want to share it with Debian.
So, I attached 2 nginx configs (a vhost and a subdir).
If you find it useful, please, feel free to add these configs to glpi
documentation.
Jean-Marc
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# GLPI
server {
server_name glpi.example.com;
index index.php;
root /usr/share/glpi;
access_log /var/log/nginx/glpi-access.log;
error_log /var/log/nginx/glpi-error.log;
location ~ ^/(files|config|scripts|locales)/(.+)$ {
deny all;
}
location /install/mysql {
deny all;
}
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_intercept_errors on;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
fastcgi_param SCRIPT_NAME $fastcgi_script_name;
fastcgi_param PATH_TRANSLATED
$document_root$fastcgi_path_info;
fastcgi_param SERVER_NAME $host;
# With php5-fpm:
fastcgi_pass unix:/var/run/php5-fpm.sock;
}
# Install is only allowed via local access (from the GLPI server).
# Add your IP address if you need it for remote installation,
# but remember to remove it after installation for security.
location ~ ^/install/(.+\.php)$ {
allow 127.0.0.1;
allow ::1;
deny all;
try_files $uri =404;
fastcgi_intercept_errors on;
includefastcgi_params;
fastcgi_param SERVER_NAME $host;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
fastcgi_pass unix:/var/run/php5-fpm.sock;
}
}
# GLPI
location = /glpi {
alias /usr/share/glpi/;
}
location /glpi/ {
root /usr/share;
index index.php;
location ~ ^/glpi/config/(.+)$ {
deny all;
}
location ~ ^/glpi/scripts/(.+)$ {
deny all;
}
location ~ ^/glpi/locales/(.+)$ {
deny all;
}
location /glpi/install/mysql {
deny all;
}
# Install is only allowed via local access (from the GLPI server).
# Add your IP address if you need it for remote installation,
# but remember to remove it after installation for security.
location ~ ^/glpi/install/(.+\.php)$ {
allow 127.0.0.1;
allow ::1;
deny all;
try_files $uri =404;
fastcgi_intercept_errors on;
includefastcgi_params;
fastcgi_param SERVER_NAME $host;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_pass unix:/var/run/php5-fpm.sock;
}
location ~ ^/glpi/(.+\.php)$ {
try_files $uri =404;
fastcgi_intercept_errors on;
includefastcgi_params;
fastcgi_param SERVER_NAME $host;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_pass unix:/var/run/php5-fpm.sock;
}
}
Bug#815804: info about the bug
Hi Ben, I discussed with Maderios regarding this bug (I know him from the debian-user-french list). He told me he is not able to reproduce it because he de-installed Debian from his machine. Do you think it should stay open ? Regards, Jean-Marc <jean-m...@6jf.be> pgpA9fSMTousA.pgp Description: PGP signature
Bug#819548: Processed: tagging 819548
Thu, 31 Mar 2016 08:12:05 + ow...@bugs.debian.org (Debian Bug Tracking System) écrivait : > Processing commands for cont...@bugs.debian.org: > > > tags 819548 + unreproducible > Bug #819548 [gnome-maps] gnome-maps fails to start > Added tag(s) unreproducible. > > thanks > Stopping processing here. > > Please contact me if you need assistance. Apparently, gdm got the same problem to activate the service. = extracted from /var/log/message: /usr/lib/gdm3/gdm-x-session[1349]: Activating service name='org.gnome.Maps' org.gnome.Maps[1362]: (org.gnome.Maps:6900): Gjs-WARNING **: JS ERROR: TypeError: GObject.ParamSpec.override is not a function org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/mapMarker.js:44 org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/placeMarker.js:24 org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/geoJSONSource.js:30 org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/geoJSONShapeLayer.js:22 org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/mapView.js:34 org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/mainWindow.js:38 org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/application.js:36 org.gnome.Maps[1362]: @resource:///org/gnome/Maps/js/main.js:43 org.gnome.Maps[1362]: start@resource:///org/gnome/gjs/modules/package.js:176 org.gnome.Maps[1362]: @/usr/share/gnome-maps/org.gnome.Maps:5 org.gnome.Maps[1362]: JS_EvaluateScript() failed /usr/lib/gdm3/gdm-x-session[1349]: Activated service 'org.gnome.Maps' failed: Process org.gnome.Maps exited with status 1 = Jean-Marc <jean-m...@6jf.be> pgpDdJUKGXNqM.pgp Description: PGP signature
Bug#818410: glpi: GLPI does not provide nginx configuration examples - missing reference
Hi (again), I forgot to mention the source of the configuration I attached. I based configuration files on Fedora out-of-the-box example: http://pkgs.fedoraproject.org/cgit/rpms/glpi.git/tree/glpi-nginx.conf Regards, Jean-Marc <jean-m...@6jf.be> pgpFR_vkjFRhc.pgp Description: PGP signature
Bug#819548: gnome-maps fails to start
Sun, 3 Apr 2016 14:41:44 +0200 Andreas Henriksson <andr...@fatal.se> écrivait : > Hello again! Hi Andreas, > > mlundblad mentioned to me on IRC that he has identified the culprit > as gjs in testing not being new enough. Please confirm that upgrading > to gjs from unstable fixes the problem for you. I installed gjs 1.44.0-1 and (+ its dependency libgjs0e 1.44.0-1) from unstable and it solved the issue. Gnome Maps start without any problems. > > (This issue has been fixed upstream in gnome-maps at: > https://git.gnome.org/browse/gnome-maps/commit/?id=f735490a47afbf > and I'll add the equivalent dependency to the debian package shortly.) > > Regards, Thank you so much to you and mlundblad on IRC. Kindest regards, > Andreas Henriksson Jean-Marc <jean-m...@6jf.be> pgpkD30RBDG0G.pgp Description: PGP signature
Bug#819548: gnome-maps fails to start
Package: gnome-maps Version: 3.20.0-1 Severity: normal Dear Maintainer, I just upgraded to gnome-maps 3.20 and it failed to start. $ gnome-maps (org.gnome.Maps:1990): Gjs-WARNING **: JS ERROR: TypeError: GObject.ParamSpec.override is not a function @resource:///org/gnome/Maps/js/mapMarker.js:44 @resource:///org/gnome/Maps/js/placeMarker.js:24 @resource:///org/gnome/Maps/js/geoJSONSource.js:30 @resource:///org/gnome/Maps/js/geoJSONShapeLayer.js:22 @resource:///org/gnome/Maps/js/mapView.js:34 @resource:///org/gnome/Maps/js/mainWindow.js:38 @resource:///org/gnome/Maps/js/application.js:36 @resource:///org/gnome/Maps/js/main.js:43 start@resource:///org/gnome/gjs/modules/package.js:176 @/usr/bin/gnome-maps:5 JS_EvaluateScript() failed I checked bug reports seeing multiple reports about start failing but none of them are relevant (mostly related to older versions). Tell me if I can help. Jean-Marc -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-maps depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii geoclue-2.0 2.4.1-1 ii gir1.2-champlain-0.120.12.13-1 ii gir1.2-clutter-1.0 1.24.2-1 ii gir1.2-cogl-1.0 1.22.0-2 ii gir1.2-gdkpixbuf-2.0 2.32.3-1.2 ii gir1.2-geoclue-2.0 2.4.1-1 ii gir1.2-geocodeglib-1.0 3.20.0-1 ii gir1.2-gfbgraph-0.2 0.2.3-1 ii gir1.2-glib-2.0 1.46.0-4 ii gir1.2-goa-1.0 3.18.4-1 ii gir1.2-gtk-3.0 3.18.9-1 ii gir1.2-gtkchamplain-0.12 0.12.13-1 ii gir1.2-gtkclutter-1.01.6.6-1 ii gir1.2-gweather-3.0 3.20.0-1 ii gir1.2-rest-0.7 0.7.93-1 ii gir1.2-secret-1 0.18.3-1 ii gir1.2-soup-2.4 2.52.2-1 ii gir1.2-webkit2-4.0 2.10.8-1 ii gjs 1.43.3-2 ii libatk1.0-0 2.18.0-1 ii libc62.22-4 ii libcairo-gobject21.14.6-1 ii libcairo21.14.6-1 ii libchamplain-0.12-0 0.12.13-1 ii libclutter-1.0-0 1.24.2-1 ii libcogl-pango20 1.22.0-2 ii libcogl-path20 1.22.0-2 ii libcogl201.22.0-2 ii libdrm2 2.4.67-1 ii libegl1-mesa [libegl1-x11] 11.1.2-1 ii libfolks25 0.11.1-2+b1 ii libgbm1 11.1.2-1 ii libgdk-pixbuf2.0-0 2.32.3-1.2 ii libgee-0.8-2 0.18.0-1 ii libgeocode-glib0 3.20.0-1 ii libglib2.0-0 2.48.0-1 ii libgtk-3-0 3.18.9-1 ii libjson-glib-1.0-0 1.2.0-1 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii librest-0.7-00.7.93-1 ii libsoup2.4-1 2.52.2-1 ii libwayland-client0 1.9.0-1 ii libwayland-cursor0 1.9.0-1 ii libwayland-egl1-mesa [libwayland-egl1] 11.1.2-1 ii libwayland-server0 1.9.0-1 ii libx11-6 2:1.6.3-1 ii libxcomposite1 1:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.6-1 ii libxkbcommon00.5.0-1 ii libxml2 2.9.3+dfsg1-1 ii libxrandr2 2:1.5.0-1 gnome-maps recommends no packages. gnome-maps suggests no packages. -- no debconf information
Bug#819548: apt-get dist-upgrade solved it today on testing
Hi Andreas, Today, a standard dist-upgrade solved it on a PC I left unchanged on Stretch. Great work. Thank you. Kindest regards, Jean-Marc <jean-m...@6jf.be> pgpDhJE6y0g1K.pgp Description: PGP signature
Bug#811571: [Python-apps-team] Bug#811571: ocrfeeder: Unicode characters break exports
Sun, 1 May 2016 21:43:55 +0300 Alberto Garcia <be...@igalia.com> écrivait : Hi Berto, > This has just been fixed upstream. I'll probably update the Debian > package with the fix for this bug one of these days, but if you want to > try it yourself here's the change: > > https://git.gnome.org/browse/ocrfeeder/commit/?id=691f54618ed17a2553f154af07a6cfb4bf887e09 I just installed the unstable version and made some basic tests with the PDF I sent. It works great. I can produce and export text files. Thank's so much. > > Berto Jean-Marc <jean-m...@6jf.be> pgpfB8fVgFciz.pgp Description: PGP signature
Bug#811571: [Python-apps-team] Bug#811571: ocrfeeder: Unicode characters break exports
Sun, 17 Apr 2016 10:51:12 +0200
Jean-Marc <jean-m...@6jf.be> écrivait :
> On Tue, 26 Jan 2016 10:26:42 +0100 Alberto Garcia <be...@igalia.com> wrote:
>
> Hi Berto,
>
> > Can you share a document that you can use to reproduce that bug? I
> > just tried with an image containing accented non-ascii characters and
> > I can export it just fine to PDF, TXT, HTML and ODT.
>
> I attached a PFD file I used to test ocrfeeder.
> And giving the same error.
Actualy, it is not the same error.
>>>>>>>>>
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/ocrfeeder/studio/studioBuilder.py",
line 298, in exportDialog
self.EXPORT_FORMATS[format][1])
File "/usr/lib/python2.7/dist-packages/ocrfeeder/studio/studioBuilder.py",
line 281, in exportToFormat
name)
File "/usr/lib/python2.7/dist-packages/ocrfeeder/studio/widgetModeler.py",
line 606, in exportPagesWithGenerator
document_generator.save()
File
"/usr/lib/python2.7/dist-packages/ocrfeeder/feeder/documentGeneration.py", line
371, in save
f.write(self.text.encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 67:
ordinal not in range(128)
<<<<<<<<<<
>
> >
> > Berto
> >
>
> Regards,
>
> Jean-Marc <jean-m...@6jf.be>
Jean-Marc <jean-m...@6jf.be>
pgp7H2v4S68MG.pgp
Description: PGP signature
Bug#811571: [Python-apps-team] Bug#811571: ocrfeeder: Unicode characters break exports
On Tue, 26 Jan 2016 10:26:42 +0100 Alberto Garcia <be...@igalia.com> wrote: Hi Berto, > Can you share a document that you can use to reproduce that bug? I > just tried with an image containing accented non-ascii characters and > I can export it just fine to PDF, TXT, HTML and ODT. I attached a PFD file I used to test ocrfeeder. And giving the same error. > > Berto > Regards, Jean-Marc <jean-m...@6jf.be> cdp-p18.pdf Description: Adobe PDF document pgpfhqX6L9jin.pgp Description: PGP signature
Bug#848729: reportbug UnicodeDecodeError: possible patch, please test
On Thu, 26 Jan 2017 00:47:27 +0100 Nis Martensen <nis.marten...@web.de> wrote: > Can you please test if the attached patch fixes this bug? > I applied your patch and it does fix the bug. Thank you ! Jean-Marc <jean-m...@6jf.be> pgp7dWnzDBTXc.pgp Description: PGP signature
Bug#845199: additional info
Hi, Last week, I was testing a dist-upgrade scenario from Jessie to Strech to see how mysql-like packages will behave (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852267). I took this opportunity to also check what happen with migrating from PHP5 tp PHP7. And after the dist-upgrade, an left my dolibarr in a not-working state because of the removing of the Apache link in /etc/apache2/mods-enabled/ enabling PHP5. Just a question : all PHP app in Debian are supposed to be PHP7 compliant, aren't they ? So, in this case, why not directly removing PHP5 and enabling PHP7 ? Regards, Jean-Marc <jean-m...@6jf.be> pgpuYmr5YD1Mf.pgp Description: PGP signature
Bug#852267: upgrading mariadb-server-10.0 to mariadb-server-10.1 removed it instead of upgrading
Hi everybody, I found time to test a dist-upgrade scenario starting from a brand new Jessie and upgrading to Stretch upgrading from mysql-5.5 to mariadb-10.1 (not exactly the one I got because I upgraded from mariadb-10.0 to 10.1) And everything went fine, mariadb-server-10.1 replaced mysql-server-5.5 without any problem. So, I think the bug can be closed. Regards, Jean-Marc <jean-m...@6jf.be> pgp1yw5J26BBT.pgp Description: PGP signature
Bug#852267: upgrading mariadb-server-10.0 to mariadb-server-10.1 removed it instead of upgrading
Wed, 1 Feb 2017 00:18:18 +0200 Otto Kekäläinen <o...@debian.org> écrivait : > Thank you very much Jean-Marc for helping with testing! I helped with great pleasure. > > Can you please also try running apt-get purge mysql-* and see if it removes > the remnants cleanly? But not too cleanly, mysqld binary or /var/lib/mysql > used by mariadb-10.1 should not get deleted by the mysql purge (one user > reported he suffered such a case). So, after the dist-upgrade + autoremove --purge, I listed remaining packages containing mysql: $ dpkg --list | grep mysql ii default-mysql-client1.0.2 all MySQL database client binaries (metapackage) ii default-mysql-server1.0.2 all MySQL database server binaries and system database setup (metapackage) ii libdbd-mysql-perl 4.041-1 amd64 Perl5 database interface to the MariaDB/MySQL database ii mysql-common5.8+1.0.2 all MySQL database common files, e.g. /etc/mysql/my.cnf rc mysql-server-5.55.5.54-0+deb8u1 amd64 MySQL database server binaries and system database setup So, mysql-common 5.8+1.0.2 is still installed and mysql-server-5.5 is removed but Config files remain on the machine. And I simulated the purge you described: $ apt-get purge --simulate mysql-* [...] The following packages were automatically installed and are no longer required: galera-3 libaio1 libdbi-perl libjemalloc1 libreadline5 libterm-readkey-perl rsync socat Use 'apt autoremove' to remove them. The following packages will be REMOVED: default-mysql-client* default-mysql-server* libdbd-mysql-perl* libmariadbclient18* mariadb-client-10.1* mariadb-client-core-10.1* mariadb-common* mariadb-server-10.1* mariadb-server-core-10.1* mysql-common* mysql-server-5.5* 0 upgraded, 0 newly installed, 11 to remove and 0 not upgraded. Purg default-mysql-client [1.0.2] Purg default-mysql-server [1.0.2] Purg libdbd-mysql-perl [4.041-1] Purg libmariadbclient18 [10.1.21-5] Purg mariadb-server-10.1 [10.1.21-5] Purg mariadb-client-10.1 [10.1.21-5] Purg mariadb-client-core-10.1 [10.1.21-5] Purg mariadb-server-core-10.1 [10.1.21-5] Purg mariadb-common [10.1.21-5] Purg mysql-common [5.8+1.0.2] Purg mysql-server-5.5 Apparently, it is too cleanly. :-) I think it comes from the dependency between mysql-common and mariadb: $ apt rdepends mysql-common mysql-common Reverse Depends: PreDepends: mysql-server-5.5 (>= 5.5.54-0+deb8u1) Depends: mariadb-common (>= 5.6.25) Depends: libmariadbclient18 So, I think you can purge mysql-server-5.5 without any problem but not mysql-common: $ apt purge --simulate mysql-server-5.5 [...] The following packages will be REMOVED: mysql-server-5.5* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Purg mysql-server-5.5 For your info, there is the files from mysql-server-5.5 remain on my VM: $ dpkg --listfiles mysql-server-5.5 /etc /etc/logrotate.d /etc/logcheck /etc/logcheck/ignore.d.paranoid /etc/logcheck/ignore.d.paranoid/mysql-server-5_5 /etc/logcheck/ignore.d.server /etc/logcheck/ignore.d.server/mysql-server-5_5 /etc/logcheck/ignore.d.workstation /etc/logcheck/ignore.d.workstation/mysql-server-5_5 /etc/init.d /etc/apparmor.d /etc/mysql /etc/mysql/conf.d /etc/mysql/conf.d/mysqld_safe_syslog.cnf I checked the /var/log/apt/history.log and mysql-server-5.5 was removed during the dist-upgrade. And this process does not purge config files. I do not know if it is really usefull to keep them. Regards, Jean-Marc <jean-m...@6jf.be> pgplvJ49Tz1oV.pgp Description: PGP signature
Bug#852267: upgrading mariadb-server-10.0 to mariadb-server-10.1 removed it instead of upgrading
Package: mariadb-server-10.1 Version: 10.1.20-3 Severity: normal Dear maintainers, On 21/01, a dist-upgrade replaced mariadb 10.0 with 10.1. It removed mariadb-server-10.0:amd64 (10.0.28-2), mariadb-client-10.0:amd64 (10.0.28-2), mariadb-client-core-10.0:amd64 (10.0.28-2) but just installed mariadb-client-10.1:amd64 (10.1.20-3, automatic), mariadb-client-core-10.1:amd64 (10.1.20-3, automatic). So, no server anymore breaking my dolibarr instance. Manually installing mariadb-server-10.1 worked like a charm and solved the dolibarr issue, also replacing mariadb-server-core-10.0 (still installed after the mariadb-server-10.0 removal) with mariadb-client-core-10.1. Another strange behavior: this dist-upgrade upgraded the default-mysql-client from 1.0.1 but removed the default-mysql-server instead of upgrading it. =+=+=+=+= $ env LANG=C apt policy default-mysql-client default-mysql-server default-mysql-client: Installed: 1.0.2 Candidate: 1.0.2 Version table: *** 1.0.2 500 500 http://ftp.be.debian.org/debian testing/main amd64 Packages 100 http://ftp.be.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status default-mysql-server: Installed: (none) Candidate: 1.0.2 Version table: 1.0.2 500 500 http://ftp.be.debian.org/debian testing/main amd64 Packages 100 http://ftp.be.debian.org/debian unstable/main amd64 Packages I hope it will help for future upgrade. Regards, Jean-Marc <jean-m...@6jf.be> P.S. sorry for this incompleted bug report; reportbug does not work anymore on my system (see bug #848729). -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) pgpY8_9Zz2Iv2.pgp Description: PGP signature
Bug#852267: [debian-mysql] Bug#852267: upgrading mariadb-server-10.0 to mariadb-server-10.1 removed it instead of upgrading
Mon, 23 Jan 2017 13:53:26 +0200 Otto Kekäläinen <o...@debian.org> écrivait : > Can you provide me steps on how to reproduce this? What packages > exactly did you have installed before the upgrade (mariadb-*, > default-mysql-server, something that depends on mariadb-* or mysql-*)? This is the log of the dist-upgrade I did on 21/01: Start-Date: 2017-01-21 13:09:35 Commandline: apt dist-upgrade Requested-By: jim (1000) Install: mariadb-client-10.1:amd64 (10.1.20-3, automatic), mariadb-client-core-10.1:amd64 (10.1.20-3, automatic) Upgrade: hunspell-en-us:amd64 (20070829-6, 20070829-7), icedove:amd64 (1:45.4.0-1, 1:45.6.0-2), libgles2-mesa:amd64 (13.0.2-3, 13.0.3-1), libgles1-mesa:amd64 (13.0.2-3, 13.0.3-1), libv8-3.14.5:amd64 (3.14.5.8-8.1, 3.14.5.8-11), libglapi-mesa:amd64 (13.0.2-3, 13.0.3-1), libbz2-1.0:amd64 (1.0.6-8, 1.0.6-8+b1), liferea:amd64 (1.12~rc2-1, 1.12~rc2-2), nano:amd64 (2.7.3-1, 2.7.4-1), libxatracker2:amd64 (13.0.2-3, 13.0.3-1), libegl1-mesa:amd64 (13.0.2-3, 13.0.3-1), libflickcurl0:amd64 (1.25-3, 1.26-1), libgbm1:amd64 (13.0.2-3, 13.0.3-1), default-mysql-client:amd64 (1.0.1, 1.0.2), icedove-l10n-fr:amd64 (1:45.4.0-1, 1:45.6.0-2), liferea-data:amd64 (1.12~rc2-1, 1.12~rc2-2), libwayland-egl1-mesa:amd64 (13.0.2-3, 13.0.3-1), mysql-common:amd64 (5.8+1.0.1, 5.8+1.0.2), libgl1-mesa-dri:amd64 (13.0.2-3, 13.0.3-1), bzip2:amd64 (1.0.6-8, 1.0.6-8+b1), testdisk:amd64 (7.0-1+b1, 7.0-3), libgl1-mesa-glx:amd64 (13.0.2-3, 13.0.3-1), mesa-vdpau-drivers:amd64 (13.0.2-3, 13.0.3-1), calendar-google-provider:amd64 (1:45.4.0-1, 1:45.6.0-2), iceowl-extension:amd64 (1:45.4.0-1, 1:45.6.0-2) Remove: mariadb-server-10.0:amd64 (10.0.28-2), default-mysql-server:amd64 (1.0.1), mariadb-client-10.0:amd64 (10.0.28-2), mariadb-client-core-10.0:amd64 (10.0.28-2) End-Date: 2017-01-21 13:10:41 As you can see, it upgraded default-mysql-client:amd64 (1.0.1, 1.0.2) and removed default-mysql-server:amd64 (1.0.1). I do not know if it helps but I added my system policy at the end of this mail. As far as I remember, I installed a mysql client but never a server. I think the server came when I installed dolibarr. But it was 2 years ago, when Jessie was the testing. And I checked dolibarr but default-mysql-server is only "Recommends", not "Depends". Just like the apache2 package. It looks strange to me an app based on a LAMP stack just recommends its components. I do not know what you think. I think the removal comes from the lake of dependency between dolibarr and default-mysql-server or similar. I checked all the mysql server's packages' reverse dependencies and I have nothing installed depending on them. > > > When I tested dist-upgrade today, it does not even install > mariadb-server automatically (due to the removes of old packages) and > I needed to apt install it manually. When done so, everything removed > and upgraded as expected. I'll try to simulate it by installing dolibarr on a Debian Jessie and upgrading it to testing. I'll keep you posted. Regards, Jean-Marc <jean-m...@6jf.be> =+=+=+=+=+=+= $ env LANG=C apt policy Package files: 100 /var/lib/dpkg/status release a=now 1 http://ftp.be.debian.org/debian experimental/main amd64 Packages release o=Debian,a=experimental,n=experimental,l=Debian,c=main,b=amd64 origin ftp.be.debian.org 100 http://ftp.be.debian.org/debian unstable/non-free amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=non-free,b=amd64 origin ftp.be.debian.org 100 http://ftp.be.debian.org/debian unstable/contrib amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=contrib,b=amd64 origin ftp.be.debian.org 100 http://ftp.be.debian.org/debian unstable/main amd64 Packages release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64 origin ftp.be.debian.org 500 http://ftp.be.debian.org/debian testing/non-free amd64 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=non-free,b=amd64 origin ftp.be.debian.org 500 http://ftp.be.debian.org/debian testing/contrib amd64 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=contrib,b=amd64 origin ftp.be.debian.org 500 http://ftp.be.debian.org/debian testing/main amd64 Packages release o=Debian,a=testing,n=stretch,l=Debian,c=main,b=amd64 origin ftp.be.debian.org Pinned packages: pgp3L5zIzeBDT.pgp Description: PGP signature
Bug#852267: upgrading mariadb-server-10.0 to mariadb-server-10.1 removed it instead of upgrading
Tue, 24 Jan 2017 04:21:45 +0100 Andreas Beckmann <a...@debian.org> écrivait : hi Andreas, > I expect that the upgrade behavior improves once mariadb-10.0 is gone > from testing (and mysql-5.6 needs to go away as well). > From what I observed apt does not easily switch from package A to > package B if A still has an installation candidate. Once that is gone, A > is more likely a candidate for removal. Any idea when mariadb-10.0 will be gone from testing ? > > > Andreas Jean-Marc <jean-m...@6jf.be> pgp1pYhncEMI1.pgp Description: PGP signature
Bug#836972: gnome-control-center could not get screen information anymore
Thu, 8 Sep 2016 08:21:20 +0200 Andreas Henriksson <andr...@fatal.se> écrivait : > Control: tags -1 + unreproducible moreinfo > > Hello Jean-Marc. Hi Andreas, > > Thanks for your bug report. > [...] > I'm not able to reproduce your problem on neither of my two machines. Clicking on the "Displays" icon in g-c-c drives to a sub-menu where I usually got infos on screens connected to my machines allowing to change screens' settings. Now, I got no screens' icons at all, just a message saying it is not posible to get screen info. > Could you please quote the exact message you're seeing? Exact message is: "Could not get screen information" > Did you get any warning or error output when starting g-c-c from the command > line? No message. I also started g-c-c in verbose mode but got nothing relevant. > Interesting. Both of them running testing/stretch I guess? Yes, both run the same Debian version. > > Could you please keep a tight watch on what you're updating the coming > days and if any of the updates makes the issue go away? If so please > report that information back. Not all of gnome 3.21/3.22 has yet migrated > to testing and it might be that we need a tighter dependency somewhere. That's the problem of running in Strech. Do you know which lib/sub-component g-c-c uses to get screens' info ? It can help me to look if upgrading one or more packages from Sid solve the problem. > > Regards, > Andreas Henriksson Regards, Jean-Marc <jean-m...@6jf.be> pgpIinrRyx0Lr.pgp Description: PGP signature
Bug#836972: gnome-control-center display issues identified.
Thu, 8 Sep 2016 13:34:21 +0200 Andreas Henriksson <andr...@fatal.se> écrivait : > Control: found 836972 3.21.90-1 > Control: tags 836972 = pending > > Hello Jean-Marc, Đặng Duy Sơn. Hello Andreas, > > I'm happy to tell you that Michael Biebl notified me about > http://bugs.debian.org/836939 which is another symptom of > the same underlying issue where he had already identified > the cause. > > The problem is a mismatch between gnome-desktop3 and mutter. > Both need to be either 3.20 or 3.21/3.22. > > I've just committed a change that should guarantee that > gnome-desktop3 3.21.x won't install together with mutter 3.20 > which should resolve your issue. > > Hopefully mutter 3.21.x et.al. migrates to testing today, but > if not then you should be able to resolve your issues by > installing mutter + gnome-shell + dependencies from > unstable/sid. I just installed mutter 3.21 from unstable. It came with gnome-shell 3.21 + dependencies. I closed the session, re-opened it and the issue was gone. Great ! > > Thanks for your feedback. Thank you so much for your great work to you and Michael ! > > Regards, > Andreas Henriksson > Regards, Jean-Marc <jean-m...@6jf.be> pgpwcdigkaKaA.pgp Description: PGP signature
Bug#836972: gnome-control-center could not get screen information anymore
Package: gnome-control-center Version: 1:3.21.90-1 Severity: important Dear Maintainer, Since the last today's update, gnome-control-center could not get screen information anymore. That's the only message you got when you start it and choose "Displays" option. I started it from the commandline, from the gnome menu and from a rigth-click and the situation is the same. I also checked on my second computer. It worked before the upgrade and did not after upgrading to version 3.21. Regards, Jean-Marc -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-control-center depends on: ii accountsservice0.6.40-3 ii apg2.2.3.dfsg.1-4 ii colord 1.3.2-1 ii desktop-file-utils 0.23-1 ii gnome-control-center-data 1:3.21.90-1 ii gnome-desktop3-data3.21.90-3 ii gnome-settings-daemon 3.21.90-2 ii gsettings-desktop-schemas 3.21.4-2 ii libaccountsservice00.6.40-3 ii libatk1.0-02.20.0-1 ii libc6 2.23-5 ii libcairo-gobject2 1.14.6-1+b1 ii libcairo2 1.14.6-1+b1 ii libcanberra-gtk3-0 0.30-3 ii libcanberra0 0.30-3 ii libcheese-gtk253.20.2-2 ii libcheese8 3.20.2-2 ii libclutter-1.0-0 1.26.0-2 ii libclutter-gtk-1.0-0 1.8.0-1 ii libcolord-gtk1 0.1.26-1 ii libcolord2 1.3.2-1 ii libcups2 2.1.4-4 ii libfontconfig1 2.11.0-6.7 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.49.6-1 ii libgnome-bluetooth13 3.20.0-1 ii libgnome-desktop-3-12 3.21.90-3 ii libgoa-1.0-0b 3.20.3-1 ii libgoa-backend-1.0-1 3.20.3-1 ii libgrilo-0.3-0 0.3.1-1 ii libgtk-3-0 3.21.5-3 ii libgtop-2.0-10 2.34.1-2 ii libgudev-1.0-0 230-3 ii libibus-1.0-5 1.5.11-1 ii libkrb5-3 1.14.3+dfsg-1 ii libmm-glib01.6.0-1 ii libnm0 1.2.4-2 ii libnma01.2.4-1 ii libpango-1.0-0 1.40.2-1 ii libpangocairo-1.0-01.40.2-1 ii libpolkit-gobject-1-0 0.105-16 ii libpulse-mainloop-glib09.0-3 ii libpulse0 9.0-3 ii libpwquality1 1.3.0-1 ii libsmbclient 2:4.4.5+dfsg-2 ii libsoup2.4-1 2.55.90-1 ii libupower-glib30.99.4-3 ii libwacom2 0.19-1 ii libx11-6 2:1.6.3-1 ii libxi6 2:1.7.6-1 ii libxml22.9.4+dfsg1-1+b1 Versions of packages gnome-control-center recommends: ii cracklib-runtime 2.9.2-3 ii cups-pk-helper0.2.6-1 ii gkbd-capplet 3.6.0-1 ii gnome-online-accounts 3.20.3-1 ii gnome-user-guide 3.20.2-1 ii gnome-user-share 3.18.1-1 ii iso-codes 3.70-1 ii libnss-myhostname 231-4 ii mousetweaks 3.12.0-1 ii network-manager-gnome 1.2.4-1 ii policykit-1 0.105-16 ii pulseaudio-module-bluetooth 9.0-3 ii realmd0.16.3-1 ii rygel 0.30.3-1 ii rygel-tracker 0.30.3-1 ii system-config-printer-common 1.5.7-2 Versions of packages gnome-control-center suggests: ii gstreamer1.0-pulseaudio 1.8.3-1+b1 ii libcanberra-gtk-module 0.30-3 ii libcanberra-gtk3-module 0.30-3 ii x11-xserver-utils7.7+7 -- no debconf information
Bug#845199: dolibarr broken after upgrading from 3.5.8+dfsg1-1 to 4.0.2+dfsg4-1 and purging php5 packages
Package: dolibarr Version: 4.0.2+dfsg4-1 Severity: important Dear Maintainer, On Sunday, November the 20th, I ran a dist-upgrade. It came with an upgrade of Dolibarr. Install went fine. I started Dolibarr and was re-directed to the update page. I ran all the steps, step by step, to update from 3.5 to 4.0 and everything went fine. After the update, I did a quick tour of the application (clients, providers, bank accounts, ..). And evrything was looking fine. After that, I ran an autoremove cleaning up the following packages: libfpdi-php:amd64 (1.4.1-1), php-fpdf:amd64 (3:1.8.1.dfsg-2), php7.0-mbstring:amd64 (7.0.12-1), php5-cli:amd64 (5.6.26+dfsg-1), php5-readline:amd64 (5.6.26+dfsg-1), php5-json:amd64 (1.3.9-1), libapache2-mod-php5:amd64 (5.6.26+dfsg-1), libfpdf-tpl-php:amd64 (1.2-2), libonig4:amd64 (6.1.2-1), php5-curl:amd64 (5.6.26+dfsg-1), php5-ldap:amd64 (5.6.26+dfsg-1), php-mbstring:amd64 (1:7.0+46), php5:amd64 (5.6.26+dfsg-1), libpoppler61:amd64 (0.44.0-3), php-mail-mime:amd64 (1.10.0-2), libqdbm14:amd64 (1.8.78-6+b5) And Dolibarr stops working. I just code the PHP code instead of the application login page. Tell me if I can help solving this issue. Jean-Marc -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dolibarr depends on: ii fonts-dejavu-core 2.37-1 ii javascript-common 11 ii libapache2-mod-php 1:7.0+46 ii libapache2-mod-php7.0 [libapache2-mod-php] 7.0.12-1 ii libjs-jquery3.1.1-1 ii libjs-jquery-cookie 11-3 ii libjs-jquery-flot 0.8.3+dfsg-1 ii libjs-jquery-ui 1.12.1+dfsg-1 ii libnusoap-php 0.9.5-3 ii libphp-adodb5.20.7-1 ii php-cli 1:7.0+46 ii php-curl1:7.0+46 ii php-gd 1:7.0+46 ii php-ldap1:7.0+46 ii php-pclzip 2.8.2-4 ii php-tcpdf 6.2.12+dfsg2-1 ii php7.0-cli [php-cli]7.0.12-1 ii php7.0-curl [php-curl] 7.0.12-1 ii php7.0-gd [php-gd] 7.0.12-1 ii php7.0-ldap [php-ldap] 7.0.12-1 ii php7.0-mysql [php-mysqli] 7.0.12-1 ii ttf-dejavu-core 2.37-1 ii xdg-utils 1.1.1-1 Versions of packages dolibarr recommends: ii apache2 [httpd] 2.4.23-7 ii default-mysql-client 1.0.1 ii default-mysql-server 1.0.1 Versions of packages dolibarr suggests: ii firefox-esr [www-browser] 45.5.0esr-1 ii midori [www-browser] 0.5.11-ds1-4 pn php-geoip ii w3m [www-browser] 0.5.3-32 -- no debconf information
Bug#845199: dolibarr broken after upgrading from 3.5.8+dfsg1-1 to 4.0.2+dfsg4-1 and purging php5 packages
Mon, 21 Nov 2016 13:50:54 +0100 Raphael Hertzog <hert...@debian.org> écrivait : > Hello, hi Raphael, > > You seem to have libapache2-mod-php7.0 installed. But is the apache module > correctly enabled? Apparently not. > > Please show the output of: > $ ls -lR /etc/apache2 To not make the report too big and unreadable, I do not copy the output. But I suppose you want to know if /etc/apache2/mods-enabled contains a symlink to activate php7 module. I found this in /etc/apache2/mods-available: [...] -rw-r--r-- 1 root root 867 oct 15 17:11 php7.0.conf -rw-r--r-- 1 root root 102 oct 15 17:11 php7.0.load But no link related to them into /etc/apache2/mods-enabled. Something missing in the php7 install. Or something removing this in php5 purge. Do you know the right way to activate php7 ? Just creating 2 symlinks into mods-enabled for php7.0.conf and php7.0.load ? > > Cheers, Bye, > -- > Raphaël Hertzog ◈ Debian Developer > > Support Debian LTS: http://www.freexian.com/services/debian-lts.html > Learn to master Debian: http://debian-handbook.info/get/ Jean-Marc <jean-m...@6jf.be> pgp7pVlRQoqLD.pgp Description: PGP signature
Bug#845199: dolibarr broken after upgrading from 3.5.8+dfsg1-1 to 4.0.2+dfsg4-1 and purging php5 packages
Mon, 21 Nov 2016 14:56:05 +0100 Raphael Hertzog <hert...@debian.org> écrivait : hi Raphael, > > Run "a2enmod php7.0" Running this command enabled the PHP7.0 module. $ sudo a2enmod php7.0 [sudo] Mot de passe de jim : Considering dependency mpm_prefork for php7.0: Considering conflict mpm_event for mpm_prefork: Considering conflict mpm_worker for mpm_prefork: Module mpm_prefork already enabled Considering conflict php5 for php7.0: Enabling module php7.0. To activate the new configuration, you need to run: systemctl restart apache2 $ ls -l /etc/apache2/mods-enabled/ total 0 [...] lrwxrwxrwx 1 root root 29 nov 21 15:15 php7.0.conf -> ../mods-available/php7.0.conf lrwxrwxrwx 1 root root 29 nov 21 15:15 php7.0.load -> ../mods-available/php7.0.load I restarted apache: $ sudo systemctl restart apache2 and it solved the issue ! > > But this should be done automatically by the installation of > libapache2-mod-php7.0. Maybe it is missing. > > I guess that it was not done because php5 was still enabled and the two > are conflicting. But when php5 got removed, nothing enabled php7.0... > [...] Thank you so much for your quick reaction and help. > Cheers, > -- > Raphaël Hertzog ◈ Debian Developer Jean-Marc <jean-m...@6jf.be> pgpE1A2LflaSI.pgp Description: PGP signature
Bug#845199: [php-maint] Bug#845199: dolibarr broken after upgrading from 3.5.8+dfsg1-1 to 4.0.2+dfsg4-1 and purging php5 packages
Tue, 6 Dec 2016 18:25:53 +0100 Raphael Hertzog <hert...@debian.org> écrivait : > The problem is not the lack automatic switch, the package was working fine > with PHP5. But when the user dropped PHP5 because after all he had PHP7 > already, then the application stopped working. I got this problem after an purging the php5 packages from my system (they were automatically installed and the system did not need them anymore because it replaced them with PHP7 packages). > > So what I was suggesting is that something enables the latest available > PHP (i.e. 7 currently) when the currently enabled PHP (i.e. 5 in this > case) is being removed. And what about enabling PHP7 when these packages replace the previous automatically installed PHP5 packages ? Regards, Jean-Marc <jean-m...@6jf.be> pgpcCa8kEEOGK.pgp Description: PGP signature
Bug#865972: #865972 - same problem of false positive regarding PermitRootLogin parameter
Dear Maintainers, Another similar problem hits the PermitRootLogin parameter. The openssh-server in Debian testing / Buster (Version: 1:7.4p1-10+deb9u1) sets prohibit-password as default value for the PermitRootLogin parameter. If not present in the sshd_config file, rkhunter considers the default value as 'yes' allowing root access using password and will generate a warning. So, if the default value "prohibit-password" is secure enough, maybe changing this line ALLOW_SSH_ROOT_USER=unset can solve this. Regards, Jean-Marc <jean-m...@6jf.be> pgpL1OoPr4ckC.pgp Description: PGP signature
Bug#861657: minidlna: apt remove --purge minidlna does not purge user, group, /run/minidlna directory
On Wed, 3 May 2017 06:38:24 +0200 Jean-Marc <jean-m...@6jf.be> wrote: > > 2. Default installation creates directory /var/lib/minidlna as home > > directory for minidlna user and system administrator could put media > > files in there. > > I can't remove this directory completely on package purge, because > > admin, not minidlnad manage files in this directory. > > I can't remove minidlna user either, because this could lead > > to /var/lib/minidlna have numeric owner/group. The next package > > installed will use this free uid/gid and get access to the files. > > Please see https://wiki.debian.org/AccountHandlingInMaintainerScripts > > for some more explanation on the topic. > > Just for info, /var/lib/minidlna directory is not present anymore. > Anyway, I'll take a look at the wiki's page. I briefly looked at the wiki's page. And, apparently, there are reason to remove users accounts and reasons to not remove users accounts. So, I understand you opt to keep the user/group even after purging the package. If you do not see any reason to keep this bug open, can you, please, close it ? Regards, Jean-Marc <jean-m...@6jf.be> pgp6WLFV2hyE9.pgp Description: PGP signature
Bug#861657: minidlna: apt remove --purge minidlna does not purge user, group, /run/minidlna directory
Package: minidlna Version: 1.1.6+dfsg-1 Severity: normal Dear Maintainer, I just removed minidlna from my PC. And some pieces remain (minidlna user and group, /run/minidlna directory). Nothing really important but not really clean neither. Regards, JM -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#861657: minidlna: apt remove --purge minidlna does not purge user, group, /run/minidlna directory
Wed, 3 May 2017 00:56:16 +0300 Alexander Gerasiov <g...@cs.msu.su> écrivait : Hi Alexander, > Hello Jean-Marc, > > On Tue, 02 May 2017 13:39:03 +0200 > Jean-Marc <jean-m...@6jf.be> wrote: > > > Package: minidlna > > Version: 1.1.6+dfsg-1 > > Severity: normal > > > > Dear Maintainer, > > > > I just removed minidlna from my PC. > Sad news =) :-) > > > > > And some pieces remain (minidlna user and group, /run/minidlna > > directory). > > I do not consider this a bug. > > 1. /run should be cleaned on the next boot (it is tmpfs on typical > installations isn't it?). Right. Today, it disappears. > > 2. Default installation creates directory /var/lib/minidlna as home > directory for minidlna user and system administrator could put media > files in there. > I can't remove this directory completely on package purge, because > admin, not minidlnad manage files in this directory. > I can't remove minidlna user either, because this could lead > to /var/lib/minidlna have numeric owner/group. The next package > installed will use this free uid/gid and get access to the files. > Please see https://wiki.debian.org/AccountHandlingInMaintainerScripts > for some more explanation on the topic. Just for info, /var/lib/minidlna directory is not present anymore. Anyway, I'll take a look at the wiki's page. Thank you so much for your answer. > [...] > -- > Best regards, > Alexander Gerasiov > Regards, Jean-Marc <jean-m...@6jf.be> pgpnm40d2jspT.pgp Description: PGP signature
Bug#876760: unattended-upgrades.postinst script calls dpkg-vendor
Package: unattended-upgrades
Version: 0.97
Severity: normal
Dear Maintainer,
Today's upgrade installed v 0.97.
And post installation script called dpkg-vendor (see [1]).
But dpkg-vendor is in dpkg-dev package.
Which is not installed on my system.
Is it an missing dependency or a mistake in the post install script ?
And what will be the consequences of these errors in the postinstall
script ?
Cheers,
Jean-Marc
-- [1]
Paramétrage de unattended-upgrades (0.97) ...
/var/lib/dpkg/info/unattended-upgrades.postinst: 65:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
/var/lib/dpkg/info/unattended-upgrades.postinst: 66:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
/var/lib/dpkg/info/unattended-upgrades.postinst: 124:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
/var/lib/dpkg/info/unattended-upgrades.postinst: 125:
/var/lib/dpkg/info/unattended-upgrades.postinst: dpkg-vendor: not found
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages unattended-upgrades depends on:
ii apt 1.5~rc4
ii apt-utils1.5~rc4
ii debconf 1.5.63
ii init-system-helpers 1.49
ii lsb-base 9.20170808
ii lsb-release 9.20170808
ii python3 3.5.3-3
ii python3-apt 1.4.0~beta3+b1
ii ucf 3.0036
ii xz-utils 5.2.2-1.3
Versions of packages unattended-upgrades recommends:
ii anacron 2.3-24
ii cron [cron-daemon] 3.0pl1-128+b1
Versions of packages unattended-upgrades suggests:
pn bsd-mailx
ii exim4-daemon-light [mail-transport-agent] 4.89-6
pn needrestart
-- debconf information:
unattended-upgrades/origins_pattern:
"origin=Debian,codename=${distro_codename},label=Debian-Security";
unattended-upgrades/enable_auto_updates: true
Bug#876760: unattended-upgrades.postinst script calls dpkg-vendor
Mon, 25 Sep 2017 22:08:31 +0200 Alexandre Detiste <alexandre.deti...@gmail.com> écrivait : > Hi, Hi Alexandre, > > Maybe these call to dpkg-vendor could simply be replaced by > > test -f /etc/dpkg/origins/ubuntu > > ? > > An other way is to replace all the invocation of dpkg-vendor by a > single shell variable > which will be filled in the .postinst template at build time (dpkg-dev > is in build-essential). 2 questions: - what is the best way or the Debian recommendation to do this (testing a file or populating a variable) ? - do the maintainers need help to do it ? > > Greets, Cheers, > > Alexandre Jean-Marc <jean-m...@6jf.be> pgpCDZwa6ulmr.pgp Description: PGP signature
Bug#885553: /usr/lib/python3.6/lib2to3 not removed during update to 3.6.4-2
On Wed, 27 Dec 2017 22:53:37 +0100 Laurent Bigonville <bi...@debian.org> wrote: > Package: python3.6-2to3 > Version: 3.6.4-2 > Severity: important > > Hi, Hi Laurent, > > During the update from 3.6.4-1 to 3.6.4-2, I see the following messages: > > Dépaquetage de python3.6-2to3 (3.6.4-2) sur (3.6.4-1) ... > dpkg: avertissement: impossible de supprimer l'ancien répertoire « > /usr/lib/python3.6/lib2to3/pgen2 » : Le dossier n'est pas vide > dpkg: avertissement: impossible de supprimer l'ancien répertoire « > /usr/lib/python3.6/lib2to3/fixes » : Le dossier n'est pas vide > dpkg: avertissement: impossible de supprimer l'ancien répertoire « > /usr/lib/python3.6/lib2to3 » : Le dossier n'est pas vide > > It seems that these directories still contains __pycache__ directories and > some files in them. > > These should be removed during the upgrade I got the same after package python3.6-2to3 migrated to testing today. > > Regards, > > Laurent Bigonville > Regards, Jean-Marc <jean-m...@6jf.be> pgpepRXx1Azyq.pgp Description: PGP signature
Bug#891434: the same on 2 Acer Aspire V13 PC's
On Wed, 07 Mar 2018 11:13:02 -0500 Rann Bar-On <r...@duke.edu> wrote: > Is this still the case with 2.02+dfsg1-3 or has it been fixed? Yes, it is. I experinced the same issue on 2 Acer Aspire V13 PC's. Updating GRUB to 2.02+dfsg1-2 and to 2.02+dfsg1-3. Both PC's left unbootable. Rescued with an install image + re-installing GRUB with the option --removable. I saved the logs if you are interested. Regards, Jean-Marc <jean-m...@6jf.be> pgpy3OdO2EOsf.pgp Description: PGP signature
Bug#909348: gdm3 upgrade from 3.28 to 3.30 tried to remove /usr/lib/udev/rules.d
Package: gdm3 Version: 3.30.0-1 Severity: normal Dear Maintainer, Today, upgrading my system, I got a message when gdm3 upgraded saying (sorry, it's in french): Dépaquetage de gdm3 (3.30.0-1) sur (3.28.2-4) ... dpkg: avertissement: impossible de supprimer l'ancien répertoire « /usr/lib/udev/rules.d » : Le dossier n'est pas vide dpkg: avertissement: impossible de supprimer l'ancien répertoire « /usr/lib/udev » : Le dossier n'est pas vide Impossible to remove the directory /usr/lib/udev/rules.d because it is not empty. I noticed the file /usr/lib/udev/rules.d/61-gdm.rules being present in this directory and the package contains the same but not in the same location anymore apparently moved to /lib/udev/rules.d. Is it possible the gdm3 upgrade tried to remove the directory instead of removing only this file ? Anyway, one of the upgraded package tried it. Here is the list of package included into my morning upgrade: Start-Date: 2018-09-22 07:45:26 Commandline: apt full-upgrade Requested-By: jim (1000) Upgrade: fonts-lyx:amd64 (2.3.0-3, 2.3.1-2-1), libiptcdata0:amd64 (1.0.4-6+b1, 1.0.5-2), libproxy1v5:amd64 (0.4.15-1, 0.4.15-2), foomatic-db-compressed-ppds:amd64 (20180604-1, 20180917-1), libproxy1-plugin-gsettings:amd64 (0.4.15-1, 0.4.15-2), gdm3:amd64 (3.28.2-4, 3.30.0-1), libgsf-1-114:amd64 (1.14.43-1, 1.14.44-1), gir1.2-gdm-1.0:amd64 (3.28.2-4, 3.30.0-1), libgdm1:amd64 (3.28.2-4, 3.30.0-1), whiptail:amd64 (0.52.20-6, 0.52.20-7), libnewt0.52:amd64 (0.52.20-6, 0.52.20-7), libproxy-tools:amd64 (0.4.15-1, 0.4.15-2), libgsf-1-common:amd64 (1.14.43-1, 1.14.44-1), libproxy1-plugin-networkmanager:amd64 (0.4.15-1, 0.4.15-2), openprinting-ppds:amd64 (20180604-1, 20180917-1), gstreamer1.0-libav:amd64 (1.15.0.1+git20180723+db823502-1, 1.15.0.1+git20180723+db823502-2), libsgutils2-2:amd64 (1.42-3, 1.44-1), gir1.2-gstreamer-1.0:amd64 (1.14.2-2, 1.14.3-1), libgsf-bin:amd64 (1.14.43-1, 1.14.44-1), libgstreamer1.0-0:amd64 (1.14.2-2, 1.14.3-1), wfrench:amd64 (1.2.3-11, 1.2.4-1), libdouble-conversion1:amd64 (2.0.1-5, 3.1.0-2) End-Date: 2018-09-22 07:45:43 I hope this will be helpfull. Regards, Jean-Marc -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 0.6.45-1 ii adduser 3.117 ii dconf-cli 0.30.0-1 ii dconf-gsettings-backend 0.30.0-1 ii debconf [debconf-2.0] 1.5.69 ii gir1.2-gdm-1.03.30.0-1 ii gnome-session [x-session-manager] 3.28.1-1 ii gnome-session-bin 3.28.1-1 ii gnome-settings-daemon 3.30.0-1 ii gnome-shell 3.30.0-1 ii gnome-terminal [x-terminal-emulator] 3.30.0-1 ii gsettings-desktop-schemas 3.28.0-1 ii libaccountsservice0 0.6.45-1 ii libaudit1 1:2.8.4-2 ii libc6 2.27-6 ii libcanberra-gtk3-00.30-6 ii libcanberra0 0.30-6 ii libgdk-pixbuf2.0-02.38.0+dfsg-6 ii libgdm1 3.30.0-1 ii libglib2.0-0 2.58.0-4 ii libglib2.0-bin2.58.0-4 ii libgtk-3-03.24.0-3 ii libkeyutils1 1.5.9-9.3 ii libpam-modules1.1.8-3.8 ii libpam-runtime1.1.8-3.8 ii libpam-systemd239-9 ii libpam0g 1.1.8-3.8 ii librsvg2-common 2.40.20-3 ii libselinux1 2.8-1+b1 ii libsystemd0 239-9 ii libwrap0 7.6.q-27 ii libx11-6 2:1.6.6-1 ii libxau6 1:1.0.8-1+b2 ii libxcb1 1.13-3 ii libxdmcp6 1:1.1.2-3 ii lsb-base 9.20170808 ii mutter [x-window-manager] 3.30.0-1 ii policykit-1 0.105-21 ii terminator [x-terminal-emulator] 1.91-1 ii ucf 3.0038 ii x11-common1:7.7+19 ii x11-xserver-utils 7.7+8 ii xfce4-session [x-session-manager] 4.12.1-6 ii xfwm4 [x-window-manager] 4.12.5-1 ii xterm [x-terminal-emulator] 335-1 Versions of packages gdm3 recommends: ii at-spi2-core2.30.0-2 ii desktop-base9.0.7
Bug#909348: gdm3 upgrade from 3.28 to 3.30 tried to remove /usr/lib/udev/rules.d
Sat, 22 Sep 2018 12:37:40 +0100 Simon McVittie écrivait : > Yes. It was a bug that it was in /usr/lib/udev/rules.d: it should always > have been in /lib/udev/rules.d. > > Is this a "merged /usr" system, where /lib is a symbolic link to /usr/lib? Indeed. My fault. $ ls -l / [...] lrwxrwxrwx 1 root root 7 jan 22 2017 lib -> usr/lib lrwxrwxrwx 1 root root 9 jan 22 2017 lib32 -> usr/lib32 lrwxrwxrwx 1 root root 9 jan 22 2017 lib64 -> usr/lib64 lrwxrwxrwx 1 root root10 jan 22 2017 libx32 -> usr/libx32 Please, close this bug. Sorry for this. The good part of it: I read doc about "merged /usr": https://wiki.debian.org/UsrMerge https://salsa.debian.org/md/usrmerge/raw/master/debian/README.Debian https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/ And I got a question: regarding the fact Debain seems adopting "merged /usr" (it has been the default since debootstrap 1.0.85 in Oct 2016), why did you say your file should always have been in /lib/udev ? Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgplInjwc9nUn.pgp Description: PGP signature
Bug#914332: Debian Bug report logs #914377 - python3: syntax error in rtupdate hook prevents configuration
Pyzo is not compatible with Python-3.7 because using of the reserved word 'async. See also Pyzo on github: https://github.com/pyzo/pyzo/issues/529 Seems to be fixed in Pyzo 4.6.0 and 4.6.1. This bug should be linked to https://bugs.debian.org/914332 Jean-Marc https://6jf.be/keys/ED863AD1.txt pgptjrKz6jaHa.pgp Description: PGP signature
Bug#914377: Bug 914377 - clarifying the situation
Hi Matthias, The first part of this (Reported by: James Van Zandt ) is related to the pyzo package and documented in the bug report #914332 (https://bugs.debian.org/914332 - Adrian Bunk is preparing a NMU). The second part of this (Message From: cruncher ) is related to the fs-uae package and documented in the bug report #914790 (https://bugs.debian.org/914790 - fixed in sid) Maybe this bug can be closed regarding this information. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpKOkndjOPqq.pgp Description: PGP signature
Bug#912324: BleachBit causing error since updating Firefox to Firefox Quantum 60.0 ESR Fixed ?
Hi Hugo, I just tested bleachbit (2.0-2) on my Debian testing/sid and it is perfectly working (I got no error messages). I am using Firefox-ESR 60.4.0esr-1 from testing/main. So, as described in the bleachbit issue (See [1]), I think Firefox ESR 60 broke bleachbit. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt [1] https://github.com/bleachbit/bleachbit/issues/401 pgpPIdSP0kBuk.pgp Description: PGP signature
Bug#923298: chromium: file overlap with chromium-sandbox without Conficts and/or Replaces
On Tue, 26 Feb 2019 08:39:22 -0500 Michael Gilbert wrote: > control: tag -1 pending > > This may not be common knowledge, but mixed suites have always been a > supported configuration. This is a legitimate bug. I have a fix > queued for the next -security upload. > > Best wishes, > Mike > > Hi Mike, Can you specify in which version this will be fixed ? I can see version 72.0.3626.121-1 in unstable but changelog does not mention this bug. Thank you. Regards, Jean-Marc
Bug#923298: chromium: file overlap with chromium-sandbox without Conficts and/or Replaces
On Tue, 26 Feb 2019 08:39:22 -0500 Michael Gilbert wrote: > control: tag -1 pending > > This may not be common knowledge, but mixed suites have always been a > supported configuration. This is a legitimate bug. I have a fix > queued for the next -security upload. > > Best wishes, > Mike > > Hi Mike, Can you specify in which version this will be fixed ? I can see version 72.0.3626.121-1 in unstable but changelog does not mention this bug. Thank you. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgp8jnrOQ_s54.pgp Description: PGP signature
Bug#921945: sylpheed: Sylpheed uses the wrong application for opening pdf files
Thu, 7 Mar 2019 10:15:39 +0100 Ricardo Mones écrivait : > control: forwarded -1 https://sylpheed.sraoss.jp/redmine/issues/312 > control: severity -1 wishlist > > Hi Jean-Marc, Hi Ricardo, > On Sun, Feb 10, 2019 at 01:57:28PM +0100, Jean-Marc wrote: > > Package: sylpheed > > Version: 3.7.0-4 > > Severity: normal > > > > Dear Maintainer, > > > > Sylpheed does not take into account the XDG default application the > > desktop environment should use for opening files of a specific > > MIME/Filetype. > > > > Example: . when I tried to open a PDF file, Sylpheed uses gimp to open > > the file. > > > > Gimp is the first application in the > > /usr/share/applications/mimeinfo.cache entry defining which > > application(s) can read/open/associate with pdf files. > > > > $ grep application/pdf /usr/share/applications/mimeinfo.cache > > application/pdf=gimp.desktop;inkscape.desktop;org.gnome.Evince.desktop;libreoffice-draw.desktop; > > > > It should use my desktop's default application from Debian Gnome > > default spec in /usr/share/applications/gnome-mimeapps.list to open > > PDF files. > > AFAIK Sylpheed is not a GNOME application, is just a GTK+2 application. I am speaking about taking into account the Cross-Desktop Group (XDG) spec. I had mentionned the file containing the Debian default values for my desktop as example. It has nothing to do with Gnome in particular. See https://www.freedesktop.org/ for more info. . Association between MIME types and applications https://specifications.freedesktop.org/mime-apps-spec/latest/ or in this one-page: https://specifications.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.1.html > Anyway I'm forwarding this upstream, just in case they may consider > worth to implement it for a better user experience. Thank you. > thanks for reporting, > -- > Ricardo Mones Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpR9g_iS3NCv.pgp Description: PGP signature
Bug#912864: openssl: new version of openssl breaks some openvpn clients
On Mon, 26 Nov 2018 23:41:13 +0100 Sebastian Andrzej Siewior wrote: > On 2018-11-04 22:15:04 [+0100], Kurt Roeckx wrote: > > > You're implying openvpn doesn't pick up the openssl.cnf changes so I > > > have to set tls-version-min 1.0 in the server side configuration? OK, > > > that works too. > > > > Your client doesn't support the settings in the openssl.cfg file. Your > > openvpn client by defaults does TLS 1.0 only. The only way for your client > > to do something other than TLS 1.0 is set the tls-version-min variable > > to something. If you set it to 1.0, it will do any version > > supported by the openssl library higher than 1.0. > > James, is everything okay/clear? > The tls-version-min option for the older OpenVPN version should have > fixed things. > Is there anything else or can this be considered done? > > > Kurt > > Sebastian Hi James, May I ask you if you got all the answers you needed and if it fixed the problem. Thank you so much. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpbKgFaTfbY4.pgp Description: PGP signature
Bug#922547: linux-image-4.9.0-8-armmp: Failed to boot after upgrading to linux-image-4.9.0-8-armmp version 4.9.144-3
Package: src:linux Version: 4.9.130-2 Severity: normal Dear Maintainer, Today, I upgraded my Debian stable. This upgrade included a Linux image upgrade from 4.9.130-2 to 4.9.144-3. The ugrade went well but left my cubieboard unbootable. I tried to create a rescue SD disk using the firmware + partition images I found here: https://get.debian.org/debian/dists/stable/main/installer-armhf/current/images/netboot/SD-card-images/ But I got the same: an unbootable rescue disk. I finally need to boot on my backup SD disk apt-marking the package linux-image-4.9.0-8-armmp as hold. Jean-Marc -- Package-specific info: ** Version: Linux version 4.9.0-8-armmp (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.130-2 (2018-10-27) ** Command line: console=ttyS0,115200 quiet ** Not tainted ** Kernel log: [8.973619] Registered IR keymap rc-empty [8.974088] input: sunxi-ir as /devices/platform/soc@01c0/1c21800.ir/rc/rc0/input0 [8.974114] rc rc0: sunxi-ir as /devices/platform/soc@01c0/1c21800.ir/rc/rc0 [9.008281] sunxi-ir 1c21800.ir: initialized sunXi IR driver [9.086910] lirc_dev: IR Remote Control driver registered, major 242 [9.094194] rc rc0: lirc_dev: driver ir-lirc-codec (sunxi-ir) registered at minor = 0 [9.094209] IR LIRC bridge handler initialized [9.197604] input: axp20x-pek as /devices/platform/soc@01c0/1c2ac00.i2c/i2c-0/0-0034/axp20x-pek/input/input1 [9.293592] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok [9.417609] Adding 1000444k swap on /dev/mmcblk0p2. Priority:-1 extents:1 across:1000444k SSFS [ 11.391116] random: crng init done [ 11.391132] random: 7 urandom warning(s) missed due to ratelimiting [ 13.618733] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [ 13.850605] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 14.024784] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 14.157500] systemd-journald[193]: Received request to flush runtime journal from PID 1 [ 14.408922] EXT4-fs (mmcblk0p1): mounting ext2 file system using the ext4 subsystem [ 14.419429] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null) [ 15.810981] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.950694] sun4i-emac 1c0b000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 16.950732] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 31.099975] tun: Universal TUN/TAP device driver, 1.6 [ 31.099986] tun: (C) 1999-2004 Max Krasnyansky [ 121.770373] rc rc0: IR event FIFO is full! [ 121.774487] rc rc0: IR event FIFO is full! [ 121.778581] rc rc0: IR event FIFO is full! [ 121.782674] rc rc0: IR event FIFO is full! [ 121.786771] rc rc0: IR event FIFO is full! [ 121.790864] rc rc0: IR event FIFO is full! [ 121.794956] rc rc0: IR event FIFO is full! [ 121.799049] rc rc0: IR event FIFO is full! [ 121.803141] rc rc0: IR event FIFO is full! [ 121.807233] rc rc0: IR event FIFO is full! [ 121.811325] rc rc0: IR event FIFO is full! [ 121.815418] rc rc0: IR event FIFO is full! [ 121.819540] rc rc0: IR event FIFO is full! [ 121.823633] rc rc0: IR event FIFO is full! [ 121.827726] rc rc0: IR event FIFO is full! [ 121.831818] rc rc0: IR event FIFO is full! [ 121.835910] rc rc0: IR event FIFO is full! [ 121.840002] rc rc0: IR event FIFO is full! [ 121.844095] rc rc0: IR event FIFO is full! [ 121.848187] rc rc0: IR event FIFO is full! [ 121.852279] rc rc0: IR event FIFO is full! [ 121.856375] rc rc0: IR event FIFO is full! [ 121.860468] rc rc0: IR event FIFO is full! [ 121.864562] rc rc0: IR event FIFO is full! [ 307.911134] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 406.240378] systemd: 42 output lines suppressed due to ratelimiting [ 859.482624] rc rc0: IR event FIFO is full! [ 859.495934] rc rc0: IR event FIFO is full! [ 879.822042] rc rc0: IR event FIFO is full! [ 879.826157] rc rc0: IR event FIFO is full! [ 879.830265] rc rc0: IR event FIFO is full! [ 879.834358] rc rc0: IR event FIFO is full! [ 879.838449] rc rc0: IR event FIFO is full! [ 879.842540] rc rc0: IR event FIFO is full! [ 879.846632] rc rc0: IR event FIFO is full! [ 879.850725] rc rc0: IR event FIFO is full! [ 879.854818] rc rc0: IR event FIFO is full! [ 879.858910] rc rc0: IR event FIFO is full! [ 879.863002] rc rc0: IR event FIFO is full! [ 879.867112] rc rc0: IR event FIFO is full! [ 879.871206] rc rc0: IR event FIFO is full! [ 879.875299] rc rc0: IR event FIFO is full! [ 879.879391] rc rc0: IR event FIFO is full! [ 879.883483] rc rc0: IR event FIFO is full! [ 879.887576] rc rc0: IR event FIFO is full! [ 879.891667] rc rc0: IR event FIFO is full! [ 879.895759] rc rc0: IR event FIFO is full! [ 879.
Bug#921945: sylpheed: Sylpheed uses the wrong application for opening pdf files
Package: sylpheed Version: 3.7.0-4 Severity: normal Dear Maintainer, Sylpheed does not take into account the XDG default application the desktop environment should use for opening files of a specific MIME/Filetype. Example: . when I tried to open a PDF file, Sylpheed uses gimp to open the file. Gimp is the first application in the /usr/share/applications/mimeinfo.cache entry defining which application(s) can read/open/associate with pdf files. $ grep application/pdf /usr/share/applications/mimeinfo.cache application/pdf=gimp.desktop;inkscape.desktop;org.gnome.Evince.desktop;libreoffice-draw.desktop; It should use my desktop's default application from Debian Gnome default spec in /usr/share/applications/gnome-mimeapps.list to open PDF files. $ grep -i pdf /usr/share/applications/gnome-mimeapps.list application/pdf=org.gnome.Evince.desktop This association can be found using the xdg-mime command: $ xdg-mime query default application/pdf org.gnome.Evince.desktop And a file can be opened the right way using the xdg-open command. Regards, Jean-Marc See also: - Association between MIME types and applications https://specifications.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.1.html - XDG Base Directory Specification https://standards.freedesktop.org/basedir-spec/basedir-spec-0.8.html -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sylpheed depends on: ii libassuan0 2.5.2-1 ii libatk1.0-0 2.30.0-2 ii libc62.28-5 ii libcairo21.16.0-2 ii libcompfaceg11:1.5.2-5+b2 ii libenchant1c2a 1.6.0-11.1+b1 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7 ii libglib2.0-0 2.58.2-4 ii libgpg-error01.33-3 ii libgpgme11 1.12.0-6 ii libgtk2.0-0 2.24.32-3 ii libgtkspell0 2.0.16-1.2 ii libldap-2.4-22.4.47+dfsg-3 ii libonig5 6.9.1-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpangoft2-1.0-01.42.4-6 ii libssl1.11.1.1a-1 ii pinentry-gtk21.1.0-1+b1 ii sensible-utils 0.0.12 Versions of packages sylpheed recommends: ii aspell-fr [aspell-dictionary] 0.50-3-8 ii bogofilter 1.2.4+dfsg1-13 ii ca-certificates20190110 ii sylpheed-i18n 3.7.0-4 Versions of packages sylpheed suggests: pn claws-mail-tools ii curl 7.63.0-1 pn sylpheed-doc pn sylpheed-plugins -- no debconf information
Bug#921736: minissdpd: Script in d/minissdpd.config uses /sbin/ifconfig, but package does not depend on net-tools
On Fri, 08 Feb 2019 17:57:04 +0100 Tim Dengel wrote: > Package: minissdpd > Version: 1.5.20180223-5 > Severity: important > > Dear Maintainer, > > the script in debian/minissdpd.config uses /sbin/ifconfig, but the package > does not depend on net-tools, causing the script to fail on upgrades if > net-tools is not installed. > Is it possible to increase the bug severity to serious ? Increasing it to serious allows apt-listbugs to list it in case of upgrade. Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpjmWPf2mjFL.pgp Description: PGP signature
Bug#792490: [Pkg-openssl-devel] Bug#792490: openssl s_client doesn't allow for certificate pinning anymore!
On Mon, 7 Sep 2015 15:24:33 +0200 Kurt Roeckx wrote: > On Mon, Sep 07, 2015 at 02:56:44PM +0200, Florent Daigniere wrote: > > > > Agreed. The catch is that it's useless as a debugging tool too with the > > new behaviour (see bug #792396). There's no indication whatsoever that > > the system's CA path has been added to the certificate chain... and the > > manual goes as far as suggesting that it isn't: > > > > " > > -CApath directory > > The directory to use for server certificate verification. [...] > > " The bug reports a problem because "openssl s_client is not providing any way to disregard the system's trusted CAs anymore" found in version openssl/1.0.2d-1. I tested the option -no-CApath on a Debian stable (openssl 1.1.0j-1~deb9u1) and on a Debian testing/sid (openssl 1.1.1a-1) and it forced openssl to disregard the local system's CAs. Can you tell me if this is what you are looking for ? In this case, we can maybe ask to close this bug. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpY4sc1b3lAD.pgp Description: PGP signature
Bug#905720: acme-tiny: Please follow upstream versioning instead of date-based versions
On Sat, 6 Apr 2019 14:28:22 +0100 Samuel Henrique wrote: > Control: tags -1 patch > > Fix available on https://salsa.debian.org/samueloph/acme-tiny > > Discussion about the epoch bump: > https://lists.debian.org/debian-devel/2019/04/msg00052.html > > -- > Samuel Henrique Hi Samuel, I have a question about bugs 905720 and 924393. For both, you said there is a fix ([0]) and you mentionned the discution on debian-devel list ([1]) related the first epoch for acme-tiny. My question: do you think bug 905720 should be merged into bug 924393 ? I looked at them but (maybe I am wrong) I did not see any merge indication. Secondary question : what is blocking the fix ? You dropped this mail in April, the 6th. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt [0] https://salsa.debian.org/samueloph/acme-tiny [1] https://lists.debian.org/debian-devel/2019/04/msg00052.html pgpD5M7o4pjHS.pgp Description: PGP signature
Bug#894569: [Letsencrypt-devel] Bug#894569: acme-tiny: compatibility issues
On Thu, 5 Apr 2018 22:23:43 +0300 sergio wrote: > On 03/04/18 20:30, Sebastien Badia wrote: > > > The actual version in Debian stable (stretch) is 20160801-3+deb9u1. > > Could you please, tell us more about your problem ? > > Unfortunately I can't reproduce it more! But a week ago I had to > download the latest version from github (that successfully works) as > 20160801-3+deb9u1 produced some python Traceback. May be it were some > letsencrypt issues? > > > -- > sergio Hi Sergio, Any information to add to this bug report ? Can you reproduce it ? In case you cannot reproduce the issue, can this bug be closed ? Thanks in advance. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpBMNwuU5m2C.pgp Description: PGP signature
Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account
This problem seems to be solved in the last gnome-shell version (3.34.1+git20191024-1). You can close this bug report. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpuXLTRrWFC5.pgp Description: PGP signature
Bug#942272: gnome-shell: numlock state is reversed
Hi EdiD, I got numlock state problems too with this gnome-shell version. Mine were no similar to yours but seem to disappear with the last gnome-shell version (3.34.1+git20191024-1). Can you check if your problems still persist ? And confirm it in this bug report ? Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpTkKpcYvSeA.pgp Description: PGP signature
Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.
Package: fwupd Version: 1.3.2-2 Severity: normal Dear Maintainer, On my PC, fwupd-refresh.service failed to start. $ systemctl status fwupd-refresh.service ● fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2019-10-23 16:06:35 CEST; 2h 13min ago Docs: man:fwupdmgr(1) Process: 4608 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=0/SUCCESS) Process: 4624 ExecStart=/usr/bin/fwupdmgr get-updates --log 85-fwupd (code=exited, status=1/FAILURE) Main PID: 4624 (code=exited, status=1/FAILURE) oct 23 16:06:35 svrname systemd[1]: Starting Refresh fwupd metadata and update motd... oct 23 16:06:35 svrname fwupdmgr[4608]: Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz oct 23 16:06:35 svrname fwupdmgr[4608]: Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc oct 23 16:06:35 svrname systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE oct 23 16:06:35 svrname systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. oct 23 16:06:35 svrname systemd[1]: Failed to start Refresh fwupd metadata and update motd. That's the service definition: $ systemctl cat fwupd-refresh.service # /lib/systemd/system/fwupd-refresh.service [Unit] Description=Refresh fwupd metadata and update motd Documentation=man:fwupdmgr(1) After=network.target network-online.target systemd-networkd.service NetworkManager.service connman.service [Service] Type=oneshot RuntimeDirectory=motd.d CacheDirectory=fwupdmgr RuntimeDirectoryPreserve=yes StandardError=null ExecStart=/usr/bin/fwupdmgr refresh ExecStart=/usr/bin/fwupdmgr get-updates --log 85-fwupd DynamicUser=yes RestrictAddressFamilies=AF_NETLINK AF_UNIX AF_INET AF_INET6 SystemCallFilter=~@mount ProtectKernelModules=yes ProtectControlGroups=yes RestrictRealtime=yes And about the runtime directory: $ ls -ld /run/motd.d lrwxrwxrwx 1 root root 14 oct 23 16:06 /run/motd.d -> private/motd.d $ ls -ld /run/private/ drwx-- 3 root root 60 oct 23 16:06 /run/private/ $ sudo ls -ld /run/private/motd.d drwxr-xr-x 2 62803 62803 40 oct 23 16:06 /run/private/motd.d $ sudo ls -l /run/private/motd.d total 0 Kind Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwupd depends on: ii libarchive13 3.4.0-1 ii libc6 2.29-2 ii libefiboot137-2 ii libefivar1 37-2 ii libelf10.176-1.1 ii libfwupd2 1.3.2-2 ii libgcab-1.0-0 1.3-1 ii libglib2.0-0 2.62.1-1 ii libgnutls303.6.9-5 ii libgpg-error0 1.36-7 ii libgpgme11 1.13.1-1 ii libgudev-1.0-0 233-1 ii libgusb2 0.3.0-1 ii libjson-glib-1.0-0 1.4.4-2 ii libpolkit-gobject-1-0 0.105-26 ii libsmbios-c2 2.4.1-1 ii libsoup2.4-1 2.68.2-1 ii libsqlite3-0 3.30.1-1 ii libtss2-esys0 2.1.0-4+b1 ii libxmlb1 0.1.13-1 ii shared-mime-info 1.10-1 Versions of packages fwupd recommends: ii bolt 0.8-4 ii fwupd-amd64-signed [fwupd-signed] 1.3.2+2 ii python33.7.5-1 fwupd suggests no packages. -- no debconf information
Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.
Wed, 23 Oct 2019 16:40:37 + wrote : Hi Mario, > Internal Use - Confidential > > In 1.3.2-5 the service is disabled by default (and also this issue should be > fixed). Okay. So, the bug can be closed, I guess. Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpwpc8u5Cvgq.pgp Description: PGP signature
Bug#941908: gnome: unable to start gnome-shell, cursor only with no login
On Mon, 07 Oct 2019 14:26:28 -0500 william l-k wrote: > Thank you for your suggestions. I'll give it try and report back. gnome-shell 3.34 released to testing yesterday solving a similar issue (see https://bugs.debian.org/941782). Can you check if the problem you reported is also solved now after full-upgrading to the last testing version ? And in case it is, confirm it here ? Thank you for reporting this issue. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpOdldjbfrN_.pgp Description: PGP signature
Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account
On Wed, 09 Oct 2019 17:40:15 +0200 Jean-Marc wrote: > Package: gnome-shell > Version: 3.34.0-2 > Severity: normal > > Dear Maintainer, I would like to re-phrase : > Since the last upgrade from gnome-shell 3.30 to 3.34, the gnome-shell does > not take the gsettings org.gnome.desktop.peripherals.keyboard numlock-state > into account and always start with org.gnome.desktop.peripherals.keyboard > numlock-state set to false. I should have written : [...] and always start as if the value org.gnome.desktop.peripherals.keyboard numlock-state is set to false. It means, to be as clear as possible I can start with numlock-state set to true but the numpad will not render numbers. Hitting the numlock key changes the value of this setting and the behavior of the shell. Right now, the numlock-state value is false and the numpad returns numbers. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgphxaKb1AFVn.pgp Description: PGP signature
Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account
Package: gnome-shell Version: 3.34.0-2 Severity: normal Dear Maintainer, Since the last upgrade from gnome-shell 3.30 to 3.34, the gnome-shell does not take the gsettings org.gnome.desktop.peripherals.keyboard numlock-state into account and always start with org.gnome.desktop.peripherals.keyboard numlock-state set to false. I set "org.gnome.desktop.peripherals.keyboard remember-numlock-state true" on my system. to keep the numlock-state to the same value reboot after reboot, session after session. So, when GDM starts, it remembers the last numlock-state. With gnome-shell 3.30, it was the same. Now, with gnome-shell 3.34, it always start with numlock-state set to false leading to strange behaviors. For example, if I leave the session with numlock on, when I re-open a new session, gsettings show this: $ gsettings list-recursively | grep keyboard.*numlock org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state true and my numlock key on my keyboard is set to on too (with the led swtiched to on) but when I type on the numpad, I do not get numbers. I have to type on numlock key, swithing the led off to get my numpad working as it was on. For example, now, that's my setting: $ gsettings list-recursively | grep keyboard.*numlock org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state false and the numpad with the led off gives numbers. I hope I am clear in my explanations. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.34.0-1 ii evolution-data-server3.34.0-3 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-atspi-2.0 2.34.0-3 ii gir1.2-freedesktop 1.62.0-2 ii gir1.2-gcr-3 3.33.4-2 ii gir1.2-gdesktopenums-3.0 3.34.0-2 ii gir1.2-gdm-1.0 3.34.0-2 ii gir1.2-geoclue-2.0 2.5.5-1 ii gir1.2-glib-2.0 1.62.0-2 ii gir1.2-gnomebluetooth-1.03.34.0-1 ii gir1.2-gnomedesktop-3.0 3.34.0-2 ii gir1.2-gtk-3.0 3.24.12-1 ii gir1.2-gweather-3.0 3.28.3-2 ii gir1.2-ibus-1.0 1.5.19-4+b1 ii gir1.2-mutter-5 3.34.0-4 ii gir1.2-nm-1.01.20.2-1 ii gir1.2-nma-1.0 1.8.22-2 ii gir1.2-pango-1.0 1.42.4-7 ii gir1.2-polkit-1.00.105-26 ii gir1.2-rsvg-2.0 2.44.14-1 ii gir1.2-soup-2.4 2.68.1-2 ii gir1.2-upowerglib-1.00.99.11-1 ii gjs 1.58.0-2 ii gnome-backgrounds3.34.0-1 ii gnome-settings-daemon3.34.0-3 ii gnome-shell-common 3.34.0-2 ii gsettings-desktop-schemas3.34.0-2 ii libatk-bridge2.0-0 2.34.0-3 ii libatk1.0-0 2.34.0-1 ii libc62.29-2 ii libcairo21.16.0-4 ii libcroco30.6.13-1 ii libecal-2.0-13.34.0-3 ii libedataserver-1.2-243.34.0-3 ii libgcr-base-3-1 3.33.4-2 ii libgdk-pixbuf2.0-0 2.38.2+dfsg-1 ii libgirepository-1.0-11.62.0-2 ii libgjs0g 1.58.0-2 ii libgles2 1.1.0-1+b1 ii libglib2.0-0 2.62.0-3 ii libglib2.0-bin 2.62.0-3 ii libgnome-autoar-0-0 0.2.3-2 ii libgstreamer1.0-01.16.1-1 ii libgtk-3-0 3.24.12-1 ii libical3 3.0.5-2 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-5-03.34.0-4 ii libnm0 1.20.2-1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0
Bug#941782: gir1.2-gnomedesktop-3.0 3.34.0-2 breaks gnome-shell
On Sat, 5 Oct 2019 15:33:34 -0700 Mike Miller wrote: > Package: gir1.2-gnomedesktop-3.0 > Version: 3.34.0-2 > Followup-For: Bug #941782 > > Affected by this today, gnome-shell is completely non-functional with > the version of gir1.2-gnomedesktop-3.0 now in testing. Confirm that > installing the stable version of the package (3.30.2.1-2) restores it. and to restore/install the stable version of the package gir1.2-gnomedesktop-3.0 1/ add the stable to your source.list 2/ sudo apt update 3/ sudo apt install gir1.2-gnomedesktop-3.0=3.30.2.1-2 4/ sudo apt-mark hold gir1.2-gnomedesktop-3.0 Do not forget to mark it unhold once the bug will be fixed. > -- > mike I add this info to this bug because a lot of people asked for a solution on the #debian-next channel since yesterday. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpNkAmYYTk86.pgp Description: PGP signature
Bug#942234: gdm3: the button «Shutdown» does not work anymore
Package: gdm3 Version: 3.34.0-2 Severity: normal Dear Maintainer, Since the last upgrade to GDM 3.34, the shutdown button does not work anymore. If I click on it, I get the popup window with the three buttons (Cancel, Reboot, Shutdown) but clicking on Reboot or Shutdown just close this popup window and does nothing more. Looking in /var/log/daemon.log, I found this message each time I use the GDM Shutdown option: Oct 12 20:43:19 machineName gnome-session-binary[11980]: WARNING: Shutdown failed: GDBus.Error:org.freedesktop.DBus.Error.InteractiveAuthorizationRequired: Interactive authentication required. Moreover, I also notice this in the systemctl status gdm.service output: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Sat 2019-10-12 15:00:24 CEST; 6h ago Process: 1008 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1020 (gdm3) Tasks: 3 (limit: 4915) Memory: 11.2M CGroup: /system.slice/gdm.service └─1020 /usr/sbin/gdm3 oct 12 20:29:01 machineName gdm3[1020]: Child process -9036 was already dead. oct 12 20:42:28 machineName gdm-launch-environment][11942]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) oct 12 20:43:09 machineName gdm-password][12188]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type oct 12 20:43:25 machineName gdm-password][12196]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type oct 12 20:43:31 machineName gdm-password][12196]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type oct 12 20:43:31 machineName gdm-password][12196]: gkr-pam: unable to locate daemon control file oct 12 20:43:31 machineName gdm-password][12196]: pam_unix(gdm-password:session): session opened for user jim by (uid=0) oct 12 20:43:34 machineName gdm3[1020]: Child process -11964 was already dead. oct 12 21:05:27 machineName gdm-launch-environment][14042]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) oct 12 21:05:44 machineName gdm3[1020]: Child process -14060 was already dead. Maybe something missing since the last upgrade from 3.30. Maybe it is because of the file /etc/securetty. It was in the package login since Buster but it is not present in this package in Bullseye anymore. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 0.6.45-2 ii adduser 3.118 ii dconf-cli 0.34.0-1 ii dconf-gsettings-backend 0.34.0-1 ii debconf [debconf-2.0] 1.5.73 ii gir1.2-gdm-1.03.34.0-2 ii gnome-session [x-session-manager] 3.34.1-1 ii gnome-session-bin 3.34.1-1 ii gnome-settings-daemon 3.34.0-3 ii gnome-shell 3.34.0-2 ii gnome-terminal [x-terminal-emulator] 3.34.0-1 ii gsettings-desktop-schemas 3.34.0-2 ii libaccountsservice0 0.6.45-2 ii libaudit1 1:2.8.5-2 ii libc6 2.29-2 ii libcanberra-gtk3-00.30-7 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-02.38.2+dfsg-1 ii libgdm1 3.34.0-2 ii libglib2.0-0 2.62.1-1 ii libglib2.0-bin2.62.1-1 ii libgtk-3-03.24.12-1 ii libkeyutils1 1.6-6 ii libpam-modules1.3.1-5 ii libpam-runtime1.3.1-5 ii libpam-systemd242-7 ii libpam0g 1.3.1-5 ii librsvg2-common 2.44.14-1 ii libselinux1 2.9-2+b2 ii libsystemd0 242-7 ii libwrap0 7.6.q-28 ii libx11-6 2:1.6.8-1 ii libxau6 1:1.0.8-1+b2 ii libxcb1 1.13.1-2 ii libxdmcp6 1:1.1.2-3 ii lsb-base 11.1.0 ii mutter [x-window-manager] 3.34.0-4 ii policykit-1 0.105-26 ii procps2:3.3.15-2+b1 ii
Bug#949221: python3-enchant: Warning during the package installation: SyntaxWarning: "is" with a literal. Did you mean "=="?
Package: python3-enchant Version: 2.0.0-1 Severity: normal Dear Maintainer, Yesterday, during a full-upgrade, my Debian system automatically installed python3-enchant (2.0.0-1). During the package installation, I got a warning message: /usr/lib/python3/dist-packages/enchant/checker/CmdLineChecker.py:163: SyntaxWarning: "is" with a literal. Did you mean "=="? if index is 0: It seems with the last python 3 versions, this syntax starts to get warned about this being consider as a minor bug. Please, can you take this in charge ? Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-enchant depends on: ii libenchant1c2a 1.6.0-11.3 ii python3 3.7.5-3 python3-enchant recommends no packages. python3-enchant suggests no packages. -- no debconf information
Bug#901965: hid2hci.patch
Hi bluez maintainers, A person got in touch with debian-user-french people asking for help because she was facing the issue described in this bug report. I wonder if there is any progress on finding a solution ? For info, this problem is also mentionned in the bug report #889110 ([1]) (closed by Michael Biebl on 9 Feb 2018). And in the RedHat Bug 1563554 ([2]) suggesting a workaround by just adding in front of the line containing in the file /lib/udev/rules.d/97-hid2hci.rules. Can you, please, advice what is the best solution to, at least, mitigate the risk of being hit by this bug ? Specifying the ACTION like described in the RH bugreport or using the driver usbhid like in the Тут Root's proposed patch. And about further investigations, unfortunately, I cannot reproduce the bug and, then, I am not able to investigate further to know if it is really a driver or kernel bug. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt [1] https://bugs.debian.org/889110 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1563554 pgpMRzCyEtr6N.pgp Description: PGP signature
Bug#956910: Bug fixes with packages from unstable
Install the next version of gnome-shell from unstable: sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpgFTeNEF7SN.pgp Description: PGP signature
Bug#956885: gnome: gdm fails to start up after bullseye upgrade
On Thu, 16 Apr 2020 11:30:01 -0500 "Julio C. Ortega" wrote: > I can confirm also that downgrading gir1.2-gnomedesktop-3.0 to 3.34.2-2 > solved the problem. You can also force the next version of gnome-shell from unstable. sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. > Julio C. Ortega Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpoNNqPZcVvR.pgp Description: PGP signature
Bug#956885: gnome: gdm fails to start up after bullseye upgrade
On Thu, 16 Apr 2020 11:30:01 -0500 "Julio C. Ortega" wrote: > I can confirm also that downgrading gir1.2-gnomedesktop-3.0 to 3.34.2-2 > solved the problem. You can also force the next version of gnome-shell from unstable. sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. > Julio C. Ortega Jean-Marc
Bug#953832: ImportError: /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block
Hi Faidon, Do you need some help ? Do you think reporting this upstream can help ? Also, I am not really used to report bug or help in bug triage. So, tell me if I am doing something wrong. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgp4u_NAgJZM2.pgp Description: PGP signature
Bug#970140: gramps: Python3.8 SyntaxWarning: "is not" with a literal. in exportvcalendar.py:205 during installation
Package: gramps Version: 5.1.3-1 Severity: normal Dear Maintainer, Since Python3.8, "is" and "is not" checks produce SyntaxWarning when used with certains type of literals. See release notes: https://docs.python.org/3.8/whatsnew/3.8.html#changes-in-python-behavior "The compiler now produces a SyntaxWarning when identity checks (is and is not) are used with certain types of literals (e.g. strings, numbers). These can often work by accident in CPython, but are not guaranteed by the language spec. The warning advises users to use equality tests (== and !=) instead." Please, replace "is not" with "!=" in /usr/lib/python3/dist-packages/gramps/plugins/export/exportvcalendar.py - line 205. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gramps depends on: ii gir1.2-gtk-3.03.24.22-1 ii librsvg2-22.48.8+dfsg-1 ii python3 3.8.2-3 ii python3-bsddb36.2.7-1.1+b1 ii python3-gi3.36.1-1 ii python3-gi-cairo 3.36.1-1 ii xdg-utils 1.1.3-2 Versions of packages gramps recommends: ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-gexiv2-0.10 0.12.1-1 ii gir1.2-osmgpsmap-1.01.1.0-7 ii graphviz2.42.2-4 ii python3-icu 2.5-1 Versions of packages gramps suggests: ii fonts-freefont-ttf20120503-10 ii gir1.2-goocanvas-2.0 2.0.4-1 ii gir1.2-gtkspell3-3.0 3.0.10-1 ii python3-numpy 1:1.19.1-1 ii python3-pil 7.2.0-1 pn rcs -- no debconf information
Bug#970337: fonts-open-sans: warning when purging the package
Package: fonts-open-sans Version: 1.11-1 Severity: normal Dear Maintainer, apt mentioned fonts-open-sans was automatically installed but not needed anymore. I then ran an apt autoremove --purge. During the purge, I got a warning because dpkg was not able to remove the directory /usr/share/fonts/truetype/open-sans, this directory being not empty. Indeed, it still contained one file named .uuid: $ ls -la /usr/share/fonts/truetype/open-sans total 12 drwxr-xr-x 2 root root 4096 sep 14 21:30 . drwxr-xr-x 21 root root 4096 jui 12 22:14 .. -rw-r--r-- 1 root root 36 fév 13 2020 .uuid Maybe something to manage in one of the control files. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#970140: gramps: Python3.8 SyntaxWarning: "is not" with a literal.
Followed up upstream: https://gramps-project.org/bugs/view.php?id=11641 Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpB6jufWn8Ea.pgp Description: PGP signature
Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles
I removed the 3 packages : sudo apt purge webext-noscript webext-privacy-badger webext-ublock-origin-firefox I then installed the 3 extensions from the Firefox add-ons repo. And everything works fine. So, most probably, FF80 checks add-ons and removes/disables old ones. I Cc this to webext maintainers. Maybe they are not aware of this problem. Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpvmfi2MLoVI.pgp Description: PGP signature
Bug#970337: fonts-open-sans: warning when purging the package
Apparently, there are already other bugs related to similar problems. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898522 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920928 These 3 have references to each other. This one has not : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909541 And this bug is being worked on: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040 Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpZHxB5UhTcJ.pgp Description: PGP signature
Bug#969174: Fixed here [was Re: Bug#969174: firefox: FF80 seems to have
broken all add-ons on existing profiles] Message-Id: <20200904132941.cacb8887fd7ab7f486ccc...@6jf.be> In-Reply-To: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 04 Sep 2020 01:33:53 +0200 Christoph Anton Mitterer wrote: > On Thu, 2020-09-03 at 22:43 +0200, Ra=C3=BAl S=C3=A1nchez Siles wrote: > > Fortunately 80.0.1-1 came around and this bug has been somehow > > fixed or not exposed. This is what I can tell so far. Let me know if > > I can provide any more helpful information. >=20 > yes... that seems to fix it... Not on my system. I though it was fixed because just after the upgrade to FF 80.0.1-1, the extensions re-appeared. But at the second start, they were gone again. It is a bit the same behavior that with FF80.0.1. If you disable+re-enable the extensions, they are back. But they disappear after briefly appearing once you re-start FF. > Cheers, > Chris. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpRC1DJ2d8Hb.pgp Description: PGP signature
Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»
Bug already reported 2 times: initramfs-tools: update-initramfs should not store temporary files on /boot https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929424 pigz: abort: write error on (No space left on device) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960181 The 2 bugs are all marked as DONE. In the second bug #960181, when marking it as DONE on Sun, 10 May 2020, Ben Hutchings reported this comment : « There may be a bug here, in that the /boot partition was too small. That has been fixed in the installer, but unfortunately we don't have a general way to grow the partition on installed systems. ». No way to check if there is a way to avoid this in the 2 scripts mkinitramfs and update-initramfs ? Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpekgKDlgIMh.pgp Description: PGP signature
Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles
On Fri, 28 Aug 2020 17:18:44 +0200 Christoph Anton Mitterer wrote: > Package: firefox > Version: 80.0-1 > Severity: normal > > > Hi. > > It seems that with FF80 all addons are broken in existing profiles. They're > shown > in the add-ons list, but e.g. their icons aren’t in the menu. > > E.g. ublock origin, noscript also don't seem to work... so it's not just a > display > issue. > > Cheers, > Chris I am facing the same issue. Add-ons installed, shown as active in the add-ons' menu but not appearing in the FF bar as they were with FF79. One remark nevertheless : if I open the page about:support and click on the button "Refresh Firefox..." and then re-start Firefox, I got the icon of the add-ons I installed through Debian packages meaning noScript, privacy Badger and uBlock Origin in the FF bar. Chris, can you try this ? But after browsing the web and re-starting FF, they disappeared again. Chris, Mike, did you install add-ons from Debian or directly from FF repository ? Maybe the current versions are not compatible with FF80. My installed packages: Packages Version =-= firefox 80.0-1 webext-noscript 10.1.9.6-2 webext-privacy-badger 2020.7.21-1 webext-ublock-origin 1.28.0+dfsg-1 Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpu5zBlp8Xi7.pgp Description: PGP signature
Bug#976640: git: git - trying to install git failed due to unmet dependencies
Package: git Version: 1:2.28.0-1 Severity: normal File: git Dear Maintainer, Trying to install git on my Debian testing system failed due to unmet dependencies. git seems to strictly depend on git-man git-man >> 1:2.28.0 but testing only contains 2.29.2-1 which leads to an impossible installation. Example : $ env LANG=C sudo apt install git 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: git : Depends: git-man (< 1:2.28.0-.) but 1:2.29.2-1 is to be installed E: Unable to correct problems, you have held broken packages. $ env LANG=C apt policy git-man git-man: Installed: (none) Candidate: 1:2.29.2-1 Version table: 1:2.29.2+next.20201030-1 1 1 https://mirror.as35701.net/debian experimental/main amd64 Packages 1:2.29.2-1 990 990 https://mirror.as35701.net/debian testing/main amd64 Packages 500 https://mirror.as35701.net/debian unstable/main amd64 Packages Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git depends on: pn git-man ii libc62.31-5 ii libcurl3-gnutls 7.72.0-1 pn liberror-perl ii libexpat12.2.10-1 ii libpcre2-8-0 10.34-7 ii perl 5.32.0-5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages git recommends: ii ca-certificates 20200601 ii less 551-2 ii openssh-client [ssh-client] 1:8.4p1-3 ii patch2.7.6-6 Versions of packages git suggests: ii gettext-base 0.19.8.1-10 pn git-cvs pn git-daemon-run | git-daemon-sysvinit pn git-doc pn git-el pn git-email pn git-gui pn git-mediawiki pn git-svn pn gitk pn gitweb
Bug#976640: git: git - trying to install git failed due to unmet dependencies
This was due to a system setting. Correcting the problem allowed me to install git without problem. Sorry for that. I'll close this bug report. Regards, -- Jean-Marc OpenPGP_signature Description: OpenPGP digital signature
Bug#972245: openjdk-11-jre-headless: WARNING: tempfile is deprecated; consider using mktemp instead.
Package: openjdk-11-jre-headless Version: 11.0.10+9-1 Followup-For: Bug #972245 Dear Maintainer, Still getting the warning about tempfile in today's upgrade. $ dpkg-query --control-show openjdk-11-jre-headless postinst | grep tempfile log=$(tempfile) log=$(tempfile) Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openjdk-11-jre-headless depends on: ii ca-certificates-java 20190909 ii java-common 0.72 ii libasound21.2.4-1.1 ii libc6 2.31-9 ii libcups2 2.3.3op1-7 ii libfontconfig12.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s1 10.2.1-6 ii libharfbuzz0b 2.7.4-1 ii libjpeg62-turbo 1:2.0.5-2 ii liblcms2-22.12~rc1-2 ii libnss3 2:3.60-1 ii libpcsclite1 1.9.0-1 ii libstdc++610.2.1-6 ii libx11-6 2:1.7.0-2 ii libxext6 2:1.3.3-1.1 ii libxi62:1.7.10-1 ii libxrender1 1:0.9.10-1 ii libxtst6 2:1.2.3-1 ii util-linux2.36.1-6 ii zlib1g1:1.2.11.dfsg-2 openjdk-11-jre-headless recommends no packages. Versions of packages openjdk-11-jre-headless suggests: ii fonts-dejavu-extra 2.37-2 pn fonts-indic pn fonts-ipafont-gothic pn fonts-ipafont-mincho pn fonts-wqy-microhei | fonts-wqy-zenhei ii libnss-mdns0.14.1-2 -- no debconf information
Bug#959125: xdg-desktop-portal-gtk: does not provide implementations for org.freedesktop.impl.portal.{ScreenCast,RemoteDesktop}
hi Pedro, On Wed, 29 Apr 2020 18:48:53 +0100 Simon McVittie wrote: Control: block -1 by 954022 On Wed, 29 Apr 2020 at 17:13:08 +0100, Pedro Ângelo wrote: > looking upstream, there's an issue reported about xdg-desktop-portal-gtk not > instantiating the ScreenCast and RemoteDesktop interfaces on Ubuntu It needs a newer version of pipewire (see #954022). > it seems to never return from the call to `createSession` The error behaviour when not everything needed is available is also not great (it should fail cleanly with an error rather than waiting forever). I'm not sure whether that's an xdg-desktop-portal or xdg-desktop-portal-gtk bug. smcv Simon said it needed a new pipewire version mentioning this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954022 This is fixed since 5/9/20. Can you check if the bug persists ? And close the bug if it is okay ? Regards, -- Jean-Marc OpenPGP_signature Description: OpenPGP digital signature
