Bug#898391: nvidia-driver-libs-nonglvnd: cannot upgrade due to libglvnd0 conflict
I'm also affected here: I'm trying to update to Mesa 17.3 after installing the 390.48.2~bpo9+3 drivers on my Stretch laptop (I'm using a hybrid graphics laptop so I need both drivers for my setup), but either I get updated Mesa or lose the nVidia blob due to conflicts with the new packaging specs (??), rendering my setup completely unupgradable and unusable.
Bug#755761: gdm3: Unable to start KDE after last gdm3 upgrade
Package: gdm3 Version: 3.12.2-2 Severity: critical Justification: breaks unrelated software After today's gdm3 upgrade on testing from 3.8 to 3.12, I'm unable to sucessfully logon onto my KDE4 setup. Here is what is happening here: after the gdm3 upgrade, if I try to start a KDE session by logging in, KDE hangs at the startup screen. Only the "harddrive" icon is shown. System remains responsive (can switch to VTs, can SSH in, mouse pointer still moves...). If I launch a task manager (like htop), there are about 3 "kdeinit4" process in a tree: /usr/bin/kdeinit4 --oom-pipe 4 +kcminit_startup CPU load during this hang remains at zero. There is no disk activity present. For all effects the system sat there, idle. After poking a bit those "hung" kdeinit4 processes with GDB, if I kill the one with the following backtrace: #0 0x7f38346195c0 in __read_nocancel () at ../sysdeps/unix/syscall- template.S:81 #1 0x004070d5 in _start () KDE resumes startup as usual (it's almost always the second-to-last kdeinit4 process in the tree). Another workaround is to switch to a different login manager (be it kdm or LightDM), and in such case KDE starts up without incident, but these aren't really good options to me as I like using GDM. Yesterday's systemd-sysv update doesn't seem to be relevant to this case, as the older version of gdm3 worked fine until today, when I received the faulty upgrade. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.37-2 ii adduser 3.113+nmu3 ii dconf-cli0.20.0-2 ii dconf-gsettings-backend 0.20.0-2 ii debconf [debconf-2.0]1.5.53 ii gir1.2-gdm3 3.12.2-2 ii gnome-session [x-session-manager]3.12.1-3 ii gnome-session-bin3.12.1-3 ii gnome-session-flashback [x-session-manager] 3.8.0-3 ii gnome-settings-daemon3.12.2-1 ii gnome-shell 3.12.2-3 ii gnome-terminal [x-terminal-emulator] 3.12.3-1 ii gsettings-desktop-schemas3.12.2-1 ii kde-window-manager [x-window-manager]4:4.11.9-1 ii konsole [x-terminal-emulator]4:4.13.1-1 ii libaccountsservice0 0.6.37-2 ii libatk1.0-0 2.12.0-1 ii libaudit11:2.3.7-1 ii libc62.19-7 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libgdm1 3.12.2-2 ii libglib2.0-0 2.40.0-3 ii libglib2.0-bin 2.40.0-3 ii libgtk-3-0 3.12.2-1+b1 ii libpam-modules 1.1.8-3 ii libpam-runtime 1.1.8-3 ii libpam-systemd 208-6 ii libpam0g 1.1.8-3 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii librsvg2-common 2.40.2-1 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-6 ii libsystemd-id128-0 208-6 ii libsystemd-journal0 208-6 ii libsystemd-login0208-6 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-2 ii libxau6 1:1.0.8-1 ii libxdmcp61:1.1.1-1 ii libxrandr2 2:1.4.2-1 ii lsb-base 4.1+Debian13 ii marco [x-window-manager] 1.8.1+dfsg1-1 ii mate-session-manager [x-session-manager] 1.8.1-4 ii mate-terminal [x-terminal-emulator] 1.8.0+dfsg1-3 ii metacity [x-window-manager] 1:2.34.13-1 ii policykit-1 0.105-6 ii ucf 3.0030 ii x11-common 1:7.7+7 ii x11-xserver-utils7.7+3 ii xterm [x-terminal-emulator] 308-1 V
Bug#742461: mate-settings-daemon enters a infinite crash/restart loop
Package: mate-settings-daemon Version: 1.8.0-1 Severity: grave Justification: renders package unusable After doing a apt dist-update last night, several core components of MATE were upgraded to 1.8 on my Jessie system. Normally I use KDE, but from time to time I also use MATE, but since that update I've been unable to reach a stable desktop. Everything starts to flicker badly: panels, menus, tray icons, desktop icons. Fonts and dialogs switch font sizes, menus are hard to use, and in general, the overall desktop feels extremely unstable and sluggish. Taking a look at dmesg, I find dozens of these: [ 621.039193] traps: mate-settings-d[12942] trap int3 ip:7ff691c3a3c9 sp:7fff62967f40 error:0 [ 621.583086] traps: mate-settings-d[12963] trap int3 ip:7f6cf8dbc3c9 sp:7fff2c45d9e0 error:0 [ 622.144056] traps: mate-settings-d[12982] trap int3 ip:7f8023b6d3c9 sp:7fff476512b0 error:0 [ 622.717133] traps: mate-settings-d[13009] trap int3 ip:7f1059c9d3c9 sp:7fff96c0a210 error:0 [ 623.261964] traps: mate-settings-d[13034] trap int3 ip:7f10dbc413c9 sp:7fffb5473430 error:0 [ 623.819512] traps: mate-settings-d[13061] trap int3 ip:7ff2d2bc13c9 sp:7fff21f21640 error:0 [ 624.355532] traps: mate-settings-d[13081] trap int3 ip:7f66db7843c9 sp:7fff11fbecc0 error:0 [ 624.899599] traps: mate-settings-d[13108] trap int3 ip:7f14966b33c9 sp:7fff2518efc0 error:0 [ 625.463491] traps: mate-settings-d[13135] trap int3 ip:7f1f5019b3c9 sp:7fffb9e93260 error:0 [ 626.051037] traps: mate-settings-d[13162] trap int3 ip:7f56a6a813c9 sp:7fff9fea4cb0 error:0 [ 626.602089] traps: mate-settings-d[13190] trap int3 ip:7f9c52e473c9 sp:7fff8217cf50 error:0 [ 627.186409] traps: mate-settings-d[13217] trap int3 ip:7fc7eaa183c9 sp:74926d10 error:0 [ 627.725624] traps: mate-settings-d[13236] trap int3 ip:7f426cf153c9 sp:7fffbbfd2bb0 error:0 [ 628.295965] traps: mate-settings-d[13262] trap int3 ip:7f6a982823c9 sp:7fff9418ab50 error:0 [ 628.829837] traps: mate-settings-d[13289] trap int3 ip:7f8d9cf5c3c9 sp:7fff50c74520 error:0 [ 629.450491] traps: mate-settings-d[13308] trap int3 ip:7f8b2c2663c9 sp:7fff4c84fb30 error:0 [ 630.016590] traps: mate-settings-d[13331] trap int3 ip:7f43da0fb3c9 sp:7fff38086700 error:0 [ 630.555314] traps: mate-settings-d[13358] trap int3 ip:7fd7a9b503c9 sp:7fff73a05c80 error:0 [ 631.119840] traps: mate-settings-d[13386] trap int3 ip:7ff4c042a3c9 sp:7fff48037df0 error:0 [ 631.707592] traps: mate-settings-d[13413] trap int3 ip:7f0056e3f3c9 sp:7fff8b866740 error:0 [ 632.264920] traps: mate-settings-d[13440] trap int3 ip:7f25142ff3c9 sp:7fffb113ab30 error:0 [ 632.814582] traps: mate-settings-d[13467] trap int3 ip:7fb5387d03c9 sp:7fff1a405f10 error:0 which matches the frequency of the desktop flickering, which means that mate-settings-daemon is at fault (it gets killed, desktop loses settings, it respawns, icons and widgets gets their colors and fonts back, then it gets killed again... and repated until I manage to logoff. Hence because of this, MATE is completely broken on my system. I've tried switching mate-settings-desktop backends (I had GStreamer, tried switching to Pulse) since the actual mate-settings-daemon binary seems to live on those, but to no avail - desktop is still unstable. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mate-settings-daemon depends on: ii mate-settings-daemon-gstreamer 1.8.0-1 mate-settings-daemon recommends no packages. mate-settings-daemon suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712105: foomatic-filters: foomatic-rip fails when using bjc250gs driver
Package: foomatic-filters Version: 4.0.17-1 Severity: grave Justification: renders package unusable I have a good old Canon BJC-250 printer that I've been using for years on my Linux stations. Currently it's plugged to an old Pentium box (since it's parport) running Wheezy which acts as a print server. The printer had worked flawlessly with older distros/CUPS/foomatic versions, and I'm using the bjc250gs drivers as it is the fastest driver for it (and it allows to tune some printer-specific features). However, since having moved all my systems to Wheezy (i386 and amd64, all clean installs), the bjc250gs driver is unusable for me, since it always causes foomatic-rip to end abruptly, and therefore nothing is sent to the printer. I had enabled debugging messages on CUPS, but found nothing interesting except for this: D [12/Jun/2013:20:40:42 -04-30] [Job 57] Options from the PPD file: D [12/Jun/2013:20:40:42 -04-30] [Job 57] D [12/Jun/2013:20:40:42 -04-30] [Job 57] D [12/Jun/2013:20:40:42 -04-30] [Job 57] D [12/Jun/2013:20:40:42 -04-30] [Job 57] File: D [12/Jun/2013:20:40:42 -04-30] [Job 57] D [12/Jun/2013:20:40:42 -04-30] [Job 57] D [12/Jun/2013:20:40:42 -04-30] [Job 57] D [12/Jun/2013:20:40:42 -04-30] [Job 57] Filetype: PDF D [12/Jun/2013:20:40:42 -04-30] [Job 57] Storing temporary files in /var/spool/cups/tmp D [12/Jun/2013:20:40:43 -04-30] [Job 57] File contains 1 pages D [12/Jun/2013:20:40:43 -04-30] [Job 57] Starting renderer with command: gs -dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -dNOINTERPOLATE -sDEVICE=bjccmyk -sPrinterType=BJC-250 -dDEVICEWIDTHPOINTS=612 -dDEVICEHEIGHTPOINTS=792 -r180x180 -sFeeder=Auto -sQuality=Normal -dInverse=false -dSmooth=false -dCompress=true -dComposeK=false -dLimitCheck=false -dPaperRed=255 -dPaperGreen=255 -dPaperBlue=255 -dRedGamma=1.0 -dGreenGamma=1.0 -dBlueGamma=1.0 -dGamma=1.0 -dRandom=15 -sOutputFile=- /var/spool/cups/tmp/foomatic-WeJjFP D [12/Jun/2013:20:40:43 -04-30] [Job 57] Starting process "kid3" (generation 1) D [12/Jun/2013:20:40:43 -04-30] [Job 57] Starting process "kid4" (generation 2) D [12/Jun/2013:20:40:43 -04-30] [Job 57] Starting process "renderer" (generation 2) D [12/Jun/2013:20:40:43 -04-30] [Job 57] JCL: 2345X@PJL D [12/Jun/2013:20:40:43 -04-30] [Job 57] D [12/Jun/2013:20:40:43 -04-30] [Job 57] D [12/Jun/2013:20:40:43 -04-30] [Job 57] renderer received signal 11 D [12/Jun/2013:20:40:43 -04-30] [Job 57] Kid3 exit status: 1 D [12/Jun/2013:20:40:43 -04-30] PID 10226 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9. It happens on ALL of my Wheezy installs (ranging from that old Pentium MMX-225 box all the way up to a Sandy Bridge i5 laptop). My only workaround is to use the Gutenprint driver, which not only is slower, but harder to set up and getting good print quality from that one is not exactly straightforward, unlike with bjc250gs. Trying to find documentation or useful resources online with foomatic-related errors it's like a shot in the dark, because there is nothing clear, just dozens and dozens of users with the same error, but on different printer/driver combinations, none of those apply to my case. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/2 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages foomatic-filters depends on: ii bash 4.2+dfsg-0.1 ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii libdbus-1-31.6.8-1 ii ucf3.0025+nmu3 Versions of packages foomatic-filters recommends: ii colord 0.1.21-1 ii cups1.5.3-5 ii cups-bsd [lpr] 1.5.3-5 ii cups-client 1.5.3-5 ii foomatic-db-engine 4.0.8-3 ii ghostscript 9.05~dfsg-6.3 ii poppler-utils 0.18.4-6 foomatic-filters suggests no packages. -- debconf information: foomatic-filters/ps_accounting: true foomatic-filters/custom_textfilter: foomatic-filters/title: foomatic-filters/config_parsed: true foomatic-filters/spooler: cups foomatic-filters/textfilter: Automagic foomatic-filters/filter_debug: false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
