Bug#1076599: Fixed in upstream version 24.08
As nothing happened and the KDE6 transition is ongoing, I manually compiled the 24.08 upstream and it works. -- eric
Bug#1079022: Yes please do not close: it saved my ass via apt-listbug
So I second to not close critical bugs that can be caught via apt-listbug (I mean when you do not hit the extra liblz4-1 that breaks apt-listbug). --eric
Bug#1075969: python3-fitz: error when launching pymupdf
Package: python3-fitz Version: 1.24.2+ds1-2 Severity: grave Justification: renders package unusable /usr/bin/pymupdf Traceback (most recent call last): File "/usr/bin/pymupdf", line 5, in from fitz.__main__ import main ModuleNotFoundError: No module named 'fitz' dpkg -L python3-fitz /. /usr /usr/bin /usr/bin/pymupdf /usr/lib /usr/lib/python3 /usr/lib/python3/dist-packages /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/INSTALLER /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/METADATA /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/README.md /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/WHEEL /usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/entry_points.txt /usr/lib/python3/dist-packages/fitz_old /usr/lib/python3/dist-packages/fitz_old/__init__.py /usr/lib/python3/dist-packages/fitz_old/__main__.py /usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-311-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-312-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/fitz_old/fitz_old.py /usr/lib/python3/dist-packages/fitz_old/table.py /usr/lib/python3/dist-packages/fitz_old/utils.py -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.37 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-fitz depends on: ii libc62.39-3.1 ii libfreetype6 2.13.2+dfsg-1+b4 ii libgumbo20.12.0+dfsg-2+b1 ii libharfbuzz0b8.3.0-2+b1 ii libjbig2dec0 0.20-1+b2 ii libjpeg62-turbo 1:2.1.5-3 ii libmujs3 1.3.3-3+b2 ii libopenjp2-7 2.5.0-2+b3 ii python3 3.12.2-1 python3-fitz recommends no packages. python3-fitz suggests no packages. -- no debconf information
Bug#1071215: shim-signed 15.8 still on hold. Inconsistencies with shim-helpers-amd64-signed based on 15.8
On 18/05/2024 10:26, Eric Valette wrote: Thanks for the updated package. What remains not so clear for me is: 1) Why do you publish other package that are parts of the same source code until shim-signed did pass the 5) step and have step 6), 2) Why shim-helpers-amd64-signed does not depend on shim-signed instead of shim-unsigned. At least you do not answer to 2) above dpkg -s shim-helpers-amd64-signed Package: shim-helpers-amd64-signed Status: install ok installed Priority: optional Section: admin Installed-Size: 933 Maintainer: Debian EFI team Architecture: amd64 Version: 1+15.8+1 Replaces: shim (<< 15+1533136590.3beb971-3~), shim-signed (<< 1.29) Depends: shim-unsigned (>= 15.8-1) Breaks: shim-signed (<< 1.29) Conflicts: shim (<< 15+1533136590.3beb971-3~) Description: boot loader to chain-load signed boot loaders (signed by Debian) This package provides a minimalist boot loader which allows verifying signatures of other UEFI binaries against either the Secure Boot DB/DBX or against a built-in signature database. Its purpose is to allow a small, infrequently-changing binary to be signed by the UEFI CA, while allowing an OS distributor to revision their main bootloader independently of the CA. . This package contains the MOK manager and fall-back manager signed by the Debian UEFI CA to be used by shim-signed. Built-Using: shim (= 15.8-1) -- Eric Valette
Bug#1072931: ddclient: package in debian is rather old and does not work with IPV6 as it should. Upstream does.
Package: ddclient Version: 3.10.0-2.1 Severity: wishlist Thare has been several upstream versions since 3.10.0_2 (at least 5). The reworked support for IPV6 is fine. Removing patches series and changing file path for dhclient-exit-hooks is sufficient to build (altough I think the script is for up not down but...). -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.32 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ddclient depends on: ii debconf [debconf-2.0] 1.5.86 ii init-system-helpers1.66 ii perl 5.38.2-5 Versions of packages ddclient recommends: ii iproute2 6.9.0-1 pn libdigest-sha-perl ii libio-socket-inet6-perl 2.73-1 ii libio-socket-ssl-perl2.085-1 ii perl [libjson-pp-perl] 5.38.2-5 ddclient suggests no packages.
Bug#1038247: IPV6 works with git upstream version
I have taken a snapshot of git some moths ago (February or march) and it does work with both IPV4 and IPV6 at the same time. Installed the original package and then did dh_autoreconf and other stuff to build the new package after copying debian directory from original package. NB: patches series do not apply and are not really needed (touch for some missing file like NEWS is enough). Time to package a git version (anyway 3.10.0 is several version behind upstream last version). -- Eric Valette
Bug#1072624: gsmartcontrol: Does not start
Package: gsmartcontrol Version: 1.1.4+git20240531.25f1c62-1 Severity: grave Justification: renders package unusable gsmartcontrol-root [app] hz::data_file_find(): Data file "[ui:]gsc_executor_log_window.glade" not found. [app] Fatal error: Cannot create UI-resource widgets: Failed to open file â\x80\x9câ\x80\x9d: No such file or directory [app] hz::data_file_find(): Data file "[ui:]gsc_main_window.glade" not found. [app] Fatal error: Cannot create UI-resource widgets: Failed to open file â\x80\x9câ\x80\x9d: No such file or directory [app] Cannot create the main window. Exiting. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.32 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gsmartcontrol depends on: ii libatkmm-1.6-1v52.28.4-1+b1 ii libc6 2.39-3 ii libcairo2 1.18.0-3+b1 ii libcairomm-1.0-1v5 1.14.5-1 ii libgcc-s1 14.1.0-1 ii libglib2.0-0t64 2.80.2-2 ii libglibmm-2.4-1t64 2.66.7-1 ii libgtk-3-0t64 3.24.42-1 ii libgtkmm-3.0-1t64 3.24.9-1 ii libpangomm-1.4-1v5 2.46.4-1+b1 ii libsigc++-2.0-0v5 2.12.1-2 ii libstdc++6 14.1.0-1 ii libwhereami00.0~git20240120.c5f6b01-1 ii smartmontools 7.4-2 gsmartcontrol recommends no packages. gsmartcontrol suggests no packages. -- no debconf information
Bug#1072290: add something about /tmp in /etc/fstab
You may add this sentence to the listchange : if you have an /tmp entry in /etc/fstab, the system will continue to mount /tmp as before meaning as specifiied in /etc/fstab/ In that case do not use the mask command mentionned above as the system will not boot. -- Eric Valette
Bug#1072290: I should add that the bug is due to bogus listchange wording
The way I read the message below is as this: /tmp will unconditionnaly mounted as a tmpfs file system (which I do not want). Uncondionnally does not mean "even if /tmp is explictly mounted in /etc/fstab". So this encourage user to do the command mentionned below. The previous setup is rather unclear. I tried to let the /tmp entry in /etc/fstab and do not do the mask command and then it boot but "/tmp is not by default a tmpfs" or by default should read unless otherwyse explicitly mounted via entry in /etc/fstab. - found in list-change systemd (256~rc3-3) unstable; urgency=medium - /tmp/ is now by default a tmpfs, via the tmp.mount unit provided upstream. The previous setup can be retained simply by masking the unit locally with: systemctl mask tmp.mount or: touch /etc/systemd/system/tmp.mount -------- -- Eric Valette
Bug#1072187: Just followed what is advised in the apt changelog
Found in apt-listchange message: changelog extract - systemd (256~rc3-3) unstable; urgency=medium - /tmp/ is now by default a tmpfs, via the tmp.mount unit provided upstream. The previous setup can be retained simply by masking the unit locally with: systemctl mask tmp.mount or: touch /etc/systemd/system/tmp.mount -- Eric Valette
Bug#1072187: Note that /tmp is an ext4 fs in my /etc/fstab
It is not a tmpfs but an ext4 fs with : /tmp ext4 default,discard,noatime,nodiratime 0 2 as the end of line UUID=x not being relevant. -- Eric Valette
Bug#1072187: Checked again uncommenting /tmp in /etc/fstab and doing the mask again => no boot
Very annoying. I have no link in /etc/systemd/system/tmp.mount -- Eric Valette
Bug#1072187: Not fixed even in rc3-6 when following the apt-changelist mask command system does still not boot
So I have tmp in /etc/fstab I followed the advice to perfrom systemctl mask tmp.mount I have a strange message about binfmt and grub-common failing and the reasons is that / is still ro If I remove the /tmp entry from fstab and do systemctl unmask tmp.mount and reboot the boot is correct. -- Eric Valette
Bug#1071215: shim-signed 15.8 still on hold. Inconsistencies with shim-helpers-amd64-signed based on 15.8
On 17/05/2024 22:19, Steve McIntyre wrote: The process of getting a new version of shim-signed is long and complex, and not entirely under our control: 1. Build shim, test the hell out of it. 2. Upload shim, wait for it to build, check that the binary is reproducible. 3. Submit a shim-review issue (or several) at https://github.com/rhboot/shim-review/issues . 4. Upload our binaries to Microsoft's site for signing. 5. Wait for the review (and maybe fix things), potentially multiple passes here. 6. Wait for the signature to come back. 7. Prepare the shim-signed package with the signed binaries, and test like hell. 8. Upload shim-signed. We're currently at step 5. For sure I knew that M$ was involved for signing the binaries so that BIOS EFI accept to load it. Thanks for the detailled explanation. What remains not so clear for me is: 1) Why do you publish other package that are parts of the same source code until shim-signed did pass the 5) step and have step 6), 2) Why shim-helpers-amd64-signed does not depend on shim-signed instead of shim-unsigned. But, again, thanks for the rationale and explanations. -- eric
Bug#1071215: shim-signed 15.8 still on hold. Inconsistencies with shim-helpers-amd64-signed based on 15.8
Package: shim-signed Version: 1.40+15.7-1 Severity: normal For about two weeks, shim-helpers-amd64-signed is at version 15.8 (I have downgraded and put it on hold) but corresponding shim-signed is apparently blocked and not entering unstable. Any rationale? -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.30 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages shim-signed depends on: ii grub-efi-amd64-bin 2.12-2 ii grub2-common 2.12-2 hi shim-helpers-amd64-signed 1+15.7+1 ii shim-signed-common 1.40+15.7-1 shim-signed recommends no packages. shim-signed suggests no packages. -- no debconf information
Bug#1070986: This is a bug in debian scripts not upstream
On 14/05/2024 23:39, Tom Overlund wrote: It's actually upstream. I ran the same: $ make bindeb-pkg on the upstream source as I did on the Debian source, and yes, it gave me .deb packages. Here's the repo for the upstream script that was part of the problem: https://github.com/torvalds/linux/commits/master/scripts/package/builddeb Note the recent changes. I may be wrong, and it's a Debian patch that is causing the problem, but from what I've seen of the code it's probably upstream. I suppose I could download an upstream version of 6.7, and verify it has the same problem, but since nobody on the Debian maintainer side seems to care, I won't bother. Okay. A workorange is explained there. If you do not need debug info for example. You can also look at the new script to see if it changed something for removing debug information for stripped modules. -- eric https://lore.kernel.org/lkml/zxmgqjm1466fq...@archie.me/T/
Bug#1070986: This is a bug in debian scripts not upstream
As title says, this is a bug in debian additionnal scripts to build the packages, not upstream. Using upstream code works but does not produce package and knowing exacltly the minimal kernel setup for debian is not obvious. Once you have a working .deb you can probably reuse the .config. -- eric
Bug#1070986: I already reported for 6.6 and answer was that you should not sign modules!
It has been a month and nobody did care on 6.6. I bet I may be identical for 6.7. NB : I reported other bugs as the localmodconfig options do not include many rather basic options (ISO 9660, usb disks, ...). This one can be fixed by adding the relevant config options... -- eric
Bug#1068851: Acknowledgement (bash calls sudo when sartting ?)
Closing. It is a resolver problem. For some reason, Network-anager does not read /etc/hosts and my fiber box, does not honor the host-name send in dhcp request. Grrr -- eric
Bug#1068851: bash calls sudo when sartting ?
Package: bash Version: 5.2.21-2 Severity: important LANG="C"; bash sudo: unable to resolve host tri-yann5: Name or service not known I downgraded sudo but no change. Probably related to something else but still. dash works normally. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.26 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bash depends on: ii base-files 13 ii debianutils 5.17 ii libc62.38-6 ii libtinfo66.4+20240113-1 Versions of packages bash recommends: ii bash-completion 1:2.11-8 Versions of packages bash suggests: ii bash-doc 5.2.21-2 -- no debconf information
Bug#1067611: privoxy takes more than 2 mins to start.
On 24/03/2024 19:01, Eric Valette wrote: On 24/03/2024 18:46, Roland Rosenfeld wrote: Hi Eric! What do you see in the output of systemctl status network-online.target privoxy.service On my system provoxy starts a the moment when network-online is active and takes 1 second to start. Can you see, when network-online is active on your system? Is it just after booting or does it also take these two minutes? I can browse internet via another browser or read mail with thunderbird while privoxy is still starting up. So network is up I have no idea for network-online precisely but still. systemctl status network-online.target privoxy.service ● network-online.target - Network is Online Loaded: loaded (/usr/lib/systemd/system/network-online.target; static) Active: active since Sun 2024-03-24 17:04:32 CET; 2h 4min ago Docs: man:systemd.special(7) https://systemd.io/NETWORK_ONLINE mars 24 17:04:32 tri-yann5 systemd[1]: Reached target network-online.target - Network is Online. ● privoxy.service - Privacy enhancing HTTP Proxy Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; preset: enabled) Active: active (running) since Sun 2024-03-24 17:04:33 CET; 2h 4min ago Docs: man:privoxy(8) https://www.privoxy.org/user-manual/ Main PID: 8125 (privoxy) Tasks: 9 (limit: 37429) Memory: 10.7M (peak: 30.9M) CPU: 1.423s CGroup: /system.slice/privoxy.service └─8125 /usr/sbin/privoxy --pidfile /run/privoxy.pid --user privoxy /etc/privoxy/config so apprently the culprit is network online that comes long after TCP/IP stack is up and running with both IPV4 and V6 available. systemctl is-enabled NetworkManager-wait-online.service systemd-networkd-wait-online.service enabled enabled So I guess I should disable networkd-wait-online.service -- eric
Bug#1067611: privoxy takes more than 2 mins to start.
On 24/03/2024 18:46, Roland Rosenfeld wrote: Hi Eric! Thank you for your bug report. On So, 24 Mär 2024, Eric Valette wrote: Package: privoxy Version: 3.0.34-3+b2 Severity: important Usually the first thing I do after booting is starting firefox. Here I have to start until privoxy starts which takes aroun two mins. I purged the package, reinstalled. No change. I didn't notice a problem with privoxy startup time, so let's try to track down what's the root cause of your problem is. privoxy waits for network-online.target before it starts. Maybe you could check, whether network-online or privoxy is delaying here. What do you see in the output of systemctl status network-online.target privoxy.service On my system provoxy starts a the moment when network-online is active and takes 1 second to start. Can you see, when network-online is active on your system? Is it just after booting or does it also take these two minutes? I can browse internet via another browser or read mail with thunderbird while privoxy is still starting up. So network is up I have no idea for network-online precisely but still. Even when the system is up, if I do service privoxy stop and then start it takes long so I bet it is privoxy. If the former, this isn't a privoxy issue, since privoxy has to wait for a working network, otherwise it isn't able to bind the interfaces (this was a problem in https://bugs.launchpad.net/ubuntu/+source/privoxy/+bug/1870101). If it's a problem in privoxy, that it is really starting up delayed, what do you see journalctl -u privoxy or in /varl/log/privoxy/logfile? I already did that without success. But I can try again. Maybe you should (temporarily) increase debug level in /etc/provoxy/config (maybe debug 4096 could be helpful, maybe others, too). Does your problem only happen on system startup or can you reproduce it via systemctl stop privoxy; systemctl start privoxy See above. Will spend some time to debug it but not now. Greetings Roland -- eric
Bug#1067611: privoxy takes more than 2 mins to start.
Package: privoxy Version: 3.0.34-3+b2 Severity: important Usually the first thing I do after booting is starting firefox. Here I have to start until privoxy starts which takes aroun two mins. I purged the package, reinstalled. No change. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.22 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages privoxy depends on: ii adduser3.137 ii debconf [debconf-2.0] 1.5.86 ii init-system-helpers1.66 ii libbrotli1 1.1.0-2+b3 ii libc6 2.38-6 ii libmbedcrypto7t64 2.28.7-1.1 ii libmbedtls14t642.28.7-1.1 ii libmbedx509-1t64 2.28.7-1.1 ii libpcre2-8-0 10.42-4+b1 ii logrotate 3.21.0-2 ii ucf3.0043+nmu1 ii zlib1g 1:1.3.dfsg-3.1 Versions of packages privoxy recommends: it doc-base 0.11.2 Versions of packages privoxy suggests: ii apparmor 3.0.12-1+b2 -- debconf information: privoxy/listen-address: 127.0.0.1:8118 [::1]:8118
Bug#1065310: I've been hit by this bug also
Using different package name, all with t64 in their names and yes it seams that Provides: is not taken into account for reverse depends. -- eric
Bug#1066976: linux-source-6.6: make localmodconfig does not configure USB storage, nor cdrom filesystem
Package: linux-source-6.6 Version: 6.6.15-2 Severity: normal After using make localmodconfig I discovered that USB keys cannot be mounted, nor ISO images. I think theses are basics that shoul be enabled like other stuffs. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.22 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-source-6.6 depends on: ii binutils 2.42-3 ii xz-utils 5.6.0-0.2 Versions of packages linux-source-6.6 recommends: ii bc1.07.1-3+b2 ii bison 2:3.8.2+dfsg-1+b1 ii build-essential 12.10 ii cpio 2.15+dfsg-1 ii flex 2.6.4-8.2+b2 ii kmod 32-1 ii libelf-dev0.191-1 ii libssl-dev3.2.1-2 ii linux-config-6.6 6.6.15-2 ii rsync 3.2.7-1+b2 Versions of packages linux-source-6.6 suggests: ii libncurses-dev [ncurses-dev] 6.4+20240113-1 ii pkg-config1.8.1-2 ii pkgconf [pkg-config] 1.8.1-2 ii qtbase5-dev 5.15.10+dfsg-7.2+b1 -- no debconf information
Bug#1066975: linux-source-6.6 fails to build if pahole is not installed
Package: linux-source-6.6 Version: 6.6.15-2 Severity: minor I never installed pahole before... It is not in the list of required package. -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.22 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-source-6.6 depends on: ii binutils 2.42-3 ii xz-utils 5.6.0-0.2 Versions of packages linux-source-6.6 recommends: ii bc1.07.1-3+b2 ii bison 2:3.8.2+dfsg-1+b1 ii build-essential 12.10 ii cpio 2.15+dfsg-1 ii flex 2.6.4-8.2+b2 ii kmod 32-1 ii libelf-dev0.191-1 ii libssl-dev3.2.1-2 ii linux-config-6.6 6.6.15-2 ii rsync 3.2.7-1+b2 Versions of packages linux-source-6.6 suggests: ii libncurses-dev [ncurses-dev] 6.4+20240113-1 ii pkg-config1.8.1-2 ii pkgconf [pkg-config] 1.8.1-2 ii qtbase5-dev 5.15.10+dfsg-7.2+b1 -- no debconf information
Bug#1065819: linux-source-6.6 cannot be rebuild according to debian documentation
On 10/03/2024 12:25, Bastian Blank wrote: Control: severity -1 important Yes, the kernel included Debian package support can't handle compressed modules in various ways. Just disable them for now. OK. Will try. Maybe doc should be updated until it is fixed. It however means that you cannot get the same linux-image when you rebuild. Plus it annoys me to revert back my own script for external modules signature. Thanks anyway. -- eric
Bug#1065819: linux-source-6.6 cannot be rebuild according to debian documentation
Package: linux-source-6.6 Version: 6.6.15-2 Severity: grave Justification: renders package unusable As I wanted: 1) to stay on long term kernel 6.6 branch, 2) 6.7.x has been uploaded to unstable already, 3) I would like to enable NTFS3, and AMD TEE I decided I will try to recompile the kernel myself first (I have MOK keys already registered and used to manually sign some external modules). I used the following debian documentation https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-getting https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-building cd linux-source-6.6 make localmodconfig and accepted the default values. Then make clean make bindeb-pkg And then it correctly builds the kernel and modules .ko file, then sign the ko and xz compress it to get foo.ko.xz. Here are extracts AR drivers/gpu/built-in.a AR drivers/built-in.a AR built-in.a AR vmlinux.a LD vmlinux.o OBJCOPY modules.builtin.modinfo GEN modules.builtin GEN .vmlinux.objs MODPOST Module.symvers CC .vmlinux.export.o UPD include/generated/utsversion.h CC init/version-timestamp.o LD .tmp_vmlinux.btf BTF .btf.vmlinux.bin.o LD .tmp_vmlinux.kallsyms1 NM .tmp_vmlinux.kallsyms1.syms KSYMS .tmp_vmlinux.kallsyms1.S AS .tmp_vmlinux.kallsyms1.S LD .tmp_vmlinux.kallsyms2 NM .tmp_vmlinux.kallsyms2.syms KSYMS .tmp_vmlinux.kallsyms2.S AS .tmp_vmlinux.kallsyms2.S LD vmlinux BTFIDS vmlinux NM System.map SORTTAB vmlinux RELOCS arch/x86/boot/compressed/vmlinux.relocs RSTRIP vmlinux ... SIGN debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/bluetooth.ko XZ debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/bluetooth.ko.xz INSTALL debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/rfcomm/rfcomm.ko SIGN debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/rfcomm/rfcomm.ko XZ debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/rfcomm/rfcomm.ko.xz INSTALL debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/bnep/bnep.ko SIGN debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/bnep/bnep.ko XZ debian/linux-image/lib/modules/6.6.15/kernel/net/bluetooth/bnep/bnep.ko.xz INSTALL debian/linux-image/lib/modules/6.6.15/kernel/net/rfkill/rfkill.ko SIGNdebian/linux-image/lib/modules/6.6.15/kernel/net/rfkill/rfkill.ko XZ debian/linux-image/lib/modules/6.6.15/kernel/net/rfkill/rfkill.ko.xz INSTALL debian/linux-image/lib/modules/6.6.15/kernel/virt/lib/irqbypass.ko SIGN debian/linux-image/lib/modules/6.6.15/kernel/virt/lib/irqbypass.ko XZ debian/linux-image/lib/modules/6.6.15/kernel/virt/lib/irqbypass.ko.xz DEPMOD debian/linux-image/lib/modules/6.6.15 INSTALL debian/linux-libc-dev/usr/include But then it tries to sign again the modules using the .ko file that does not exist: ls -l debian/linux-image/lib/modules/6.6.15/kernel/arch/x86/events/*.ko* -rw-rw-r-- 1 valette valette 103484 9 mars 19:39 debian/linux-image/lib/modules/6.6.15/kernel/arch/x86/events/rapl.ko.xz And fails with: SIGN debian/linux-image/lib/modules/6.6.15/kernel/arch/x86/events/rapl.ko At main.c:298: - SSL error:8002:system library::No such file or directory: ../crypto/bio/bss_file.c:67 - SSL error:1080:BIO routines::no such file: ../crypto/bio/bss_file.c:75 sign-file: debian/linux-image/lib/modules/6.6.15/kernel/arch/x86/events/rapl.ko make[6]: *** [scripts/Makefile.modinst:137 : debian/linux-image/lib/modules/6.6.15/kernel/arch/x86/events/rapl.ko] Erreur 1 make[5]: *** [Makefile:1846 : modules_install] Erreur 2 make[4]: *** [Makefile:2061 : run-command] Erreur 2 make[3]: *** [debian/rules:17 : binary-arch] Erreur 2 dpkg-buildpackage: erreur: le sous-processus make -f debian/rules binary a retourné lâ\x80\x99état de sortie 2 make[2]: *** [scripts/Makefile.package:146 : bindeb-pkg] Erreur 2 make[1]: *** [/usr/src/linux-source-6.6/Makefile:1563 : bindeb-pkg] Erreur 2 make: *** [Makefile:246 : __sub-make] Erreur 2 -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-source-6.6 depends on: ii binutils 2.42-3 ii xz-utils 5.6.0-0.2 Versions of packages linux-source-6.6 recommends: ii bc1.07.1-3+b1 ii bison 2:3.8.2+dfsg-1+b1 ii build-essential 12.10 ii cpio 2.15+dfsg-1 ii flex 2.6.4-8.2
Bug#1065015: reopen unti I can install the packages
reopen 1065015
Bug#1065015: the control file for the akonadi libraries are palin wrong
On Mon, 04 Mar 2024 05:41:21 +0100 Sune Stolborg Vuorela wrote: On Sunday, March 3, 2024 6:16:23 PM CET Eric Valette wrote: > The transition is completed but the package cannot install because of > Breaks: in the control file The transition is still on going. This is in absolute number of packages the biggest one ever. If it it wasn't for all of the newish languages like node/ js, go and rust it would also in the relative numbers be the biggest one ever. This remains the only packages I cannot install due to transition on all machines. apt install libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5akonadisearchcore5t64 libkf5akonadisearchpim5t64 libkf5akonadisearchxapian5t64 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: kaddressbook-data kdepim-themeeditors kirigami-addons-data libkf5eventviews5abi1 libkf5ksieveui5 libkf5mailimporter5 libkf5mailimporterakonadi5 libkf5templateparser5 libkpimaddressbookimportexport5 libqt5location5-plugins libqt5positioning5-plugins pim-sieve-editor qml-module-org-kde-kirigami-addons-labs-mobileform qml-module-qtlocation qml-module-qtpositioning Use 'apt autoremove' to remove them. The following packages will be REMOVED: akonadiconsole kaddressbook kalendar kde-standard kmail knotes korganizer libkf5akonadisearchcore5 libkf5akonadisearchpim5 libkf5akonadisearchxapian5 libkf5incidenceeditor5abi1 libkf5mailcommon5abi2 libkf5messagecomposer5abi1 libkf5messagelist5abi1 libkf5pimcommonakonadi5abi1 mbox-importer pim-data-exporter The following packages will be upgraded: libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5akonadisearchcore5t64 libkf5akonadisearchpim5t64 libkf5akonadisearchxapian5t64 5 upgraded, 0 newly installed, 17 to remove and 3 not upgraded. Need to get 277 kB of archives. After this operation, 59.5 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. And apt install libkf5akonadisearch-bin libkf5akonadisearch-plugins libkf5akonadisearchcore5t64 libkf5akonadisearchpim5t64 libkf5akonadisearchxapian5t64 akonadiconsole kaddressbook kalendar Reading package lists... Done Building dependency tree... Done Reading state information... Done akonadiconsole is already the newest version (4:22.12.3-1). kaddressbook is already the newest version (4:22.12.3-1+b1). kalendar is already the newest version (22.12.3-2). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: akonadiconsole : Depends: libkf5akonadisearchcore5-22.12 Depends: libkf5akonadisearchxapian5-22.12 libkf5messagelist5abi1 : Depends: libkf5akonadisearchpim5-22.12 libkf5pimcommonakonadi5abi1 : Depends: libkf5akonadisearchpim5-22.12 E: Unable to correct problems, you have held broken packages.
Bug#1065388: libqt5core5t64: control files are wrong for all t64 qt libraries
Package: libqt5core5t64 Version: 5.15.10+dfsg-7.1 Severity: grave Justification: renders package unusable Package: libqt5core5t64 Source: qtbase-opensource-src Version: 5.15.10+dfsg-7.1 Architecture: amd64 Maintainer: Debian Qt/KDE Maintainers Installed-Size: 6061 Depends: shared-mime-info, libc6 (>= 2.35), libdouble-conversion3 (>= 2.0.0), libgcc-s1 (>= 3.4), libglib2.0-0t64 (>= 2.22.0), libicu72 (>= 72.1~rc-1~), libpcre2-16-0 (>= 10.22), libstdc++6 (>= 11), libzstd1 (>= 1.5.5), zlib1g (>= 1:1.1.4) Recommends: qttranslations5-l10n Suggests: libthai0 Breaks: libqt5core5a (<< 5.15.10+dfsg-7.1) Replaces: libqt5core5a Provides: libqt5core5a (= 5.15.10+dfsg-7.1), qtbase-abi-5-15-10 Section: libs Priority: optional Multi-Arch: same Homepage: https://www.qt.io/developers/ Description: Qt 5 core module Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide standard GUI functionality. . The QtCore module contains core non-GUI functionality. The Breaks: makes apt to search for a libqt5core5a >= 5.15.10+dfsg-7.1 but it will never exist as long as the package is not FIRST replaced by the t64 version. Removing the Breaks: make it installable and the provides expose the libqt5core5a as present. It has been stuck for 5 days already and I do not think this is due to the transition (except many package are uninstalable due to various error in control files). -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt5core5t64 depends on: ii libc6 2.38-6 ii libdouble-conversion3 3.3.0-1+b1 ii libgcc-s1 14-20240221-2.1 ii libglib2.0-0t642.78.4-2.1+b1 ii libicu72 72.1-4+b1 ii libpcre2-16-0 10.42-4+b1 ii libstdc++6 14-20240221-2.1 ii libzstd1 1.5.5+dfsg2-2 ii shared-mime-info 2.4-1 ii zlib1g 1:1.3.dfsg-3.1 Versions of packages libqt5core5t64 recommends: ii qttranslations5-l10n 5.15.10-2 Versions of packages libqt5core5t64 suggests: ii libthai0 0.1.29-2
Bug#1065015: the control file for the akonadi libraries are palin wrong
The transition is completed but the package cannot install because of Breaks: in the control file And I second that the abi provided should be without t64libkf5akonadisearchpim5-22.12 I managed to install removing the breaks in the package name and modifying the abi provided So nothing to do with transition. And You are not alone to make mistake in control files. -- eric
Bug#1065349: [Pkg-samba-maint] Bug#1065349: libsmbclient0: Actually breaks part of t64 transition
On 03/03/2024 14:50, Michael Tokarev wrote: Control: severity -1 important 03.03.2024 13:21, Eric Valette : Package: libsmbclient0 Version: 2:4.19.5+dfsg-3 Severity: grave Justification: renders package unusable This is wrong, in my opinion. The effect of this bug on platforms unaffected by time64_t transition is exactly the same as on platforms affected by the transition. apt download libsmbclient0 Réception de :1 http://ftp.de.debian.org/debian unstable/main amd64 libsmbclient0 amd64 2:4.19.5+dfsg-3 [86,5 kB] 86,5 ko réceptionnés en 0s (418 ko/s) valette@tri-yann5:/tmp$ dpkg-deb -R libsmbclient0_2%3a4.19.5+dfsg-3_amd64.deb libsmbclient valette@tri-yann5:/tmp$ cd libsmbclient/ valette@tri-yann5:/tmp/libsmbclient$ more DEBIAN/control Package: libsmbclient0 Source: samba Version: 2:4.19.5+dfsg-3 Architecture: amd64 Maintainer: Debian Samba Maintainers Installed-Size: 240 Depends: samba-libs (= 2:4.19.5+dfsg-3), libbsd0 (>= 0.0), libc6 (>= 2.25), libndr3 (>= 2:4.17.2), libtalloc2 (>= 2.4.1~), libtevent0t64 (>= 0.15.0) Breaks: libsmbclient (<< 2:4.19.5+dfsg-3) Replaces: libsmbclient Section: libs Priority: optional Multi-Arch: same Homepage: https://www.samba.org Description: shared library for communication with SMB/CIFS servers This package provides a shared library that enables client applications to talk to Microsoft Windows and Samba servers using the SMB/CIFS protocol. So Although I'm not a debian developer, I read this control file as: You cannot install libsmbclient0 without breaking libsmbclient if the version of libsmbclient is not at least 2:4.19.5+dfsg-3. It will then replace libsmbclient. BUT the package libsmbclient 2:4.19.5+dfsg-3 is never going to be generated nor latter versions unless the names change back to libsmbclient. So the condition will never happen. The Provides directive give a way to provide libsmbclient 2:4.19.5+dfsg-3 And as you state, if the time_t type is already 64 bits why should package depending on libsmbclient need to be regenerated? --eric
Bug#1065349: libsmbclient0: Actually breaks part of t64 transition
Package: libsmbclient0 Version: 2:4.19.5+dfsg-3 Severity: grave Justification: renders package unusable the control file should contain: Provides: libsmbclient (= 2:4.19.5+dfsg-3) Otherwyse as many package depends on libsmbclient it cannot be removed and the replace is not sufficient. I checked how other pachage manage their transitions and it is done this way. Here is my manually modified config file. dpkg -s libsmbclient0 Package: libsmbclient0 Status: install ok installed Priority: optional Section: libs Installed-Size: 240 Maintainer: Debian Samba Maintainers Architecture: amd64 Multi-Arch: same Source: samba Version: 2:4.19.5+dfsg-3 Provides: libsmbclient (= 2:4.19.5+dfsg-3) Depends: samba-libs (= 2:4.19.5+dfsg-3), libbsd0 (>= 0.0), libc6 (>= 2.25), libndr3 (>= 2:4.17.2), libtalloc2 (>= 2.4.1~), libtevent0t64 (>= 0.15.0) Breaks: libsmbclient (<< 2:4.19.5+dfsg-3) Description: shared library for communication with SMB/CIFS servers This package provides a shared library that enables client applications to talk to Microsoft Windows and Samba servers using the SMB/CIFS protocol. Homepage: https://www.samba.org -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsmbclient0 depends on: ii libbsd0 0.12.1-1 ii libc6 2.38-6 ii libtalloc22.4.2-1 ii libtevent0t64 0.16.1-2 ii samba-libs [libndr3] 2:4.19.5+dfsg-3 libsmbclient0 recommends no packages. libsmbclient0 suggests no packages. -- no debconf information
Bug#1061242: libreoffice-impress: impress cannot start. Its display an error loading a dll that is installed
On 21/01/2024 14:49, Rene Engelhard wrote: Exactly that is the point of #1059040. The binary packages have to be renamed. (Then rebuild against libxml2-WHATEVERNEW). Then a rebuild LO will have a proper dependency on libxml2-WHATEVERNEW. I agree that package with different APIs should bump their major .so version, but not obviously change their name. At least, that has not always been like that (more than 20 years...). The libxml2 package as of now must not install unstable at current state. Agreed. Indeed the current package name of libxml2 is a problem and fullfills unstables depends, but see below. It is expected that stuff built with 2.9.x doesn't necessarily work with 2.12. And here libsdlo.so *does* link against libxml: Missing dependency < dependency at least. Yeah. But for that you need a palantir. For an unknown amount of packages in the archive? No. The bug is in libxml2. I disagree on this. Many ddl did not change their name when they have API breakage only bump major so that symbolic links does not get resolved. It managed to load the wrong ddl version because of the NEEDED libxml2.so.2 in /usr/lib/libreoffice/program/libsdlo.so and that depending on the version installed it points to either 2.9 or 2.12 Thanks for your time. -- eric
Bug#1061242: libreoffice-impress: impress cannot start. Its display an error loading a dll that is installed
Package: libreoffice-impress Version: 4:24.2.0~rc2-2 Severity: grave Justification: renders package unusable When I open a odp file, I get the message: loading of component failed /usr/lib/libreoffice/program/libsdlo.so dpkg -S /usr/lib/libreoffice/program/libsdlo.so libreoffice-draw: /usr/lib/libreoffice/program/libsdlo.so valette@tri-yann5:~$ ls -l /usr/lib/libreoffice/program/libsdlo.so -rw-r--r-- 1 root root 7690360 13 janv. 20:26 /usr/lib/libreoffice/program/libsdlo.so valette@tri-yann5:~$ file /usr/lib/libreoffice/program/libsdlo.so /usr/lib/libreoffice/program/libsdlo.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=971f3e457517759a9434b347f3df94ed199e098e, stripped In addition, trying to report the bug I get the following errors: Gathering additional data, this may take a while... Exception occurred: Connector : couldn't connect to pipe "ecc792b3cee7844e153abb7ce96bfdb921fcaff61693c3a5d788741b64e22eb": 10 at ./io/source/connector/connector.cxx:94 Cause: (com.sun.star.connection.NoConnectException) { { Message = "Connector : couldn't connect to pipe \"ecc792b3cee7844e153abb7ce96bfdb921fcaff61693c3a5d788741b64e22eb\": 10 at ./io/source/connector/connector.cxx:94", Context = (com.sun.star.uno.XInterface) @0 } } unopkg failed. Exception occurred: Connector : couldn't connect to pipe "8aafa411c24e82e7cf177bcda3fbb92df3d7dc9ea297d3ab6571624ec": 10 at ./io/source/connector/connector.cxx:94 Cause: (com.sun.star.connection.NoConnectException) { { Message = "Connector : couldn't connect to pipe \"8aafa411c24e82e7cf177bcda3fbb92df3d7dc9ea297d3ab6571624ec\": 10 at ./io/source/connector/connector.cxx:94", Context = (com.sun.star.uno.XInterface) @0 } } unopkg failed. Exception occurred: Connector : couldn't connect to pipe "f9a62ef4d44126b83f661a55e88d133b790764ef14a93a4677126280764885": 10 at ./io/source/connector/connector.cxx:94 Cause: (com.sun.star.connection.NoConnectException) { { Message = "Connector : couldn't connect to pipe \"f9a62ef4d44126b83f661a55e88d133b790764ef14a93a4677126280764885\": 10 at ./io/source/connector/connector.cxx:94", Context = (com.sun.star.uno.XInterface) @0 } } unopkg failed. ^CThe package bug script /usr/share/bug/libreoffice-impress/script exited with an error status (return code = 2). Do you still want to file a report [y|N|q|?]? y -- Package-specific info: ii nvidia-installer-cleanup 20240109+1 amd64cleanup after driver installation with the nvidia-installer pi nvidia-libopencl1:amd64 530.41.03-1 amd64NVIDIA OpenCL ICD Loader library Configuration filePackage Exists Changed /etc/libreoffice/registry/impress.xcd libreoffice-impress Yes No /etc/libreoffice/registry/ogltrans.xcdlibreoffice-impress Yes No All deployed shared extensions: Experimental features enabled: Installed VCLplugs: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++--==--= un libreoffice-gtk3 (no description available) ii libreoffice-kf5 4:24.2.0~rc2-2 amd64office productivity suite -- KDE Frameworks 5 integration ii libreoffice-qt5 4:24.2.0~rc2-2 amd64office productivity suite -- Qt 5 integration ii libreoffice-qt6 4:24.2.0~rc2-2 amd64office productivity suite -- Qt 6 integration Java (javaldx): /usr/lib/jvm/java-21-openjdk-amd64/lib/amd64/client:/usr/lib/jvm/java-21-openjdk-amd64/lib/amd64/server:/usr/lib/jvm/java-21-openjdk-amd64/lib/amd64/native_threads:/usr/lib/jvm/java-21-openjdk-amd64/lib/amd64 Java: http://openoffice.org/2004/java/framework/1.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> file:///usr/lib/jvm/java-21-openjdk-amd64 Configuration filePackage Exists Changed /etc/libreoffice/registry/draw.xcdlibreoffice-drawYes No /etc/libreoffice/registry/graphicfilter.xcd libreoffice-drawYes No All deployed shared extensions: -- System Information: Debian Release: trixie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.11-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-impress depend
Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update
On Mon, 20 Nov 2023 21:17:40 +0100 Michael Biebl wrote: I will add a versioned Breaks isc-dhcp-client (<< 4.4.3-P1-5) to network-manager, assuming the next version fixing this issue will be 4.4.3-P1-5. Btw, the AppArmor policy also references /usr/lib/NetworkManager/nm-dhcp-client.action This binary is long gone. You can just remove any traces of it. Is is allowed to put a versioned break on a non existing version? Result is that I cannot upgrade as I still need dhcp. -- eric
Bug#1054211: systemd: ystemd-networkd-wait-online.service reports a timeout error while network is activated
On 19/10/2023 15:23, Michael Biebl wrote: On 10/19/23 10:47, eric wrote: Package: systemd Version: 254.5-1 Severity: normal Do you have any network interfaces managed by systemd-networkd? If not, why is systemd-networkd-wait-online.service enabled? How do I specify/know that? I havent changed my network config besides regular package update. I've no /etc/network/interface file and my config should be managed by network manager. Currently ethernet cable but wifi sometimes. -- eric
Bug#1031363: Fixed with 0.17.0-3 and thunderbird 1:115.1.1-1
The 0.17 in unstable and the thunderbird version that use the external lib are happily working together. But can be closed. -- eric
Bug#1038595: linux-image-amd64: DVB broken with 6.3.7
Package: linux-image-6.3.0-1-amd64 Version: 6.3.7-1 Severity: normal Tags: patch tvheadend does not work with this kernel. 6.1.27 does. The patch and the probme is also found by other https://bbs.archlinux.org/viewtopic.php?id=286421 -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.15.117 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-6.1.0-9-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20230519-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-9-amd64 recommends: ii apparmor 3.0.8-3 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-9-amd64 suggests: pn debian-kernel-handbook ii extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1 ii grub-efi-amd64 2.06-13 pn linux-doc-6.1
Bug#1038593: linux-image-amd64: DVB broken with 6.3.7
Package: linux-image-amd64 Version: 6.3.7-1 Severity: normal Tags: patch tvheadend does not work with this kernel. 6.1.27 does. The patch and the probme is also found by other https://bbs.archlinux.org/viewtopic.php?id=286421 -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.15.117 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-headers-rt-amd64 depends on: pn linux-headers-6.1.0-9-rt-amd64 pn linux-headers-6.3.0-1-rt-amd64 pn linux-headers-6.4.0-0-rt-amd64 linux-headers-rt-amd64 recommends no packages. linux-headers-rt-amd64 suggests no packages.
Bug#1034796: kio-gdrive: Does not work. Network account create does not propose gogle drive
On 30/04/2023 00:48, Nicholas D Steeves wrote: Control: severity -1 important Control: tag -1 moreinfo Justification: Package is not unusable for everyone. See the following for further info: https://www.debian.org/Bugs/Developer#severities It is hard to know if it is broken for you or for many others. As I saw exactly the same reports on other distrib I assume this is a general problem. Using dolphin for network, you can select gdrive but it does not propose to add a google account. That's odd, mine shows a "New account" button. I tested on another computer with exactly the same setup unstable + experimental, nearly same package set (well execpt I use a generic debian kernel on this one). And there it kinda works: 1)I cannot access an old account, 2) but I can create a new one 3) and relaucching kdeinit5 I can even access the content, So this is probably incompatible left over in the .config or similar. I will try to search for gdrive or kio there. Kernel: Linux 5.15.108 (SMP w/8 CPU threads; PREEMPT) Neat, I track this branch too :) It is my own kernel that I use for years on my machin just updating it to official long term stable... Are you able to reproduce this bug with a pure testing/bookworm or sid/unstable system? If so, please provide steps to reproduce, and remove the moreinfo tag from this bug at that time. Well the package are now in testing I guess due to the hard freeze. Thnaks for replying. More later when I can put my hands back on the problematic config. --eric
Bug#1034796: kio-gdrive: Does not work. Network account create does not propose gogle drive
Package: kio-gdrive Version: 22.12.3-1 Severity: grave Justification: renders package unusable Using dolphin for network, you can select gdrive but it does not propose to add a google account. Using systemsettings, I have the same problem and using the command rpoposed in the packahe readme.md gives: kioclient5 exec gdrive:/ kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/gdrive" not found kf.kio.core: KIO::get didn't emit a mimetype! Please fix the KIO worker for URL QUrl("gdrive:/") -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.15.108 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kio-gdrive depends on: ii kaccounts-integration 4:22.12.3-1 ii kio5.104.0-1 ii libaccounts-qt5-1 1.16-2 ii libc6 2.36-9 ii libkaccounts2 4:22.12.3-1 ii libkf5coreaddons5 5.104.0-1 ii libkf5i18n55.104.0-1 ii libkf5kiocore5 5.104.0-1 ii libkf5kiogui5 5.104.0-1 ii libkf5kiowidgets5 5.104.0-1 ii libkf5notifications5 5.104.0-1 ii libkf5widgetsaddons5 5.104.0-1 ii libkpimgapicore5abi1 [libkpimgapicore5-22.12] 22.12.3-1 ii libkpimgapidrive5 [libkpimgapidrive5-22.12]22.12.3-1 ii libqt5core5a 5.15.8+dfsg-7 ii libqt5gui5 5.15.8+dfsg-7 ii libqt5widgets5 5.15.8+dfsg-7 ii libstdc++6 13-20230419-1 kio-gdrive recommends no packages. kio-gdrive suggests no packages. -- no debconf information
Bug#1031363: librnp0 from experimental breaks thunderbird openpgp feature
Package: librnp0 Version: 0.17.0~git20220428-1 Severity: serious Justification: makes unrelated software on the system Thre is no dependency and the packages installs but thunderbird do not manage to dlopen the dddl and it breaks opengpg. Downgrading to unstable version fixes the problem. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.15.93 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages librnp0 depends on: ii libbotan-2-19 2.19.3+dfsg-1 ii libbz2-1.0 1.0.8-5+b1 ii libc6 2.36-8 ii libgcc-s1 12.2.0-14 ii libjson-c5 0.16-2 ii libstdc++6 12.2.0-14 ii zlib1g 1:1.2.13.dfsg-1 librnp0 recommends no packages. librnp0 suggests no packages. -- no debconf information
Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber
On Sun, 12 Feb 2023 13:23:40 +0100 Eric Valette wrote: On 12/02/2023 12:15, Simon McVittie wrote: > Control: severity -1 serious > > On Sun, 12 Feb 2023 at 11:16:18 +0100, Eric Valette wrote: >> Severity: critical >> Justification: breaks unrelated software > > wireplumber uses GLib, so this is not unrelated software. If you use this definition, you cannot create critical bugs in any shared libraries! You, for sure, never can use it for libc... -- eric
Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber
On 12/02/2023 12:14, Jeremy Bícha wrote: Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2769 On Sun, Feb 12, 2023 at 5:18 AM Eric Valette wrote: Package: libglib2.0-0 Version: 2.75.2-1 Severity: critical Justification: breaks unrelated software I've tried to install this version on two different machines and each time it did break wireplumber/pulseoaudio. Yes, this will be fixed in the next release of glib to Experimental. By the way, sometimes packages are in Experimental instead of Unstable because they are known to be broken, in one way or another. Sure but if noone test them and reports the problem is found in unstable and impacts more people. -- eric
Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber
On 12/02/2023 12:15, Simon McVittie wrote: Control: severity -1 serious On Sun, 12 Feb 2023 at 11:16:18 +0100, Eric Valette wrote: Severity: critical Justification: breaks unrelated software wireplumber uses GLib, so this is not unrelated software. If you use this definition, you cannot create critical bugs in any shared libraries! --eric
Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber
Package: libglib2.0-0 Version: 2.75.2-1 Severity: critical Justification: breaks unrelated software I've tried to install this version on two different machines and each time it did break wireplumber/pulseoaudio. extract of journalctl: févr. 12 11:13:06 tri-yann4 wireplumber[2267]: Failed to set scheduler settings: Opération non permise févr. 12 11:13:06 tri-yann4 kernel: traps: wireplumber[2299] trap int3 ip:7fe5d515b4e7 sp:7fe5d2e22b40 error:0 in libglib-2.0.so.0.7502.0[7fe5d511c000+8e000] févr. 12 11:13:06 tri-yann4 systemd-coredump[2304]: Process 2267 (wireplumber) of user 1000 dumped core. #0 0x7fe5d52c4633 wp_object_interest_validate (libwireplumber-0.4.so.0 + 0x2c633) -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.15.93 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libglib2.0-0 depends on: ii libc6 2.36-8 ii libffi8 3.4.4-1 ii libmount1 2.38.1-4 ii libpcre2-8-0 10.42-1 ii libselinux1 3.4-1+b5 ii zlib1g1:1.2.13.dfsg-1 Versions of packages libglib2.0-0 recommends: ii libglib2.0-data 2.75.2-1 ii shared-mime-info 2.2-1 ii xdg-user-dirs 0.18-1 Versions of packages libglib2.0-0 suggests: pn low-memory-monitor -- no debconf information
Bug#1025366: Note that the bug is also present in 7.0.6
On 25/01/2023 10:36, Gianfranco Costamagna wrote: On Sun, 4 Dec 2022 11:19:52 +0100 Eric Valette wrote: Already fixed there same ways but did not report the bug hoping it will be soon fixed. -- eric Hello, please try 7.0.6 thanks Same error, same fix. As long as the file does not chnage... -- eric
Bug#1028476: kalendar does not display many outlook/teams calendar event (ews backend)
Package: kalendar Version: 22.12.0-3 Severity: important I have corporate kalendar that I can correctly see using outlook web app or teams. Kaldendar congiured to access the kalendar wia akonadi_ews does see some events plus moste are missing. I do not find any pattern to know why some are correctly diplayed and others are not (recurring events sometimes work, I cannot even see simple event I create whith only mee as participant (reminder). This is currently unusable and I could not corrrently manage my appointments without microsoft proprietary clients. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.10.162 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kalendar depends on: ii akonadi-server 4:22.12.0-2 ii kdepim-runtime 4:22.12.0-2 ii kio5.101.0-2 ii libc6 2.36-8 ii libgcc-s1 12.2.0-14 ii libgpgme11 1.18.0-3 ii libkf5akonadicalendar5abi1 [libkf5akonadicalendar5-22.12] 4:22.12.0-2 ii libkf5akonadicontact5 [libkf5akonadicontact5-22.12]4:22.12.0-2 ii libkf5akonadicore5abi2 [libkf5akonadicore5-22.12] 4:22.12.0-2 ii libkf5akonadimime5 [libkf5akonadimime5-22.12] 4:22.12.0-2 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-22.12]4:22.12.0-2 ii libkf5calendarcore5abi25:5.101.0-1 ii libkf5calendarsupport5abi1 [libkf5calendarsupport5-22.12] 4:22.12.0-2 ii libkf5codecs5 5.101.0-1 ii libkf5configcore5 5.101.0-1 ii libkf5configgui5 5.101.0-1 ii libkf5configwidgets5 5.101.0-1 ii libkf5contacts55:5.101.0-1 ii libkf5coreaddons5 5.101.0-1 ii libkf5dbusaddons5 5.101.0-1 ii libkf5eventviews5abi1 [libkf5eventviews5-22.12]4:22.12.0-2 ii libkf5i18n55.101.0-1+b1 ii libkf5itemmodels5 5.101.0-2 ii libkf5kiocore5 5.101.0-2 ii libkf5mailcommon5abi2 [libkf5mailcommon5-22.12]4:22.12.0-2 ii libkf5mime5abi1 [libkf5mime5-22.12]22.12.0-2 ii libkf5widgetsaddons5 5.101.0-1 ii libkf5windowsystem55.101.0-2 ii libkf5xmlgui5 5.101.0-1+b1 ii libqt5core5a 5.15.7+dfsg-2 ii libqt5dbus55.15.7+dfsg-2 ii libqt5gui5 5.15.7+dfsg-2 ii libqt5qml5 5.15.7+dfsg-2 ii libqt5quick5 5.15.7+dfsg-2 ii libqt5quickcontrols2-5 5.15.7+dfsg-2 ii libqt5widgets5 5.15.7+dfsg-2 ii libstdc++6 12.2.0-14 ii qml-module-org-kde-kirigami2 5.101.0-1+b1 ii qml-module-qtlocation 5.15.7+dfsg-2 ii qml-module-qtpositioning 5.15.7+dfsg-2 Versions of packages kalendar recommends: ii kalendarac 4:22.12.0-2 kalendar suggests no packages. -- no debconf information
Bug#1025901: libunistring2: Breaks system due to missing libunistring.so.2
Package: libunistring2 Version: 1.1-1~experimental1 Severity: critical Justification: breaks unrelated software This breaks NetworkManaget, apt ... nmcli nmcli: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory apt-cache policy libunistring2 libunistring2: Installed: 1.1-1~experimental1 Candidate: 1.1-1~experimental1 Version table: *** 1.1-1~experimental1 100 1 http://ftp.fr.debian.org/debian experimental/main amd64 Packages 100 /var/lib/dpkg/status 1.0-2 500 500 http://ftp.fr.debian.org/debian testing/main amd64 Packages 500 http://ftp.fr.debian.org/debian unstable/main amd64 Packages 0.9.10-4 500 500 http://ftp.fr.debian.org/debian stable/main amd64 Packages root@tri-yann4:~# apt install libunistring2=1.0-2 Reading package lists... Done Building dependency tree... Done Reading state information... Done /usr/lib/apt/methods/http: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory E: Method http has died unexpectedly! E: Sub-process http returned an error code (127) E: Method /usr/lib/apt/methods/http did not start correctly -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.10.158 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libunistring2 depends on: ii libunistring5 1.1-1~experimental1 libunistring2 recommends no packages. libunistring2 suggests no packages. -- no debconf information
Bug#1024395: Fixed on my laptop with 1+2.06+7
After upgrading all grub*2.06-7 at once,I confirm it works on both laptop and Desktop. Now, the dependency still seems strange to me expeciallya s the signed version come usually later than the rest. -- eric
Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
On 05/12/2022 18:33, Steve McIntyre wrote: On Mon, Dec 05, 2022 at 06:19:53PM +0100, Eric Valette wrote: On 05/12/2022 18:07, Steve McIntyre wrote: You're using the Secure Boot path (shim -> grub-efi-amd64-signed), so the version of grub that matters for you is the signed version: 1+2.06+5. That is (so far) still based on grub2 source version 2.06-5. It takes a short while for the builds to propagate through the signing machinery in Debian. Please be patient, the fix is on the way to you. If you can check again when 1+2.06+6 is available, that will be more helpful. Fair enough but for me this should be handled as a dependency so that you cannot upgrade only part of grub components. A meta package that makes sure all the dependencies are ok before starting the upgrade. There are no dependency issues to worry about here, I'm afraid you simply misunderstood the grub packaging setup. That's reasonable - it's not obvious! Just don't expect the bug to be fixed until the changes have propagated... I beg to disagree on this one. On my laptop, I updated grub-efi-amd64-signed to the 1+2.06+6 version but, as installation does not trigger grub reinstall, my laptop is still broken. If you do not want to put dependency on component, each component that contains things that should be moved to EFI directory should trigger a grub update. And at first you should not update the EFI directory until all needed binaries are updated. ( ls /var/lib/dpkg/info/grub-efi-amd64-signed.* /var/lib/dpkg/info/grub-efi-amd64-signed.list /var/lib/dpkg/info/grub-efi-amd64-signed.md5sums ) The good point, is that, on my Desktop that was broken due to previous install, and on which I downgraded and pinned, because I installed a coherent set all at once, it worked. But dependencies should enforce you always have a coherent set when ruing grub update. So I have to boot windows, suspend bit locker, trigger the reinstall of grub, verify it works by rebooting and then again reenable bitlocker. Groumph. -- eric
Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
On 05/12/2022 18:07, Steve McIntyre wrote: You're using the Secure Boot path (shim -> grub-efi-amd64-signed), so the version of grub that matters for you is the signed version: 1+2.06+5. That is (so far) still based on grub2 source version 2.06-5. It takes a short while for the builds to propagate through the signing machinery in Debian. Please be patient, the fix is on the way to you. If you can check again when 1+2.06+6 is available, that will be more helpful. Fair enough but for me this should be handled as a dependency so that you cannot upgrade only part of grub components. A meta package that makes sure all the dependencies are ok before starting the upgrade. And as explained I must play with windows bitlocker to suspend it before being able to install so I would prefer doing it all at once. -- eric
Bug#1024395: Side note : the packages are marked on hold in previous mail because of dual boot with windows bitlocker activated.
If I upgrade EFI components without suspending bitlocker on Windows I need to enter the bitlocker key. Very annoying. So I cannot update normally shim and grub EFI components. There are on hold until I know I have disabled bitlocker and can manually upgrade. As soon as done, I put them again on hold. --eric
Bug#1024395: not fixed for me and worse it did break a PC that was unaffected by previous version
I had the previous version 2.06-5 on a laptop, and it was not affected by the bug, Only my very old Desktop was. As the bug was closed, I did install 2.06-6 on my laptop (or at least the composant actually upgraded) and now it also fails on my laptop with same error than on my desktop. I now have apparently several grub version flavors and several shim version flavor: 15.4 for shim-signed:amd64 and shim-signed-common and 15.6 for shim-helpers-amd64-signed and shim-unsigned And for grub, I have 2.06-6 except for the important part : grub-efi-amd64-signed that is still at 2.06-5. dpkg -l shim* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=--- un shim(no description available) hi shim-helpers-amd64-signed 1+15.6+1 amd64boot loader to chain-load signed boot loaders (signed by Debian) hi shim-signed:amd64 1.38+15.4-7 amd64Secure Boot chain-loading bootloader (Microsoft-signed binary) hi shim-signed-common1.38+15.4-7 all Secure Boot chain-loading bootloader (common helper scripts) hi shim-unsigned 15.6-1 amd64boot loader to chain-load signed boot loaders under Secure Boot root@:~# dpkg -l grub* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=---= un grub(no description available) un grub-cloud-amd64(no description available) hi grub-common 2.06-6 amd64GRand Unified Bootloader (common files) un grub-coreboot (no description available) un grub-doc(no description available) hi grub-efi 2.06-6 amd64GRand Unified Bootloader, version 2 (dummy package) hi grub-efi-amd642.06-6 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version) hi grub-efi-amd64-bin2.06-6 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 modules) hi grub-efi-amd64-signed 1+2.06+5 amd64GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) un grub-efi-arm(no description available) un grub-efi-arm64 (no description available) un grub-efi-ia32 (no description available) un grub-efi-ia64 (no description available) un grub-emu(no description available) un grub-ieee1275 (no description available) un grub-legacy (no description available) un grub-legacy-doc (no description available) un grub-linuxbios (no description available) un grub-pc (no description available) hi grub-pc-bin 2.06-6 amd64GRand Unified Bootloader, version 2 (PC/BIOS modules) un grub-uboot (no description available) un grub-xen(no description available) un grub-yeeloong (no description available) un grub2 (no description available) hi grub2-common 2.06-6 amd64GRand Unified Bootloader (common files for version 2) root@:~# -- eric
Bug#1025366: Note that the bug is also present in 7.0.2
Already fixed there same ways but did not report the bug hoping it will be soon fixed. -- eric
Bug#1025366: virtualbox-dkms does not compile with gcc-12
Package: virtualbox-dkms Version: 7.0.4-dfsg-4 Severity: grave Tags: upstream Justification: renders package unusable dkms autoinstall Sign command: /usr/lib/linux-kbuild-5.10/scripts/sign-file Binary /usr/lib/linux-kbuild-5.10/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... make -j8 KERNELRELEASE=5.10.156 -C /lib/modules/5.10.156/build M=/var/lib/dkms/virtualbox/7.0.4/build(bad exit status: 2) Error! Bad return status for module build on kernel: 5.10.156 (x86_64) Consult /var/lib/dkms/virtualbox/7.0.4/build/make.log for more information. root@tri-yann4:~# more /var/lib/dkms/virtualbox/7.0.4/build/make.log DKMS make.log for virtualbox-7.0.4 for kernel 5.10.156 (x86_64) Sat Dec 3 10:39:35 AM CET 2022 make: Entering directory '/usr/src/linux-i7-asus' CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/linux/SUPDrv-linux.o CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrv.o CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvGip.o CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvSem.o CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvTracer.o CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPLibAll.o CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/common/string/strformatrt.o CC [M] /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/combined-agnostic1.o In file included from /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/iprt/assert.h:45, from /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/VBox/sup.h:44, from /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrvInternal.h:49, from /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/SUPDrv.c:43: /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/VBox/vmm/hm_vmx.h:532:29: error: â\x80\x98VMX_BF_EPT_PT_0_MASKâ\x80\x99 undeclared here (not in a function); did you mean â\x80\x98VMX_BF_EPT_PT_RE AD_MASKâ\x80\x99? 532 | RT_BF_ASSERT_COMPILE_CHECKS(VMX_BF_EPT_PT_, UINT64_C(0), UINT64_MAX, | ^~ /var/lib/dkms/virtualbox/7.0.4/build/vboxdrv/include/iprt/assertcompile.h:107:101: note: in definition of macro â\x80\x98AssertCompileNSâ\x80\x99 107 | # define AssertCompileNS(expr) extern int RTASSERTVAR[1 RT_BF_ASSERT_COMPILE_CHECKS macros does not what is expected. Using alternate definition makes it work here is a simple patch: --- cdefs.h.orig2022-12-03 10:46:44.540262521 +0100 +++ cdefs.h 2022-12-03 10:57:10.289734851 +0100 @@ -2659,19 +2659,7 @@ * * This requires variadic macros because its too much to type otherwise. */ -#if defined(RT_COMPILER_SUPPORTS_VA_ARGS) || defined(DOXYGEN_RUNNING) -# define RT_BF_ASSERT_COMPILE_CHECKS(a_Prefix, a_uZero, a_uCovered, a_Fields) \ -AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_OR_MASK, a_uZero, a_Prefix, RT_UNPACK_ARGS a_Fields ) == a_uCovered); \ -AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_XOR_MASK, a_uCovered, a_Prefix, RT_UNPACK_ARGS a_Fields ) == 0); \ -AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_1ST_MASK_BIT, true, a_Prefix, RT_UNPACK_ARGS a_Fields ) == true); \ -AssertCompile(RT_BF_CHECK_DO_N(RT_BF_CHECK_DO_MASK_START, true, a_Prefix, RT_UNPACK_ARGS a_Fields ) == true) -/** Bit field compile time check helper - * @internal */ -# define RT_BF_CHECK_DO_N(a_DoThis, a_uLeft, a_RightPrefix, ...) \ -RT_UNPACK_CALL(RT_CONCAT(RT_BF_CHECK_DO_, RT_EXPAND(RT_COUNT_VA_ARGS(__VA_ARGS__))), (a_DoThis, a_uLeft, a_RightPrefix, __VA_ARGS__)) -#else # define RT_BF_ASSERT_COMPILE_CHECKS(a_Prefix, a_uZero, a_uCovered, a_Fields) AssertCompile(true) -#endif /** @def RT_ALIGN -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.10.156 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages virtualbox-dkms depends on: ii dkms 3.0.8-3 Versions of packages virtualbox-dkms recommends: iu virtualbox 7.0.4-dfsg-4 virtualbox-dkms suggests no packages. -- no debconf information
Bug#1024395: CONFIG_INTEGRITY_PLATFORM_KEYRING was missing for mokutil --list-enrolled to work
CONFIG_INTEGRITY_PLATFORM_KEYRING=y But the bug is still there -- eric
Bug#1024395: The mokutil --list-enrolled is due to kernel config or version
I tested with 6.0.0-4-amd kernel version, and there mokutil --list-enrolled works. So either it is a missing config item in my own generated kernel (what is needed beside all *EFI* config items, something in keyring or crypto algo?) or a kernel incompatibilty (5.10.155). But that has nothing to do with the grub bug it is just for the sake of completeness -- eric
Bug#1024647: trac: The versiuon packaged by debian contain a bug fixed upstream that prevent it to work with python3
Package: trac Version: 1.5.3+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable Afterupgrading and oldoldstable distrib to stable 11.5, becaue of the move to python3 I had to update trac to the sid version as there is not stable version yet. It did not work at all inside apache2/cgi (old install)because of a bug already fixed upstream (reload not defined) See : https://trac.edgewall.org/changeset/17571 for the fix. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.10.155 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages trac depends on: pn libjs-excanvas ii libjs-jquery 3.6.1+dfsg+~3.5.14-1 pn libjs-jquery-timepicker ii libjs-jquery-ui 1.13.2+dfsg-1 ii python3 3.10.6-3 ii python3-jinja2 3.0.3-2 ii python3-pkg-resources65.5.0-1 ii python3-setuptools 65.5.0-1 Versions of packages trac recommends: pn apache2 | httpd ii python3-babel 2.10.3-1 ii python3-docutils0.19+dfsg-2 ii python3-pygments2.13.0+dfsg-1 pn python3-subversion ii python3-tz 2022.6-1 Versions of packages trac suggests: pn libapache2-mod-wsgi pn python3-psycopg2 pn python3-textile pn trac-accountmanager pn trac-authopenid pn trac-bitten pn trac-bzr pn trac-customfieldadmin pn trac-email2trac pn trac-graphviz pn trac-ja-resource pn trac-mastertickets pn trac-mercurial pn trac-spamfilter pn trac-wikiprint pn trac-wikirename pn trac-wysiwyg pn trac-xmlrpc
Bug#1024395: Downgrading fixes the problem.
downgrading to 1+2.06+3~deb11x grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common shim-helpers-amd64-signed fix the error. However the mokutils --list-enrolled command is still void. -- eric
Bug#1024395: inconsistencies between shim-signed versions (= 15.4-7) and shim-helpers-amd64-signed shim (= 15.6-1)
dpkg -s shim-signed Package: shim-signed Status: install ok installed Priority: optional Section: utils Installed-Size: 937 Maintainer: Debian EFI Team Architecture: amd64 Multi-Arch: same Source: shim-signed (1.38) Version: 1.38+15.4-7 Depends: shim-signed-common (>= 1.38+15.4-7), grub-efi-amd64-bin, shim-helpers-amd64-signed (>= 1+15.4+2), grub2-common (>= 2.02+dfsg1-16) Recommends: secureboot-db Description: Secure Boot chain-loading bootloader (Microsoft-signed binary) This package provides a minimalist boot loader which allows verifying signatures of other UEFI binaries against either the Secure Boot DB/DBX or against a built-in signature database. Its purpose is to allow a small, infrequently-changing binary to be signed by the UEFI CA, while allowing an OS distributor to revision their main bootloader independently of the CA. . This package contains the version of the bootloader binary signed by the Microsoft UEFI CA. Built-Using: shim (= 15.4-7) dpkg -s shim-helpers-amd64-signed Package: shim-helpers-amd64-signed Status: install ok installed Priority: optional Section: admin Installed-Size: 934 Maintainer: Debian EFI team Architecture: amd64 Version: 1+15.6+1 Replaces: shim (<< 15+1533136590.3beb971-3~), shim-signed (<< 1.29) Depends: shim-unsigned (>= 15.6-1) Breaks: shim-signed (<< 1.29) Conflicts: shim (<< 15+1533136590.3beb971-3~) Description: boot loader to chain-load signed boot loaders (signed by Debian) This package provides a minimalist boot loader which allows verifying signatures of other UEFI binaries against either the Secure Boot DB/DBX or against a built-in signature database. Its purpose is to allow a small, infrequently-changing binary to be signed by the UEFI CA, while allowing an OS distributor to revision their main bootloader independently of the CA. . This package contains the MOK manager and fall-back manager signed by the Debian UEFI CA to be used by shim-signed. Built-Using: shim (= 15.6-1) -- eric
Bug#1024395: If I try to enroll the same key again : no chnage.
So apparently the keys is still there but mokutil does not see it. Strange! -- eric
Bug#1024395: grub-efi-amd64-signed: after upgrade to 1+2.06+5 I get errors when booting (although I manage to boot)
Package: grub-efi-amd64-bin Version: 1+2.06+5 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team After upgrade to 2.06-5, I get an error message "prohibited by secure boot policy" and it boot with a strange look with \xe7caracaters instead of lines. I build my own kernel and enrolled my owns keys, sign the linux kernel binarry and the mdoules with the keys. Everythong was working fine with 2.06-3. I also noticed that my enrolled keys is no more listed via "mokutil --list-enrolled". Although no key were cleared. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.10.155 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages grub-efi-amd64-signed depends on: ii grub-common 2.06-5 Versions of packages grub-efi-amd64-signed recommends: ii shim-signed 1.38+15.4-7 grub-efi-amd64-signed suggests no packages. Versions of packages grub-efi-amd64-bin depends on: ii grub-common 2.06-5 Versions of packages grub-efi-amd64-bin recommends: ii efibootmgr 17-1 -- no debconf information
Bug#1011121: Confirmed on debian unstable with commercial enterprise access point
It tried all the tricks related to openssl.cnt (SECPOLICY 0, allowunsecure retry, ...) and still get this message. WPA2 enterprisese and 801.x, certificate on a USB dongle. Works as long as I keep everything build with ssl1.1. --eric
Bug#1014675: Apparently not fixed on the 102.1 (aka ESR branch).
See: https://bugzilla.mozilla.org/show_bug.cgi?id=1745033#c59
Bug#1014911: Not fixed with 102.1
Still missing end to end security in all accounts. --eric
Bug#1013447: gupnp-tools: gupnp-av-cp fails to detect upnp av serveur that kodi or vlc detects correctly
On 25/07/2022 17:17, Andreas Henriksson wrote: Control: severity -1 normal Control: tags -1 moreinfo VLC and Kodi do detect them. As kodi and VLC detect them on the same network at the same time and use also upnp-av serveur types (rendered, file serveur). Anyway, the bug has vanished and way due to the upnp stack has other using other upnp stack did work. --eric
Bug#1014675: Announced fixed upstream in 102.0.3
Apparently fixed upstream. May we have a hint on 102.0.3 arrival. I know it is vacation period but... Regards, --eric
Bug#1014745: Bug seems fixed in 102.0.3 (SMIME was activated for me)
As I had SMIME configured on that specific account, I assume from changelog it could be fixed. --eric
Bug#1014675: as a workaround you can set mailnews.nntp.jsmodule set to false via config editor...
Read that in a bug upstream. Tried it and it worked for me. -- eric
Bug#1014745: thunderbird: Reply all remove Cc participants
On 14/07/2022 12:04, Carsten Schoenert wrote: Hello Eric, Am 14.07.22 um 11:48 schrieb eric: I had the same problem on a specific exchnage account. Reply all did not copy the content and did remove all the CC. you could try out TB 1:103.0~b5-1 from experimental which should have included the fix which issue here is about. Keep in mind that the configuration will get bumped to the new main version and isn't backward compatible, so please make a backup of your config before starting the installed version from experimental. That's exactly why I will not do this. I want to be on the next esr branch and test more deeply as I will have to use it on my professionnal account as well. If it is fixed in 103, I bet it will be backported (ESR after all). I cannot afford to break my main setup even more. It did happen everytime on .1, did not manage to reproduce it with the broken mail on .2. Thanks for the support anyway. --eric
Bug#1014071: digikam can no more be installed on unstable (needs rebuild with new kdepim packages)
Package: digikam Version: 4:7.6.0-1 Severity: normal apt install digikam Reading package lists... Done Building dependency tree... Done 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: digikam-private-libs : Depends: libkf5akonadicontact5-21.12 E: Unable to correct problems, you have held broken packages. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.125 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages digikam depends on: ii digikam-data 4:7.6.0-1 pn digikam-private-libs ii libc6 2.34-0experimental4 ii libgcc-s1 12.1.0-4 ii libkf5configcore5 5.94.0-3 ii libkf5coreaddons5 5.94.0-1 ii libkf5i18n5 5.94.0-1+b1 ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.3+b2 ii libqt5core5a 5.15.4+dfsg-3 ii libqt5gui55.15.4+dfsg-3 ii libqt5sql55.15.4+dfsg-3 ii libqt5sql5-mysql 5.15.4+dfsg-3 ii libqt5sql5-sqlite 5.15.4+dfsg-3 ii libqt5widgets55.15.4+dfsg-3 ii libstdc++612.1.0-4 ii perl 5.34.0-4 Versions of packages digikam recommends: ii ffmpegthumbs 4:22.04.2-1 ii firefox-esr [www-browser]91.11.0esr-1 ii google-chrome-stable [www-browser] 103.0.5060.53-1 ii konqueror [www-browser] 4:21.12.3-1 ii links2 [www-browser] 2.27-1 ii lynx [www-browser] 2.9.0dev.10-1 ii microsoft-edge-stable [www-browser] 103.0.1264.37-1 ii w3m [www-browser]0.5.3+git20220429-1+b1 Versions of packages digikam suggests: ii breeze-icon-theme 4:5.94.0-1 pn digikam-doc ii systemsettings 4:5.25.1-1
Bug#1013447: gupnp-tools: gupnp-av-cp fails to detect upnp av serveur that kodi or vlc detects correctly
Package: gupnp-tools Version: 0.10.3-1 Severity: grave Justification: renders package unusable starting gupnp-av-cp does not detect any DLNA (minidlnad, smartv TV, ...) content server on local network. VLC and Kodi do detect them. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.121 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages gupnp-tools depends on: ii libc6 2.34-0experimental4 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libglib2.0-0 2.72.2-2 ii libgssdp-1.2-01.4.0.1-2 ii libgtk-3-03.24.34-1 ii libgtksourceview-4-0 4.8.3-1 ii libgupnp-1.2-11.4.3-1 ii libgupnp-av-1.0-3 0.14.1-1 ii libsoup2.4-1 2.74.2-3 ii libxml2 2.9.14+dfsg-1 gupnp-tools recommends no packages. gupnp-tools suggests no packages. -- no debconf information
Bug#1011183: nvidia-driver: Please package 470.129.06 that just appeared today
Package: nvidia-driver Version: 470.103.01-4 Severity: wishlist See : https://www.nvidia.com/download/driverResults.aspx/188877/en-us -- no debconf information
Bug#1009954: gitlab: Cannot install experimental or unstable version due to ruby-omniauth dependency
On 21/04/2022 14:12, Pirate Praveen wrote: 2022, ഏപ്രിൽ 21 5:27:25 PM IST, "Éric Valette" ൽ എഴുതി The breakage is there for more than 8 months. I tried to install regularly. Even if I want to, I'm not able to support gitlab in unstable or experimental. That is the reason why I had to create fasttrack.debian.net Gitlab changes too fast for unstable or experimental. I would say the contrary : experimental version are always above what gitlab expects. experiùmental is way faster than gitlab. Putting gitlab related packages in experimental or unstable that you know cannot install is just frustrating. People have someting cretaed private packages version. In this specific case multiple upstream gems needs to updated to work with omniauth 2.0. There are upstream bugs filed already. I can't step in as upstream maintainers of all those gems. More help is always welcome. I does not work either if you bstarted from a testing ISO. Yes, only stable is currently supported. More volunteers to support testing, unstable or experimental welcome. Ben then why do yopu publsih pacakages that have no chnace to install for unstable and experimental. Even outside gitlab, only stable is officially supported, unstable remains broken for many days during transitions. See wiki.debian.org/gitlab Been ther done that. No way to make it work. FIX your package dependency. Its broken for as long as 1.9.1-1 has been in unstable meaning April 2020 see https://tracker.debian.org/pkg/ruby-omniauth I meant follow the recommended option, that is bullseye-fasttrack. Evne with buleyes fastrack, once you installed a testing iso and updated you are scewed. Could you please follow the rules and publish in experimental things that works with a debian unstable system. I'm not able to do this alone, even if I want to, this is too much work for a single maintainer. At this point only bullseye-fasttrack I can reasonably support. Then avoid publishing package for other debian version. -- eric
Bug#1009954: gitlab: Cannot install experimental or unstable version due to ruby-omniauth dependency
Package: gitlab Version: 14.8.5+ds1-3 Severity: important Dear Maintainer, So there is no way to install using experimental as the version of ruby-omniauth is no more even in unstable. apt-get -f install Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libmbedcrypto3 libmbedtls12 libmbedx509-0 linux-image-5.16.0-6-amd64 node-array-union node-array-uniq ruby-scientist ruby-securecompare ruby-sshkey Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up gitlab (14.8.5+ds1-3) ... Successfully installed graphiql-rails-1.8.0 Parsing documentation for graphiql-rails-1.8.0 Done installing documentation for graphiql-rails after 0 seconds 1 gem installed fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git Could not find gem 'omniauth (~> 1.8)' in cached gems or installed locally. The source contains the following gems matching 'omniauth': * omniauth-2.0.4 dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: gitlab E: Sub-process /usr/bin/dpkg returned an error code (1) apt-cache policy ruby-omniauth ruby-omniauth: Installed: 2.0.4-1~exp1 Candidate: 2.0.4-1~exp1 Version table: *** 2.0.4-1~exp1 100 1 http://ftp.de.debian.org/debian experimental/main amd64 Packages 100 /var/lib/dpkg/status 1.9.1-1 500 500 http://ftp.de.debian.org/debian unstable/main amd64 Packages 1.8.1-1 500 500 http://ftp.de.debian.org/debian buster/main amd64 Packages So there is no way to install using experimental. -- System Information: Debian Release: bookworm/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'oldstable'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-trunk-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor 2.0.16-2 ii bc 1.07.1-3+b1 ii bundler 2.3.5-2 ii bzip2 1.0.8-5 ii dbconfig-pgsql 2.0.21 ii debconf [debconf-2.0] 1.5.79 ii exim4-daemon-light [mail-transport-age 4.95-5 ii fonts-font-awesome [node-font-awesome] 5.0.10+really4.7.0~dfsg-4.1 ii gitlab-common 14.8.5+dfsg-1 ii gitlab-workhorse14.8.5+ds1-3 ii katex [node-katex] 0.13.11+~cs6.0.0-3 ii libjs-bootstrap4 [node-bootstrap] 4.6.1+dfsg1-1 ii libjs-codemirror [node-codemirror] 5.65.0+~cs5.83.9-1 ii libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3 ii libjs-popper.js [node-popper.js]1.16.1+ds-5 ii libruby2.7 [ruby-webrick] 2.7.5-1 ii libruby3.0 [ruby-rexml] 3.0.3-1 ii lsb-base11.1.0 ii nginx 1.18.0-9 ii nginx-core [nginx] 1.18.0-9 ii node-autosize 4.0.4~dfsg1+~4.0.0-1 ii node-axios 0.26.1+dfsg-1 ii node-babel-loader 8.2.4-1 ii node-babel-plugin-lodash3.3.4+~cs2.0.1-5 ii node-babel7 7.17.9+~cs214.260.191-1 ii node-brace-expansion2.0.1-1 ii node-cache-loader 4.1.0+~cs2.0.0-2 ii node-clipboard 2.0.8+ds+~cs9.6.11-1 ii node-compression-webpack-plugin 6.1.1-1 ii node-copy-webpack-plugin5.1.2+~cs9.0.2-4 ii node-core-js3.8.2-3 ii node-cron-validator 1.3.1-2 ii node-css-loader 5.2.7+~cs14.0.9-1 ii node-d3 5.16.0-5 ii node-d3-scale 2.2.2-4 ii node-d3-selection 1.4.0-7 ii node-dateformat 3.0.0-2 ii node-exports-loader 1.1.1-3 ii node-file-loader6.2.0-3 ii node-fuzzaldrin-plus0.6.0+dfsg+~0.6.2-1 ii node-glob 7.2.1+~cs7.6.15-2 ii node-imports-loader 0.8.0-5 ii node
Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces
On 16/02/2022 22:36, Eric Valette wrote: On 16/02/2022 21:01, Eric Valette wrote: On 16/02/2022 20:58, Alex Deucher wrote: On Wed, Feb 16, 2022 at 2:56 PM Eric Valette wrote: Here is the dmesg. For bisecting, I'm not home and the Intrenet connection is just too slow. In order to help a bit, I started to build kernel with the kernel patches set I had on my laptop so here it is: 5.11 suspend/resume is ok 5.12 suspend/resume is ok 5.13 suspend OK, resume KO, PC is dead I have to reboot. 5.14 suspend/resume is ok multiple times but I do have the exceptions at various places sudo dmesg | grep RIP [ 19.918769] RIP: 0010:ieee80211_reconfig+0x9a/0x1300 [ 19.918976] RIP: 0010:drv_remove_interface+0xd8/0xe0 [ 19.919086] RIP: 0010:drv_stop+0xb8/0xc0 [ 20.320553] RIP: 0010:iwl_mvm_mac_ctxt_init+0x1e2/0x220 [iwlmvm] [ 20.320801] RIP: 0033:0x7f0d4632536d 5.15 you have the result with latest one 5.15.24. RIP is at a given place. Sorry to be unable to do more. As a follow up : 5.17.1 from debian fixes the problem. Unfortunately it is not a long term kernel... -- eric
Bug#1008620: hplip: Please make hplip compatible with Python 3.10 transition
Package: hplip Version: 3.21.12+dfsg0-1 Severity: important Hplip is not mentionned in the python 3.10-add transition but is still not installable with python3.10 default. -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.108 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages hplip depends on: ii adduser3.121 ii cups 2.4.1op1-2 ii hplip-data 3.21.12+dfsg0-1 ii libc6 2.34-0experimental3 ii libcups2 2.4.1op1-2 ii libdbus-1-31.14.0-1 ii libhpmud0 3.21.12+dfsg0-1 ii libpython3.9 3.9.12-1 ii libsane-hpaio 3.21.12+dfsg0-1 ii libsane1 1.1.1-5 ii lsb-base 11.1.0 ii printer-driver-hpcups 3.21.12+dfsg0-1 ii python33.9.8-1 ii python3-dbus 1.2.18-3+b1 ii python3-gi 3.42.0-3 ii python3-pexpect4.8.0-2 ii python3-pil9.0.1-1 ii python3-reportlab 3.6.8-1 ii wget 1.21.2-2+b1 ii xz-utils 5.2.5-2 Versions of packages hplip recommends: ii avahi-daemon 0.8-5 ii policykit-1 0.120-6 ii printer-driver-postscript-hp 3.21.12+dfsg0-1 ii sane-utils1.1.1-5 Versions of packages hplip suggests: ii hplip-doc 3.21.12+dfsg0-1 ii hplip-gui 3.21.12+dfsg0-1 ii python3-notify20.3-4 ii system-config-printer 1.5.16-1 -- no debconf information
Bug#1008316: dpkg-fsys-usrunmess breaks system boot
On 28/03/2022 12:35, Guillem Jover wrote: There was no printed error beside the arror from dkms postinst (virtualbox assumed it was running virtualized, and nvidia just failling): just a congratulation message. Diid not check the return value of the script via echo $? Ok, so if the script did not finish with something like: ,--- error: cannot reconfigure packages: ... `--- Then I suppose it exited normally with something like: ,--- Done, hierarchy unmessed, congrats! Rebooting now is very strongly advised. (Note: you might need to run 'hash -r' in your shell.) `--- The latter. And I did the hash -r and rebooted... If the latter, I guess the maintainer script(s) running dkms, didn't exit non-zero. Hmm. Where those from external third-party packages? Third party code but packaged by debian members: dpkg -s nvidia-kernel-dkms Package: nvidia-kernel-dkms Status: install ok installed Priority: optional Section: non-free/kernel Installed-Size: 49099 Maintainer: Debian NVIDIA Maintainers Architecture: amd64 Multi-Arch: foreign Source: nvidia-graphics-drivers Version: 470.103.01-3 Provides: nvidia-kernel-470.103.01 Depends: dkms (>= 2.1.0.0), nvidia-firmware-470.103.01, nvidia-kernel-support--v1 Pre-Depends: nvidia-installer-cleanup Recommends: nvidia-driver (>= 470.103.01) | libcuda1 (>= 470.103.01) Description: NVIDIA binary kernel module DKMS source This package builds the NVIDIA Xorg binary kernel module needed by nvidia-driver, using DKMS. Provided that you have the kernel header packages installed, the kernel module will be built for your running kernel and automatically rebuilt for any new kernel headers that are installed. . The NVIDIA binary driver provides optimized hardware acceleration of OpenGL/GLX/EGL/GLES applications via a direct-rendering X Server for graphics cards using NVIDIA chip sets. . This version only supports GeForce, NVS, Quadro, RTX, Tesla, ... GPUs based on the Kepler (desktop cards only), Maxwell, Pascal, Volta, Turing, Ampere or newer architectures. The (Tesla) 470 drivers are the last driver series supporting GPUs based on the Kepler architecture. Look at the legacy driver packages for older cards. . See /usr/share/doc/nvidia-kernel-dkms/README.txt.gz for a complete list of supported GPUs and PCI IDs. . This package contains the blobs for building kernel modules for the amd64 architecture. Building the kernel modules has been tested up to Linux 5.17. Homepage: https://www.nvidia.com dpkg -s virtualbox-dkms Package: virtualbox-dkms Status: install ok installed Priority: optional Section: contrib/kernel Installed-Size: 5571 Maintainer: Debian Virtualbox Team Architecture: amd64 Source: virtualbox (6.1.32-dfsg-1) Version: 6.1.32-dfsg-1+b2 Provides: virtualbox-modules Depends: dkms (>= 2.1.0.0) Recommends: virtualbox (>= 6.1.32-dfsg-1) Description: x86 virtualization solution - kernel module sources for dkms VirtualBox is a free x86 virtualization solution allowing a wide range of x86 operating systems such as Windows, DOS, BSD or Linux to run on a Linux system. . This package provides the source code for the virtualbox kernel module to be build with dkms. Kernel sources or headers are required to compile this module. Homepage: https://www.virtualbox.org So you probably should copy /usr/lib/modules to /lib/modules before the calling the postinstall. Hmm, right, because these were not tracked, they got missed in the migration. I've checked the Debian archive and at least there, it does not look like anything else besides kernel modules are being current shipped in those directories (via apt-file), but the problem is that I've seen references in source code (via codesearch.d.o) to /usr/lib/modules, for at least apache and python modules, so I don't think an unconditional move for untracked files would be safe there. I'm thinking the following special-case options (in order of decreasing preference): * move only untracked «/usr/lib/modules/[0-9]*» expecting/assuming those to be kernel modules, You could move only the current running kernel modules using uname to find the version. It will not hurt and they will be rebuild anyway at least for the dkms ones. I guess that would be another option yes, thanks. The real problem being that dkms generated file does not appear in any file Sure. I'll try to prepare something later today. And thanks for the script anyway it helped a lot. Did not even remembered I used usrmerge and it did such a mess/wreckage. -- eric
Bug#1008316: dpkg-fsys-usrunmess breaks system boot
Package: dpkg Version: 1.21.4 Severity: critical Justification: breaks the whole system Gobally the scripts does a very good job but it missed to copy /usr/lib/modules to /lib/modules on a self generated kernel that has modules build via dkms and a few native kernel modules. Invoquing the dkms postinstall script fails because it does not find /lib/modules/x.y.z directories and rebooting without graphic drivers and other stff does not work. So you probably should copy /usr/lib/modules to /lib/modules before the calling the postinstall. To fix i did: 1) boot in recovery mode, 2) copy /usr/lib/modules to /lib/modules 3) dkms autoinstall 4) update-grub and it wworked. -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.106 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages dpkg depends on: ii libbz2-1.0 1.0.8-5 ii libc62.34-0experimental3 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 apt2.4.3 pn debsig-verify -- no debconf information
Bug#1006542: apt: Please provide a script to export keys from trusted.gpg and reference it in apt-key(8)
Package: apt Version: 2.4.0 Severity: wishlist Since new version I have warning about keys that have been stored in trusted.gpg file. I do see the export or exportall command in apt-key (8) man page but wonder how to automate the extraction and what is the best storage replacement. It would be fine to provide a script that does the conversion if you intent to really suppress the trusted.gpg support -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (no /etc/apt/preferences.d/* present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- (/etc/apt/sources.list.d/cisofy-lynis.list present, but not submitted) -- -- /etc/apt/sources.list.d/google-chrome.list -- deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main -- (/etc/apt/sources.list.d/orange-repo-microsoft-teams.list present, but not submitted) -- -- (/etc/apt/sources.list.d/orange-repo-wire.list present, but not submitted) -- -- (/etc/apt/sources.list.d/orange-repo-yourdev-gruik.list present, but not submitted) -- -- (/etc/apt/sources.list.d/orange-repo-yourdev.list present, but not submitted) -- -- (/etc/apt/sources.list.d/signal-xenial.list present, but not submitted) -- -- (/etc/apt/sources.list.d/skype-stable.list present, but not submitted) -- -- (/etc/apt/sources.list.d/skype-unstable.list present, but not submitted) -- -- (/etc/apt/sources.list.d/slack.list present, but not submitted) -- -- (/etc/apt/sources.list.d/sublime-text.list present, but not submitted) -- -- (/etc/apt/sources.list.d/vscode.list present, but not submitted) -- -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.102 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) Versions of packages apt depends on: ii adduser 3.118 ii debian-archive-keyring 2021.1.1 ii gpgv2.3.1-1 ii gpgv2 2.3.1-1 ii libapt-pkg6.0 2.4.0 ii libc6 2.34-0experimental3 ii libgcc-s1 12-20220222-1 ii libgnutls30 3.7.3-4+b1 ii libseccomp2 2.5.3-2 ii libstdc++6 12-20220222-1 ii libsystemd0 250.3-2 Versions of packages apt recommends: ii ca-certificates 20211016 Versions of packages apt suggests: pn apt-doc ii aptitude0.8.13-3 ii dpkg-dev1.21.1 ii gnupg 2.3.1-1 ii powermgmt-base 1.36 ii synaptic0.90.2+b1 -- no debconf information
Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
On 20/02/2022 16:48, Dominique Dumont wrote: On Monday, 14 February 2022 22:52:27 CET Alex Deucher wrote: Does the system actually suspend? Not really. The screens looks like it's going to suspend, but it does come back after 10s or so. The light mounted in the middle of the power button does not switch off. As I have a very similar problem and also commented on the original debian bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005005), I will add some information here on another amd only laptop (renoir AMD Ryzen 7 4800H with Radeon Graphics + Radeon RX 5500/5500M / Pro 5500M). For me the suspend works once, but after the first resume (I do know know if it is in the suspend path or the resume path I see a RIP in the dmesg (see aditional info in debian bug)) and later suspend do not work: It only go to the kde login screen. I was unable due to network connectivity to do a full bisect but tested with the patch I had on my laptop: 5.10.101 works, 5.10 from debian works 5.11 works 5.12 works 5.13 suspend works but when resuming the PC is dead I have to reboot 5.14 seems to work but looking at dmesg it is full of RIP messages at various places. 5.15.24 is a described 5.15 from debian is behaving identically 5.16 from debian is behaving identically. Is this system S0i3 or regular S3? For me it is real S3. The proposed patch is intended for INTEl + intel gpu + amdgpu but I have dual amd GPU. --eric
Bug#1005067: closed by Debian FTP Masters (reply to Dylan Aïssi ) (Bug#1005067: fixed in pipewire 0.3.46-1)
On 17/02/2022 22:27, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the pipewire-pulse package: I confirm it WFM. Thanks. -- eric
Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces
On 16/02/2022 21:01, Eric Valette wrote: On 16/02/2022 20:58, Alex Deucher wrote: On Wed, Feb 16, 2022 at 2:56 PM Eric Valette wrote: Here is the dmesg. For bisecting, I'm not home and the Intrenet connection is just too slow. In order to help a bit, I started to build kernel with the kernel patches set I had on my laptop so here it is: 5.11 suspend/resume is ok 5.12 suspend/resume is ok 5.13 suspend OK, resume KO, PC is dead I have to reboot. 5.14 suspend/resume is ok multiple times but I do have the exceptions at various places sudo dmesg | grep RIP [ 19.918769] RIP: 0010:ieee80211_reconfig+0x9a/0x1300 [ 19.918976] RIP: 0010:drv_remove_interface+0xd8/0xe0 [ 19.919086] RIP: 0010:drv_stop+0xb8/0xc0 [ 20.320553] RIP: 0010:iwl_mvm_mac_ctxt_init+0x1e2/0x220 [iwlmvm] [ 20.320801] RIP: 0033:0x7f0d4632536d 5.15 you have the result with latest one 5.15.24. RIP is at a given place. Sorry to be unable to do more. --eric
Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces
On Tue, 15 Feb 2022 15:42:27 -0500 Alex Deucher wrote: What chip is this? Can you provide the full dmesg output? Its a a renoir chip with a second gpu : [Radeon RX 5500/5500M / Pro 5500M]. Processor Information Socket Designation: FP6 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 01 0F 86 00 FF FB 8B 17 Signature: Family 23, Model 96, Stepping 1 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Multi-threading) Version: AMD Ryzen 7 4800H with Radeon Graphics Voltage: 1.2 V External Clock: 100 MHz Max Speed: 4300 MHz Current Speed: 2900 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x000D L2 Cache Handle: 0x000E L3 Cache Handle: 0x000F Serial Number: Unknown Asset Tag: Unknown Part Number: Unknown Core Count: 8 Core Enabled: 8 Thread Count: 16 Characteristics: 64-bit capable Multi-Core Hardware Thread Execute Protection Enhanced Virtualization Power/Performance Control
Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces
On 15/02/2022 19:14, Eric Valette wrote: Since I upgraded from 5.10 (own compiled kernel or debian kernel) to 5.15 (own compiled from same config or debian kernel) and even 5.16 kernel from debian, I get this behavior : 1) First suspend and resume works, 2) But later suspendend always fails. I have kernel exceptions in amdgpu : In addition when booting 5.10 I get this message : /var/log/syslog.1:Feb 13 11:11:48 pink-floyd3 kernel: [3.035073] amdgpu :03:00.0: amdgpu: ACPI VFCT table present but broken (too short #2),skipping and I do not see it on console with later kernels. Feb 14 15:40:58 pink-floyd3 kernel: [ 830.803952] Hardware name: Micro-Star International Co., L td. Bravo 17 A4DDR/MS-17FK, BIOS E17FKAMS.117 10/29/2020 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.803956] Workqueue: pm pm_runtime_work Feb 14 15:40:58 pink-floyd3 kernel: [ 830.803966] RIP: 0010:dm_suspend+0x241/0x260 [amdgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804340] Code: 4c 89 e6 4c 89 ef e8 ee 8a 16 00 83 f8 0 1 74 21 89 c2 48 c7 c6 a0 59 69 c1 48 c7 c7 60 83 76 c1 e8 14 ba 06 ff e9 6d ff ff ff <0f> 0b e9 f8 fd ff ff 4c 89 e6 4c 89 ef e8 6d ba 15 00 e9 56 ff ff Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804344] RSP: 0018:ae6040647c90 EFLAGS: 00010286 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804348] RAX: RBX: 973088a4 RC X: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804351] RDX: 000a RSI: RD I: 973088a4 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804353] RBP: R08: 03c0ca00 R0 9: 80380002 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804356] R10: 9730860f25a0 R11: 005f R1 2: 973088a4 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804358] R13: 97308132a0d0 R14: 0008 R1 5: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804361] FS: () GS:97339f68000 0() knlGS: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804364] CS: 0010 DS: ES: CR0: 80050 033 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804366] CR2: 7fb8c9ce6000 CR3: 0001115fa000 CR 4: 00350ee0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804369] Call Trace: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804375] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804380] ? nv_common_set_clockgating_state+0xa3/0xb0 [ amdgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804693] amdgpu_device_ip_suspend_phase1+0x63/0xc0 [am dgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804977] amdgpu_device_suspend+0x66/0x110 [amdgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805260] amdgpu_pmops_runtime_suspend+0xad/0x180 [amdg pu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805542] pci_pm_runtime_suspend+0x5a/0x160 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805549] ? pci_dev_put+0x20/0x20 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805553] __rpm_callback+0x44/0x150 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805558] ? pci_dev_put+0x20/0x20 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805561] rpm_callback+0x59/0x70 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805565] ? pci_dev_put+0x20/0x20 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805568] rpm_suspend+0x14a/0x720 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805572] ? _raw_spin_unlock+0x16/0x30 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805580] ? finish_task_switch.isra.0+0xc1/0x2f0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805586] ? __switch_to+0x114/0x440 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805593] pm_runtime_work+0x94/0xa0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805597] process_one_work+0x1e8/0x3c0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805604] worker_thread+0x50/0x3b0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805608] ? rescuer_thread+0x370/0x370 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805611] kthread+0x16b/0x190 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805616] ? set_kthread_struct+0x40/0x40 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805621] ret_from_fork+0x22/0x30 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805630] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805632] ---[ end trace 8d77579b410d926d ]--- Feb 14 15:40:58 pink-floyd3 kernel: [ 831.142133] amdgpu :03:00.0: [drm:amdgpu_ring_test_hel per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Feb 14 15:40:58 pink-floyd3 kernel: [ 831.142444] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ d isable failed Feb 14 15:40:59 pink-floyd3 kernel: [ 831.462157] amdgpu :03:00.0: [drm:amdgpu_ring_test_hel per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Feb 14 15:40:59 pink-floyd3 kernel: [ 831.462465] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ d isable failed Feb 14 15:40:59 pink-floyd3 kernel: [ 831.782375] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* faile d to halt cp gfx Feb 14 15:41:05 pink-floyd3 kernel: [ 837.297839] amdgp
Bug#1005005: same behavior on my MSI Bravo 17 A4DDR : second resume fails and exception in kernel traces
Since I upgraded from 5.10 (own compiled kernel or debian kernel) to 5.15 (own compiled from same config or debian kernel) and even 5.16 kernel from debian, I get this behavior : 1) First suspend and resume works, 2) But later suspendend always fails. I have kernel exceptions in amdgpu : Feb 14 15:40:58 pink-floyd3 kernel: [ 830.803952] Hardware name: Micro-Star International Co., L td. Bravo 17 A4DDR/MS-17FK, BIOS E17FKAMS.117 10/29/2020 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.803956] Workqueue: pm pm_runtime_work Feb 14 15:40:58 pink-floyd3 kernel: [ 830.803966] RIP: 0010:dm_suspend+0x241/0x260 [amdgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804340] Code: 4c 89 e6 4c 89 ef e8 ee 8a 16 00 83 f8 0 1 74 21 89 c2 48 c7 c6 a0 59 69 c1 48 c7 c7 60 83 76 c1 e8 14 ba 06 ff e9 6d ff ff ff <0f> 0b e9 f8 fd ff ff 4c 89 e6 4c 89 ef e8 6d ba 15 00 e9 56 ff ff Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804344] RSP: 0018:ae6040647c90 EFLAGS: 00010286 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804348] RAX: RBX: 973088a4 RC X: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804351] RDX: 000a RSI: RD I: 973088a4 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804353] RBP: R08: 03c0ca00 R0 9: 80380002 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804356] R10: 9730860f25a0 R11: 005f R1 2: 973088a4 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804358] R13: 97308132a0d0 R14: 0008 R1 5: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804361] FS: () GS:97339f68000 0() knlGS: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804364] CS: 0010 DS: ES: CR0: 80050 033 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804366] CR2: 7fb8c9ce6000 CR3: 0001115fa000 CR 4: 00350ee0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804369] Call Trace: Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804375] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804380] ? nv_common_set_clockgating_state+0xa3/0xb0 [ amdgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804693] amdgpu_device_ip_suspend_phase1+0x63/0xc0 [am dgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.804977] amdgpu_device_suspend+0x66/0x110 [amdgpu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805260] amdgpu_pmops_runtime_suspend+0xad/0x180 [amdg pu] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805542] pci_pm_runtime_suspend+0x5a/0x160 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805549] ? pci_dev_put+0x20/0x20 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805553] __rpm_callback+0x44/0x150 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805558] ? pci_dev_put+0x20/0x20 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805561] rpm_callback+0x59/0x70 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805565] ? pci_dev_put+0x20/0x20 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805568] rpm_suspend+0x14a/0x720 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805572] ? _raw_spin_unlock+0x16/0x30 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805580] ? finish_task_switch.isra.0+0xc1/0x2f0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805586] ? __switch_to+0x114/0x440 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805593] pm_runtime_work+0x94/0xa0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805597] process_one_work+0x1e8/0x3c0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805604] worker_thread+0x50/0x3b0 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805608] ? rescuer_thread+0x370/0x370 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805611] kthread+0x16b/0x190 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805616] ? set_kthread_struct+0x40/0x40 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805621] ret_from_fork+0x22/0x30 Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805630] Feb 14 15:40:58 pink-floyd3 kernel: [ 830.805632] ---[ end trace 8d77579b410d926d ]--- Feb 14 15:40:58 pink-floyd3 kernel: [ 831.142133] amdgpu :03:00.0: [drm:amdgpu_ring_test_hel per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Feb 14 15:40:58 pink-floyd3 kernel: [ 831.142444] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ d isable failed Feb 14 15:40:59 pink-floyd3 kernel: [ 831.462157] amdgpu :03:00.0: [drm:amdgpu_ring_test_hel per [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Feb 14 15:40:59 pink-floyd3 kernel: [ 831.462465] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ d isable failed Feb 14 15:40:59 pink-floyd3 kernel: [ 831.782375] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* faile d to halt cp gfx Feb 14 15:41:05 pink-floyd3 kernel: [ 837.297839] amdgpu :03:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x003A SMN_C2PMSG_82:0x
Bug#1005067: I suspect this bug is caused by having CONFIG_SND_VERBOSE_PROCFS not set. Fixed upstream
https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1148 -- eric
Bug#1005067: looking at apt history, it seems 0.3.44 was working and upgrading to 0.3.45 broke the audio.
Did not downgrade to confirm as I need audio ATM. -- eric
Bug#1005067: pipewire-pulse/wireplumber breaks kde audio
Package: pipewire-pulse Version: 0.3.45-1 Severity: important Today, wanted to liusten some music and discovered, I had no devices seen by kde audio. Looked at the log. got a bunch of: 1) /var/log/user.log.1:Feb 5 10:46:15 tri-yann4 pipewire-pulse[1824]: mod.protocol-pulse: client 0x557b90aba260 [kwin_killer_helper]: ERROR command:-1 (invalid) tag:106 error:25 (Input/output error) 2) /var/log/user.log.1:Feb 2 09:20:43 tri-yann4 pipewire-pulse[9372]: mod.rt: could not make thread 9380 realtime using RTKit: Permission denied removed pipewire-pulse and rebooted. Got back my audio devices. Looked at debian page for pipewire, reinstalled pipewire-pulse, wireplumber did the user space command to start it via systemd, also rmove /etc/pipewire as suggested. Rebooted. Still no audio. aplay -L list the devices correctly but they are not acessible ... -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.96 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) Versions of packages pipewire-pulse depends on: ii init-system-helpers 1.61 ii pipewire 0.3.45-1 pipewire-pulse recommends no packages. pipewire-pulse suggests no packages.
Bug#1000741: w-scan is obsolete (2017) and has been replaced by w_scan_cpp by upstream author
Package: w-scan Version: 20170107-2.1 Severity: important Tags: upstream See : https://www.gen2vdr.de/wirbel/w_scan_cpp/index2.html Unfortunately it is in german but w_scan_cpp ist ein DVB Kanalscanner und der Nachfolger von w_scan. means that w_scan_cpp is the sucessor of w_scan by upstream author. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.82 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages w-scan depends on: ii libc6 2.33-0experimental2 w-scan recommends no packages. w-scan suggests no packages. -- no debconf information
Bug#996398: libkdecorations2-5v5: experimental version is instalable and breaks unstable
Package: libkdecorations2-5v5 Version: 4:5.22.90-1 Severity: important Please add a dependency that prevent upgrading. You cannot even log afetr sddm restart. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.72 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) Versions of packages libkdecorations2-5v5 depends on: ii libc6 2.33-0experimental2 ii libkdecorations2private9 4:5.22.90-1 ii libkf5i18n5 5.86.0-1 ii libqt5core5a 5.15.2+dfsg-12 ii libqt5gui55.15.2+dfsg-12 ii libstdc++611.2.0-9 libkdecorations2-5v5 recommends no packages. libkdecorations2-5v5 suggests no packages. -- no debconf information
Bug#993409: digikam: Please package digikam 7.3
Package: digikam Version: 4:7.1.0-2+b1 Severity: wishlist Rebuilding is fine to cope with kdepim, but making an uptodate version is even better. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.61 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) Versions of packages digikam depends on: ii digikam-data 4:7.1.0-2 ii digikam-private-libs 4:7.1.0-2+b1 ii libc6 2.32-0experimental1 ii libgcc-s1 11.2.0-3 ii libkf5configcore5 5.85.0-2 ii libkf5coreaddons5 5.85.0-2 ii libkf5i18n5 5.85.0-2 ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.3 ii libqt5core5a 5.15.2+dfsg-10 ii libqt5gui55.15.2+dfsg-10 ii libqt5sql55.15.2+dfsg-10 ii libqt5sql5-mysql 5.15.2+dfsg-10 ii libqt5sql5-sqlite 5.15.2+dfsg-10 ii libqt5widgets55.15.2+dfsg-10 ii libstdc++611.2.0-3 ii perl 5.32.1-5 Versions of packages digikam recommends: ii ffmpegthumbs4:21.08.0-1 ii firefox-esr [www-browser] 91.0.1esr-1 ii google-chrome-stable [www-browser] 93.0.4577.63-1 ii konqueror [www-browser] 4:21.08.0-1 ii links2 [www-browser]2.23-1 ii lynx [www-browser] 2.9.0dev.9-2 ii w3m [www-browser] 0.5.3+git20210102-6 Versions of packages digikam suggests: pn digikam-doc ii systemsettings 4:5.21.5-2 -- no debconf information
Bug#992639: debianutils: move of installkernel to /usr/sbin/installkernel breaks kernel build on system with separate / and /usr
On 21/08/2021 18:33, Clint Adams wrote: On Sat, Aug 21, 2021 at 06:30:21PM +0200, Eric Valette wrote: And for the sake of completeness, I already did merge. Just no remembered it! So even for merged / and /usr system there is a bug unless usrmerge is installed. I'm confused. You installed usrmerge but then deleted the /sbin symlink? Ok. It was indeed unclear. Sorry. When I first installed the NAS I had separated disks partitions for / and /usr and in that case hard link do not work at all. I did not remembered I did already probably boot on a rescue usb key and did the merge using the data raid partition has a temporary space holder to copy both / and /usr to a directory there, remove the two partitions, recreate a single partition using the free space and copy back the content. This is was I called merged / and /usr. I probably never installed usrmerge once done because I had no need to do so. -- eric
Bug#992639: debianutils: move of installkernel to /usr/sbin/installkernel breaks kernel build on system with separate / and /usr
I do not mind deciding everything should be in /usr but as pointed out there are other project that should adapt. And for the sake of completeness, I already did merge. Just no remembered it! So even for merged / and /usr system there is a bug unless usrmerge is installed. -- eric
Bug#992639: debianutils: move of installkernel to /usr/sbin/installkernel breaks kernel build on system with separate / and /usr
On 21/08/2021 18:09, Clint Adams wrote: On Sat, Aug 21, 2021 at 06:04:33PM +0200, Eric Valette wrote: if you expect to have unconditionally it make a depends and people with not enough place to merge / and /usr will explain you maybe not politely you broke their system... That would make it impossible to purge usrmerge after install, which would be unfortunate. For my personnal case, On a NAS with only remote access, repartioning on the fly is a bit tricky and that has been live for about 8 years... What is your plan? Keep running sid on your NAS until 2 years from now and then never upgrade again when unmerged /usr is completely unsupported in the stable release? Avoid to make the merge as long as possible until everyting is fixed everywhere. Recent changes did broke various things if I look at critical bug. It also broke at least my laptop with no way to enter X11 (and here / and /usr are already merged). The location is incorrect anyway unless upstream kernel explicitly makes a change. I do not mind deciding everything should be in /usr but as pointed out there are other project that should adapt. -- eric
Bug#992639: debianutils: move of installkernel to /usr/sbin/installkernel breaks kernel build on system with separate / and /usr
On 21/08/2021 17:56, Clint Adams wrote: On Sat, Aug 21, 2021 at 05:51:06PM +0200, Eric Valette wrote: But as nobody makes the link, there is a problem by default. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978636#178 As soon as you install the usrmerge package you should be fine. if you expect to have unconditionally it make a depends and people with not enough place to merge / and /usr will explain you maybe not politely you broke their system... For my personnal case, On a NAS with only remote access, repartioning on the fly is a bit tricky and that has been live for about 8 years... -- eric
Bug#992639: debianutils: move of installkernel to /usr/sbin/installkernel breaks kernel build on system with separate / and /usr
On 21/08/2021 17:48, Clint Adams wrote: On Sat, Aug 21, 2021 at 05:45:48PM +0200, Eric Valette wrote: But upstream kernel look explicitely in /sbin so there will be a problem... /usr/src/linux-zotac-h67itx# sh -x /usr/src/linux-5.10.7/arch/x86/boot/install.sh 5.10.60 arch/x86/boot/bzImage System.map "/boot" + verify arch/x86/boot/bzImage + '[' '!' -f arch/x86/boot/bzImage ']' + verify System.map + '[' '!' -f System.map ']' + '[' -x /root/bin/installkernel ']' + '[' -x /sbin/installkernel ']' + exec /sbin/installkernel 5.10.60 arch/x86/boot/bzImage System.map /boot Once your /sbin is a symlink to usr/sbin, that problem will go away. But as nobody makes the link, there is a problem by default. -- eric