Your message dated Sun, 3 Apr 2022 20:03:21 +0200 with message-id <yknhaco4kba22...@thunder.hadrons.org> and subject line Re: Bug#1008716: dpkg: unable to print since dpkg update has caused the Debian Bug report #1008716, regarding dpkg: unable to print since dpkg update to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dpkg Version: 1.21.6 Severity: important Tags: upstream X-Debbugs-Cc: compte.perso.de-al...@bbox.fr Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? dpkg updates * What exactly did you do (or not do) that was effective (or ineffective)? I have updated my system (my sid) * What was the outcome of this action? a monstrous mess in the system. usb media (keys, disks, printers) no longer work. when I turn on my second screen (hot), as well as when I turn it off, the desktop crashes systematically and I'm always back to the login screen. * What outcome did you expect instead? I was hoping that my pc would work better but it didn't. *** End of the template - remove these template lines *** now, since the last update of dpkg (1.21.6), the usb supports work again. but still not the printer. h.p. envy 5536 : driverless , cups-filters 1.28.7 : ok under stable . still not under sid (3.31.12 I think) I think I have tried everything. Can you help me? and for this login problem (AMD RX 6800) ? and for this printer problem ? I'm waiting for your requests / advices .... -- Package-specific info: This system uses merged-usr-via-aliased-dirs, going behind dpkg's back, breaking its core assumptions. This can cause silent file overwrites and disappearances, and its general tools misbehavior. See <https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge>. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-5-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dpkg depends on: ii libbz2-1.0 1.0.8-5 ii libc6 2.33-7 ii liblzma5 5.2.5-2 ii libselinux1 3.3-1+b2 ii tar 1.34+dfsg-1 ii zlib1g 1:1.2.11.dfsg-4 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 2.4.3 pn debsig-verify <none> -- no debconf information
--- End Message ---
--- Begin Message ---Hi! On Thu, 2022-03-31 at 09:16:37 +0200, alain wrote: > Package: dpkg > Version: 1.21.6 > Severity: important > Tags: upstream > X-Debbugs-Cc: compte.perso.de-al...@bbox.fr > * What led up to the situation? > dpkg updates I very much doubt this. It might have happened while dpkg was also being upgraded, but that's just coincidental. I've skimmed over the discussion on the forum link you posted, and it seems you upgraded while the transition from python 3.9 to 3.10 was/is going on, which ended up with the removal of several components from your desktop and printing system, which resulted in those stopping working. On some of the logs you included there were also some worrying IO errors from your disk, so there could also be that. In any case, I don't see how this is dpkg related. If you need further assistance, please ask on the debian-user mailing list or one of the other support channels. I'm thus closing this report. Thanks, Guillem
--- End Message ---
