Bug#1072295: psensor: After updating psensor there are now two icons in the system tray
Hi, I'm pretty sure there should not be two icons, I know that one icon is a status notifier and one is a systray icon. But that doesn't change that fact that one program should have one tray icon not two. Konomi
Bug#1072295: psensor: After updating psensor there are now two icons in the system tray
I've also tested version 1.2.1-1 on XFCE and observed the same problem. Konomi
Bug#1072295: psensor: After updating psensor there are now two icons in the system tray
Package: psensor Version: 1.2.1-1 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating psensor from version 1.1.5-1.4+b1 to 1.2.1-1 I now have two icons in the system tray instead of one. I'm currently using the latest version of KDE from unstable. Konomi -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.11-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages psensor depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2 ii libatasmart4 0.19-5+b1 ii libayatana-appindicator3-1 0.5.93+really-1 ii libc62.38-11 ii libcairo21.18.0-3+b1 ii libcurl3t64-gnutls 8.8.0-1 ii libglib2.0-0t64 2.80.2-2 ii libgtk-3-0t643.24.41-4 ii libgtop-2.0-11 2.41.3-1+b1 ii libjson-c5 0.17-1+b1 ii libnotify4 0.8.3-1+b1 ii libsensors5 1:3.6.0-9 ii libudisks2-0 2.10.1-7 ii libx11-6 2:1.8.7-1+b1 ii libxnvctrl0 535.171.04-1 ii psensor-common 1.2.1-1 psensor recommends no packages. psensor suggests no packages. -- no debconf information
Bug#1072219: gtk+3.0: After updating to version 3.24.42-1 Firefox no longer remembers it's window size and positon in Wayland
Source: gtk+3.0 Version: 3.24.42-1 Severity: important X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating from version 3.24.41-4 to 3.24.42-1 Firefox no longer remembers it's window size and position. This only happens when using wayland as far as I can tell, the X11 backend of Firefox is unaffected. Looking at the changelog for 3.24.42 I believe the following changes are probably caused this bug. * Wayland: - Fix monitor sizes - Fix a crash related to tablet removal - Infer resizable edges for tiled windows - Always commit soon after acking a configure Thanks for your time. Konomi -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.11-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1071744: apt: search '?installed ?not(?automatic)' causes regex compilation error
Package: apt Version: 2.9.3 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, Running `apt search '?installed ?not(?automatic)'` results in the following message: "Error: Regex compilation error". Using the same search terms in aptitude `aptitude search '?installed ?not(?automatic)'` works as expected. Konomi -- Package-specific info: -- (/etc/apt/preferences present, but not submitted) -- -- (/etc/apt/preferences.d/apt-listbugs present, but not submitted) -- -- (/etc/apt/sources.list present, but not submitted) -- -- (no /etc/apt/sources.list.d/* present) -- -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apt depends on: ii adduser 3.137 ii base-passwd 3.6.3 ii debian-archive-keyring 2023.4 ii gpgv2.2.43-6 ii libapt-pkg6.0t642.9.3 ii libc6 2.38-11 ii libgcc-s1 14.1.0-1 ii libgnutls30t64 3.8.5-2 ii libseccomp2 2.5.5-1 ii libstdc++6 14.1.0-1 ii libsystemd0 256~rc3-2 Versions of packages apt recommends: ii ca-certificates 20240203 Versions of packages apt suggests: ii apt-doc 2.9.3 ii aptitude0.8.13-6 ii dpkg-dev1.22.6 ii gnupg 2.2.43-6 ii powermgmt-base 1.37 -- no debconf information
Bug#1071263: linux-image-6.8.9-amd64: Vulkan applications crash on computers using amdgpu
Package: linux-image-6.8.9-amd64 Version: 6.8.9-1 Severity: important Tags: patch upstream X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, Vulkan applications will crash when using version 6.8.9 of the linux kernel on systems using amd graphics. Upstream have provided a patch [1] that fixes this issue. There's also a bug report upstream as well [2] for more details. I've also provided a link to the kernel specific patch [3]. 6.8.10 also has this issue fixed. [1] https://patchwork.freedesktop.org/patch/593130/ [2] https://gitlab.freedesktop.org/drm/amd/-/issues/3343 [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c?id=37447cc246293ab6a0bbeb091ece95f57adcc845 -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.8.9-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod32-1 ii linux-base 4.9 Versions of packages linux-image-6.8.9-amd64 recommends: ii apparmor 3.0.13-2 Versions of packages linux-image-6.8.9-amd64 suggests: ii debian-kernel-handbook 1.0.21 ii firmware-linux-free 20200122-4 ii grub-efi-amd64 2.12-2 pn linux-doc-6.8
Bug#1071201: systemd-journald[468]: Assertion 'unit' failed at src/journal/journald-server.c:3015, function config_parse_compress(). Aborting.
I've reported this upstream: https://github.com/systemd/systemd/issues/32856
Bug#1058886: irqbalance: floods logs with ---...--- lines
There's an upstream issue for this on GitHub [1] where the developer is recommending cherry picking the commit to fix this issue. [1] https://github.com/Irqbalance/irqbalance/issues/281
Bug#1055694: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 360448 10 ansi_cprng 12288 0 iwlwifi 544768 1 iwlmvm snd_hda_codec 225280 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek crypto_simd16384 1 aesni_intel cryptd 28672 3 crypto_simd,ghash_clmulni_intel ecdh_generic 16384 2 bluetooth rapl 20480 0 ecc45056 1 ecdh_generic snd_seq_device 16384 2 snd_seq,snd_rawmidi crc16 12288 1 bluetooth snd_hda_core 147456 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek mc 94208 1 snd_usb_audio wmi_bmof 12288 0 snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec gigabyte_wmi 12288 0 sg 45056 0 cfg80211 1339392 3 iwlmvm,iwlwifi,mac80211 joydev
Bug#1038448: aptitude: sometimes aptitude prefers foreign architectures when using safe-upgrade
Package: aptitude
Version: 0.8.13-5
Followup-For: Bug #1038448
X-Debbugs-Cc: konomikit...@gmail.com
Dear Maintainer,
The following workaround seems to help:
/etc/apt/preferences
Package: linux-kbuild-*:i386
Pin: release o=Debian
Pin-Priority: -1
Before doing the workaround:
$ sudo aptitude safe-upgrade linux-image-amd64 linux-headers-amd64
Resolving dependencies...
The following NEW packages will be installed:
linux-headers-6.5.0-2-amd64{a} linux-headers-6.5.0-2-common{a} linux-
image-6.5.0-2-amd64{a}
linux-kbuild-6.5.0-2:i386{a}
The following packages will be upgraded:
linux-headers-amd64 linux-image-amd64
2 packages upgraded, 4 newly installed, 0 to remove and 71 not upgraded.
Need to get 87.8 MB of archives. After unpacking 540 MB will be used.
Do you want to continue? [Y/n/?]
After doing the workaround:
$ sudo aptitude safe-upgrade linux-image-amd64 linux-headers-amd64
Resolving dependencies...
The following NEW packages will be installed:
linux-headers-6.5.0-2-amd64{a} linux-headers-6.5.0-2-common{a} linux-
image-6.5.0-2-amd64{a}
linux-kbuild-6.5.0-2{a}
The following packages will be upgraded:
linux-headers-amd64 linux-image-amd64
2 packages upgraded, 4 newly installed, 0 to remove and 71 not upgraded.
Need to get 87.8 MB of archives. After unpacking 540 MB will be used.
Do you want to continue? [Y/n/?]
-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude
aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
apt version 6.0.0
NCurses version 6.3
libsigc++ version: 2.10.8
Gtk+ support disabled.
Qt support disabled.
Current library versions:
NCurses version: ncurses 6.4.20230625
cwidget version: 0.5.18
Apt version: 6.0.0
aptitude linkage:
linux-vdso.so.1 (0x7ffd4b1b6000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
(0x7f10fb00)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6
(0x7f10fb3c7000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6
(0x7f10fb392000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0
(0x7f10fb83a000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4
(0x7f10fb2a)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0
(0x7f10fae93000)
libboost_iostreams.so.1.74.0 =>
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f10fb82)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30
(0x7f10fac0)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f10fb81b000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f10fa80)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f10fab21000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f10fb27c000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f10fa61e000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f10fb25d000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
(0x7f10fb24a000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f10fae63000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f10fb224000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f10faa6)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f10fae31000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0
(0x7f10fa53d000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20
(0x7f10fa3f6000)
libxxhash.so.0 => /lib/x86_64-linux-gnu/libxxhash.so.0
(0x7f10fa3e3000)
/lib64/ld-linux-x86-64.so.2 (0x7f10fb864000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f10faa56000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f10fa3d7000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0
(0x7f10fa3af000)
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages aptitude depends on:
ii aptitude-common 0.8.13-5
ii libapt-pkg6.0 2.7.6
ii libboost-iostreams1.74.0 1.74.0+ds1-23
ii libc6 2.37-12
ii libcwidget4 0.5.18-6
ii libgcc-s1 13.2.0-5
ii libncursesw6 6.4+20230625-2
ii libsigc++-2.0-0v5 2.12.0-1
ii libsqlite3-0 3.43.2-1
ii libstdc++613.2.0-5
ii libtinfo6 6.4+20230625-2
ii libxapian30 1.4.22-1
Bug#1038448: aptitude: sometimes aptitude prefers foreign architectures when using safe-upgrade
Dear Maintainer,
This bug is now happening every time a new kernel version comes to the
repositories. It really doesn't feel like safe-upgrade is the correct
name for this parameter when it is pulling in a foreign architecture
package that breaks building some kernel modules. Could someone please
have a look at this? Again here is the output of my safe-upgrade
command:
$ sudo aptitude -sv safe-upgrade
Resolving dependencies...
The following NEW packages will be installed:
linux-compiler-gcc-13-x86{a} linux-doc-6.4{a} linux-headers-6.4.0-1-amd64{a}
linux-headers-6.4.0-1-common{a} linux-image-6.4.0-1-amd64{a}
linux-kbuild-6.4.0-1:i386{a}
The following packages will be upgraded:
gir1.2-gtk-3.0 gtk-3-examples gtk-update-icon-cache libcpupower1
libglib2.0-0 libglib2.0-0:i386
libglib2.0-bin libglib2.0-data libglib2.0-dev libglib2.0-dev-bin
libgoa-1.0-0b libgoa-1.0-common
libgtk-3-0 libgtk-3-bin libgtk-3-common libgtk-3-dev libkpathsea6
libncurses6 libncurses6:i386
libncursesw6 libncursesw6:i386 libptexenc1 libqt6core6 libqt6dbus6
libqt6gui6 libqt6network6
libqt6opengl6 libqt6openglwidgets6 libqt6printsupport6 libqt6qml6
libqt6qmlmodels6 libqt6quick6
libqt6quickwidgets6 libqt6sql6 libqt6sql6-ibase libqt6sql6-mysql
libqt6sql6-odbc libqt6sql6-psql
libqt6sql6-sqlite libqt6test6 libqt6widgets6 libqt6xml6 libsynctex2
libtexlua53-5 libtexluajit2
libtinfo6 libtinfo6:i386 libudisks2-0 linux-cpupower linux-doc
linux-headers-amd64 linux-image-amd64
linux-libc-dev ncurses-base ncurses-bin python3-charset-normalizer
python3-gi python3-gi-cairo
python3-pluggy python3-typing-extensions qt6-gtk-platformtheme
qt6-image-formats-plugins
qt6-qpa-plugins texlive-binaries udisks2
65 packages upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 169 MB of archives. After unpacking 724 MB will be used.
Note: Using 'Simulate' mode.
Do you want to continue? [Y/n/?] n
Abort.
Bug#1038448: aptitude: sometimes aptitude prefers foreign architectures when using safe-upgrade
Package: aptitude
Version: 0.8.13-5
Severity: important
X-Debbugs-Cc: konomikit...@gmail.com
Dear Maintainer,
Sometimes aptitude makes bad choices when safe-upgrade is used, the problem
is probably in the aptitude resolver. Here is an example of this happening:
$ sudo aptitude safe-upgrade linux-headers-amd64
Resolving dependencies...
The following NEW packages will be installed:
linux-headers-6.3.0-1-amd64{a} linux-headers-6.3.0-1-common{a} linux-
kbuild-6.3:i386{a}
The following packages will be upgraded:
linux-headers-amd64
1 packages upgraded, 3 newly installed, 0 to remove and 33 not upgraded.
Need to get 0 B/12.0 MB of archives. After unpacking 63.8 MB will be used.
Here aptitude wants to install linux-kbuild-6.3:i386 instead of
linux-kbuild-6.3:amd64. If I switch to using full-upgrade I get the following:
$ sudo aptitude full-upgrade linux-headers-amd64
The following NEW packages will be installed:
linux-doc-6.3{a} linux-headers-6.3.0-1-amd64{a} linux-
headers-6.3.0-1-common{a}
linux-image-6.3.0-1-amd64{a} linux-kbuild-6.3{a}
The following packages will be upgraded:
libcpupower1 linux-cpupower linux-doc linux-headers-amd64 linux-image-amd64
linux-libc-dev
6 packages upgraded, 5 newly installed, 0 to remove and 28 not upgraded.
Need to get 914 kB/124 MB of archives. After unpacking 718 MB will be used.
This actually caused a dkms module to stop compiling:
DKMS make.log for it87-20230126 for kernel 6.3.0-1-amd64 (x86_64)
Thu 15 Jun 2023 14:12:15 AEST
CC [M] /var/lib/dkms/it87/20230126/build/it87.o
MODPOST /var/lib/dkms/it87/20230126/build/Module.symvers
FATAL: modpost: /var/lib/dkms/it87/20230126/build/it87: sizeof(struct
dmi_device_id)=332 is not a modulo of the size of section
__mod_dmi___device_table=7224.
Fix definition of struct dmi_device_id in mod_devicetable.h
make[2]: *** [/usr/src/linux-
headers-6.3.0-1-common/scripts/Makefile.modpost:136:
/var/lib/dkms/it87/20230126/build/Module.symvers] Error 1
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2002: modpost]
Error 2
make: *** [Makefile:73: modules] Error 2
After changing linux-kbuild to amd64 the module builds correctly again:
Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.3.0-1-amd64 TARGET=6.3.0-1-amd64...
Signing module /var/lib/dkms/it87/20230126/build/it87.ko
Cleaning build area...
it87.ko:
Running module version sanity check.
- Original module
- Installation
- Installing to /lib/modules/6.3.0-1-amd64/updates/dkms/
depmod...
Sign command: /usr/lib/linux-kbuild-6.3/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
A Debian user in #debian-apt suggested I try pinning the i386 architecture to
400 but this had no effect on aptitude's resolver choices. The concern here
being in what ways could aptitude break a Debian install if it decides to
install foreign packages over native ones?
-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude
aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
apt version 6.0.0
NCurses version 6.3
libsigc++ version: 2.10.8
Gtk+ support disabled.
Qt support disabled.
Current library versions:
NCurses version: ncurses 6.4.20221231
cwidget version: 0.5.18
Apt version: 6.0.0
aptitude linkage:
linux-vdso.so.1 (0x7ffd3e8d5000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
(0x7f9b85c05000)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6
(0x7f9b85bcb000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6
(0x7f9b85b98000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0
(0x7f9b8623f000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4
(0x7f9b85aa6000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0
(0x7f9b85947000)
libboost_iostreams.so.1.74.0 =>
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f9b86225000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30
(0x7f9b8560)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x7f9b8622)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
(0x7f9b8520)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f9b85868000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x7f9b85844000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9b8501f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f9b855e1000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
(0x7f9b85831000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f9b855b2000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f9b8558c000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f9b854d)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1
Bug#1032912: cinnamon: Taking a screenshot of a full screen window crashes cinnamon
Hi, I tested the packages you provided and can confirm the bug is no longer occurring. Thank you for the quick response. Konomi
Bug#1032912: cinnamon: Taking a screenshot of a full screen window crashes cinnamon
Package: cinnamon Version: 5.6.7-1 Severity: important X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, Taking a screenshot of a full screen window will crash the desktop. But only when using the "Take a screenshot of a window" shortcut. I found a possibly related bug report upstream [1]. But I'm unsure if it's the same bug. [1] https://github.com/linuxmint/cinnamon/issues/11500 Steps to reproduce: 1. Run a full screen program such as a media player playing video or a game. SuperTuxKart works well for example. 2. Press Alt+Print Screen (Take a screenshot of a window). 3. Cinnamon will crash and ask you to restart it. Systemd journal: Mar 14 09:33:29 debian kernel: pool-cinnamon[3285]: segfault at 1c ip 7f9a58610a99 sp 7f9a297f99d0 error 4 in libcairo.so.2.11600.0[7f9a5856d000+cf000] likely on CPU 2 (core 0, socket 0) Mar 14 09:33:29 debian kernel: Code: ef e8 5b d0 f5 ff bf 0b 00 00 00 e8 41 2d f7 ff 89 03 eb e8 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 55 53 48 89 fb 48 83 ec 18 <8b> 6f 1c 64 48 8b 04 25 28 00 00 00 48 89 44 24 08 31 c0 85 ed 75 ~/.xsession-errors: ** Message: 09:32:31.770: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11. Exception in thread Thread-2 (wait_for_process): Traceback (most recent call last): File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner self.run() File "/usr/lib/python3.11/threading.py", line 975, in run self._target(*self._args, **self._kwargs) File "/usr/bin/cinnamon-launcher", line 88, in wait_for_process os.execvp(FALLBACK_COMMAND, (FALLBACK_COMMAND,) + FALLBACK_ARGS) File "", line 574, in execvp File "", line 616, in _execvpe File "", line 607, in _execvpe FileNotFoundError: [Errno 2] No such file or directory None: no process found -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cinnamon depends on: ii cinnamon-common 5.6.7-1 ii cinnamon-control-center 5.6.1-1 ii cinnamon-desktop-data5.6.1-1 ii cinnamon-screensaver 5.6.3-1 ii cinnamon-session 5.6.0-1 ii cinnamon-settings-daemon 5.6.1-1 ii cjs 5.6.0-1 ii cups-pk-helper 0.2.6-1+b1 ii dbus 1.14.6-1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gir1.2-accountsservice-1.0 22.08.8-6 ii gir1.2-caribou-1.0 0.4.21-8 ii gir1.2-cmenu-3.0 5.6.0-1 ii gir1.2-cvc-1.0 5.6.1-1 ii gir1.2-ecal-2.0 3.46.4-1 ii gir1.2-edataserver-1.2 3.46.4-1 ii gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1 ii gir1.2-gkbd-3.0 3.28.1-1 ii gir1.2-glib-2.0 1.74.0-3 ii gir1.2-gnomedesktop-3.0 43.2-2 ii gir1.2-goa-1.0 3.46.0-1 ii gir1.2-gsound-1.01.0.3-2 ii gir1.2-gtk-3.0 3.24.36-4 ii gir1.2-ical-3.0 3.0.16-1+b1 ii gir1.2-keybinder-3.0 0.3.2-1.1 ii gir1.2-nemo-3.0 5.6.3-1 ii gir1.2-nm-1.01.42.0-1 ii gir1.2-nma-1.0 1.10.6-1 ii gir1.2-notify-0.70.8.1-1 ii gir1.2-pango-1.0 1.50.12+ds-1 ii gir1.2-polkit-1.0122-3 ii gir1.2-soup-2.4 2.74.3-1 ii gir1.2-timezonemap-1.0 0.4.6-3 ii gir1.2-upowerglib-1.00.99.20-2 ii gir1.2-xapp-1.0 2.4.2-3 ii gkbd-capplet 3.28.1-1 ii gnome-backgrounds43.1-1 ii gnome-themes-extra 3.28-2 ii gsettings-desktop-schemas43.0-1 ii iso-flags-png-320x2401.0.2-2 ii libatk-bridge2.0-0 2.46.0-5 ii libatk1.0-0 2.46.0-5 ii libc62.36-8 ii libcairo21.16.0-7 ii libcinnamon-desktop4 5.6.1-1 ii libcinnamon-menu-3-0 5.6.0-1 ii libcjs0
Bug#1031909: python3-tk: bytecode not removed on upgrade
Package: python3-tk Version: 3.11.2-2 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, The python3-tk package does not remove bytecode on upgrade: Unpacking python3-tk:amd64 (3.11.2-2) over (3.10.8-1) ... dpkg: warning: unable to delete old directory '/usr/lib/python3.10/tkinter': Directory not empty dpkg: warning: unable to delete old directory '/usr/lib/python3.10': Directory not empty On a side note this bug is the same as #1017445 which is the same as #960653 which is the same as #918098. Why does this keep happening? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-tk depends on: ii blt 2.5.3+dfsg-4.1 ii libc6 2.36-8 ii libtcl8.6 8.6.13+dfsg-2 ii libtk8.6 8.6.13-2 ii python3 3.11.1-3 ii tk8.6-blt2.5 2.5.3+dfsg-4.1 python3-tk recommends no packages. Versions of packages python3-tk suggests: pn python3-tk-dbg pn tix -- no debconf information
Bug#1031600: geany: Geany crashes when I press Ctrl+Shift+V
Package: geany Version: 1.38-1+b1 Severity: important Tags: upstream X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, Pressing Ctrl+Shift+V crashes Geany. This has been reported upstream [1] and there is also a patch available [2]. As this causes users to lose work I've marked this as important. It would be nice to have this patched before Bookworm releases. There is currently a work around for users reading this report. Find the `keybindings.conf` file which is usually located in `~/.config/geany/` find the line that has `menu_paste=v` and directly under that line add `menu_paste=v`. Thank you for your time. [1] https://github.com/geany/geany/issues/2813 [2] https://github.com/geany/geany/pull/3091 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages geany depends on: ii geany-common 1.38-1 ii libatk1.0-0 2.46.0-5 ii libc62.36-8 ii libcairo21.16.0-7 ii libgcc-s112.2.0-14 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.5-1 ii libgtk-3-0 3.24.36-3 ii libpango-1.0-0 1.50.12+ds-1 ii libpangocairo-1.0-0 1.50.12+ds-1 ii libstdc++6 12.2.0-14 Versions of packages geany recommends: ii sensible-utils 0.0.17+nmu1 Versions of packages geany suggests: pn doc-base ii libvte9 1:0.28.2-6+b1 -- no debconf information
Bug#1028643: fontconfig: 2.14.1-3 greatly changes font rendering
As I kind of rushed the fix for this here is what I am sure should be the most correct way to fix this issue. If you want to change the fonts system wide create /etc/fonts/local.conf for your user only ~/.config/fontconfig/fonts.conf and put the following in the file: serif DejaVu Serif sans-serif DejaVu Sans monospace DejaVu Sans Mono The /etc/fonts/conf.d/50-prefer-dejavu.conf file can be removed as that's not where the config should be located (best practice as far as I know is the paths in this post). Sorry for the noise and I hope this helps everyone affected.
Bug#1028643: fontconfig
On Sun, 22 Jan 2023 13:03:00 - t...@envs.net wrote: > i can't downgrade - this is the only version available > > this fixed the color artifacts for me: > > remove /etc/fonts/conf.d/10-sub-pixel-rgb.conf This sounds like a different issue as far as I know the font change shouldn't affect subpixel font rendering. It may be that your screen isn't an LCD or wants a different order to RGB. I'd consider filing a different bug report.
Bug#919348: xfce4-screensaver: Accidental upload to unstable while fixing bug #919151
Could this bug be closed and allow xfce4-screensaver to flow to testing/stable? I know there are concerns about the stability but the 4.16 release has been out for 2 years. And as far as I know light-locker is still recommended over xfce4-screensaver so this package would not be a default for everybody. But closing this bug would allow for those of us who wish to use the package to do so without resorting to more complicated means of doing so. Please consider closing the bug. Thank you.
Bug#1014369: Regression: incorrect icon used in 0.8.0
I'm also waiting for 0.8.1 to enter unstable so I can test if this bug is resolved. It would be nice to have an update.
Bug#1028643: fontconfig: 2.14.1-3 greatly changes font rendering
This is the upstream change in fontconfig that led to this bug report [1]. I can't find any reason why Noto is now preferred over DejaVu in the change or issues. [1] https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/ad70d785974992c569b30108923875e5b5e9dc5e
Bug#1028643: fontconfig: 2.14.1-3 greatly changes font rendering
Just to add as an XFCE user this change greatly impacted the look of my desktop. So while this may be fine for GNOME users, people with other DEs could be affected by the change. I also didn't quite get the file correct to revert the change in my previous email so here's the updated version, as far as I know this should work correctly. monospace DejaVu Sans Mono sans DejaVu Sans sans-serif DejaVu Sans serif DejaVu Serif
Bug#1028643: fontconfig: 2.14.1-3 greatly changes font rendering
For anyone who is not super happy with this change from DejaVu to Noto I just did this to revert it: 1. Create a file called /etc/fonts/conf.d/50-prefer-dejavu.conf 2. Add the following: monospace DejaVu Sans Mono sans DejaVu Sans Book serif DejaVu Serif Book 3. Save the file and run fc-cache -r I'm not super familiar with how fontconfig works so if anyone who is could look over this and suggest a better method it would be greatly appreciated. But this seems to work if you want the old behaviour back.
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
I just did another round of updates and rebooted and could not reproduce the bug so I leave it to more experienced users to determine what should be done.
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
> I wonder if Konomi can reproduce this? I haven't been able to reproduce it so far, but I haven't rebooted my computer yet. I still have the video of the error though so it's definitely an issue. > Is this possible to reassign this report to console-setup? I think this would be a good idea to investigate further, who knows if this bug will cause actual problems later.
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
> There is no occurrence of ‘CCHAR’ or ‘UNUMBER’ in the source, so I > suspect this might be orthogonal to src:cryptsetup. You're right I'm not sure what's going on. I allowed the packages to update again and now there's no error, it just seems to have gone away on its own. I really hate when that happens. I'll open another bug report with no specific package if I see the error again. Sorry for the false report.
Bug#1027068: cryptsetup: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS
Package: cryptsetup Version: 2:2.6.0-2 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After doing the following updates: [UPGRADE] cryptsetup:amd64 2:2.6.0-1 -> 2:2.6.0-2 [UPGRADE] cryptsetup-bin:amd64 2:2.6.0-1 -> 2:2.6.0-2 [UPGRADE] cryptsetup-initramfs:amd64 2:2.6.0-1 -> 2:2.6.0-2 [UPGRADE] libcryptsetup12:amd64 2:2.6.0-1 -> 2:2.6.0-2 I see the following error when my system starts just after the GRUB splash screen: syntax error, unexpected ERROR, expecting CCHAR or UNUMBER or AS Please note that it's hard to read this error and I only could take a video of it so I'm not sure of the exact message. After downgrading the packages the error message no longer appears. -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup depends on: ii cryptsetup-bin 2:2.6.0-1 ii debconf [debconf-2.0] 1.5.80 ii dmsetup2:1.02.185-2 ii libc6 2.36-7 cryptsetup recommends no packages. Versions of packages cryptsetup suggests: pn cryptsetup-initramfs ii dosfstools 4.2-1 pn keyutils ii liblocale-gettext-perl 1.07-5 -- debconf information: cryptsetup/prerm_active_mappings: true
Bug#1025477: grub2: Regression when updating from 2.06-5 to 2.06-6 breaks GRUB_GFXMODE
Could someone with access please rename this bug to "grub2: Regression when updating from 2.06-5 to 2.06-6 breaks GRUB_GFXMODE" without the line breaks. I am unable to do so because gmail in plain text mode inserts line breaks and I can't figure out how to turn it off which causes control to return an error message. Thank you.
Bug#1025477: grub2: Regression when updating from grub2 2.06-5 to 2.06-5 breaks GRUB_GFXMODE
Source: grub2 Version: 2.06-6 Severity: important X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, I'm reporting against the source package because I am unsure which specific package of grub2 has caused this bug. After updating to version 2.06-6 my GRUB_GFXMODE line in /etc/default/grub no longer works. I get the following two errors displayed when grub2 first starts: Welcome to GRUB! error: no server is specified. error: no suitable video mode found. After this I am greeted with an extremely low resolution grub screen but the computer is still able to boot. Downgrading the following packages fixes the issue: Start-Date: 2022-12-05 22:52:19 Commandline: apt install ./grub2-common_2.06-5_amd64.deb ./grub- common_2.06-5_amd64.deb ./grub-efi_2.06-5_amd64.deb ./grub-efi- amd64_2.06-5_amd64.deb ./grub-efi-amd64-bin_2.06-5_amd64.deb ./grub-pc- bin_2.06-5_amd64.deb Requested-By: debian (1000) Downgrade: grub-pc-bin:amd64 (2.06-6, 2.06-5), grub-efi-amd64:amd64 (2.06-6, 2.06-5), grub-efi-amd64-bin:amd64 (2.06-6, 2.06-5), grub2-common:amd64 (2.06-6, 2.06-5), grub-common:amd64 (2.06-6, 2.06-5), grub-efi:amd64 (2.06-6, 2.06-5) End-Date: 2022-12-05 22:52:26 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1014369: Regression: incorrect icon used in 0.8.0
Package: pasystray Version: 0.8.0-1 Severity: normal Tags: upstream X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating pasystray to 0.8.0 from 0.7.1 the icon displayed in the systray no longer respects the theme set by the user. I've reported this bug upstream [1]. [1] https://github.com/christophgysin/pasystray/issues/161 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pasystray depends on: ii adwaita-icon-theme 42.0-2 ii libavahi-client30.8-6 ii libavahi-common30.8-6 ii libavahi-glib1 0.8-6 ii libayatana-appindicator3-1 0.5.91-1 ii libc6 2.33-7 ii libglib2.0-02.72.3-1 ii libgtk-3-0 3.24.34-1 ii libnotify4 0.7.12-1 ii libpulse-mainloop-glib0 15.0+dfsg1-4+b1 ii libpulse0 15.0+dfsg1-4+b1 ii libx11-62:1.7.5-1 pasystray recommends no packages. Versions of packages pasystray suggests: pn paman ii paprefs 1.2-1 ii pavucontrol 5.0-2 pn pavumeter ii pulseaudio-module-zeroconf 15.0+dfsg1-4+b1 -- no debconf information
Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory
Package: initramfs-tools Version: 0.141 Severity: minor X-Debbugs-Cc: konomikit...@gmail.com When update-initramfs runs I receive the following message: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 56M Jul 4 14:01 /boot/initrd.img-5.16.0-6-amd64 -rw-r--r-- 1 root root 58M Jul 4 14:01 /boot/initrd.img-5.17.0-3-amd64 -rw-r--r-- 1 root root 58M Jul 4 14:00 /boot/initrd.img-5.18.0-1-amd64 -rw-r--r-- 1 root root 58M Jul 4 14:56 /boot/initrd.img-5.18.0-2-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.18.0-2-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro quiet systemd.show_status=true -- /proc/filesystems btrfs fuseblk vfat ext3 ext2 ext4 -- lsmod Module Size Used by ext4 946176 1 mbcache16384 1 ext4 jbd2 163840 1 ext4 dm_crypt 61440 1 dm_mod176128 3 dm_crypt tcp_diag 16384 0 inet_diag 24576 1 tcp_diag ctr16384 3 ccm20480 9 vboxnetadp 28672 0 vboxnetflt 32768 0 vboxdrv 532480 2 vboxnetadp,vboxnetflt rfcomm 90112 16 ip6t_REJECT16384 1 nf_reject_ipv6 20480 1 ip6t_REJECT xt_hl 16384 22 ip6_tables 36864 52 ip6t_rt20480 3 ipt_REJECT 16384 1 nf_reject_ipv4 16384 1 ipt_REJECT xt_LOG 20480 14 qrtr 45056 4 cpufreq_userspace 20480 0 cpufreq_powersave 20480 0 cpufreq_ondemand 16384 0 cpufreq_conservative16384 0 nf_log_syslog 20480 14 cmac 16384 3 nft_limit 16384 17 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 28672 2 zstd 16384 12 zram 40960 2 zsmalloc 32768 1 zram xt_limit 16384 0 xt_addrtype16384 5 nft_chain_nat 16384 2 xt_nat 16384 4 nf_nat 57344 2 xt_nat,nft_chain_nat xt_conntrack 16384 20 nf_conntrack 176128 3 xt_conntrack,nf_nat,xt_nat nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack xt_tcpudp 20480 0 nft_compat 20480 130 nf_tables 278528 759 nft_compat,nft_chain_nat,nft_limit binfmt_misc24576 1 nfnetlink 20480 2 nft_compat,nf_tables nls_ascii 16384 1 nls_cp437 20480 1 vfat 20480 1 fat86016 1 vfat btusb 65536 0 btrtl 28672 1 btusb btbcm 24576 1 btusb btintel45056 1 btusb iwlmvm368640 0 btmtk 16384 1 btusb intel_rapl_msr 20480 0 intel_rapl_common 28672 1 intel_rapl_msr bluetooth 876544 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm mac80211 1085440 1 iwlmvm edac_mce_amd 36864 0 snd_hda_codec_realtek 167936 1 jitterentropy_rng 16384 1 snd_hda_codec_generic98304 1 snd_hda_codec_realtek ledtrig_audio 16384 1 snd_hda_codec_generic sha512_ssse3 49152 1 snd_hda_codec_hdmi 73728 1 sha512_generic 16384 1 sha512_ssse3 kvm_amd 151552 0 snd_hda_intel 57344 5 snd_usb_audio 356352 4 drbg 40960 1 libarc416384 1 mac80211 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib45056 1 snd_usb_audio snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg ansi_cprng 16384 0 kvm 1060864 1 kvm_amd iwlwifi 344064 1 iwlmvm snd_rawmidi45056 1 snd_usbmidi_lib snd_hda_codec 176128 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_seq_device 16384 1 snd_rawmidi snd_hda_core 110592 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek irqbypass 16384 1 kvm mc 65536 1 snd_usb_audio snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec ecdh_generic 16384 2 bluetooth joydev 28672 0 ecc40960 1 ecdh_generic rapl 20480 0 snd_pcm 147456 8 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core crc16 16384 2 bluetooth,ext4 cfg80211 1056768 3 iwlmvm,iwlwifi,mac80211 snd_timer 45056 1 snd_pcm snd 110592 27
Bug#1013907: smartmontools: Warning about disconnected USB Hard Drive when USB Flash Drive uses the same drive letter
Package: smartmontools Version: 7.3-1 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, I get the following error for a drive I previous had connected to my computer: ``` This message was generated by the smartd daemon running on: host name: debian DNS domain: workgroup The following warning/error was logged by the smartd daemon: Device: /dev/sdb [SAT], Read SMART Self-Test Log Failed Device info: TOSHIBA MQ04UBB400, S/N:0, WWN:0-00-0, FW:JS000U, 4.00 TB For details see host's SYSLOG. ``` You can also use the smartctl utility for further investigation. The original message about this issue was sent at Sun Jun 26 15:29:02 2022 AEST Another message will be sent in 24 hours if the problem persists. ``` Checking the journal shows that the current drive is not a TOSHIBA MQ04UBB400 but is actually a TOSHIBA USB DRV: ``` Jun 27 16:55:44 debian kernel: scsi 9:0:0:0: Direct-Access TOSHIBA TOSHIBA USB DRV PMAP PQ: 0 ANSI: 4 Jun 27 16:55:44 debian kernel: sd 9:0:0:0: Attached scsi generic sg1 type 0 Jun 27 16:55:45 debian kernel: sd 9:0:0:0: [sdb] 7570752 512-byte logical blocks: (3.88 GB/3.61 GiB) Jun 27 16:55:45 debian kernel: sd 9:0:0:0: [sdb] Write Protect is off Jun 27 16:55:45 debian kernel: sd 9:0:0:0: [sdb] Mode Sense: 23 00 00 00 Jun 27 16:55:45 debian kernel: sd 9:0:0:0: [sdb] No Caching mode page found Jun 27 16:55:45 debian kernel: sd 9:0:0:0: [sdb] Assuming drive cache: write through Jun 27 16:55:45 debian kernel: sdb: sdb1 sdb2 Jun 27 16:55:45 debian kernel: sd 9:0:0:0: [sdb] Attached SCSI removable disk ``` Here is the smartd portion of the log: ``` Jun 27 16:59:03 debian smartd[1069]: Device: /dev/sdb [SAT], reconnected ATA device Jun 27 16:59:03 debian smartd[1069]: Device: /dev/sdb [SAT], failed to read SMART Attribute Data Jun 27 16:59:03 debian smartd[1069]: Sending warning via /usr/share/smartmontools/smartd-runner to root ... Jun 27 16:59:03 debian smartd[1069]: Warning via /usr/share/smartmontools/smartd-runner to root: successful Jun 27 16:59:03 debian smartd[1069]: Device: /dev/sdb [SAT], Read SMART Self Test Log Failed Jun 27 16:59:03 debian smartd[1069]: Sending warning via /usr/share/smartmontools/smartd-runner to root ... Jun 27 16:59:03 debian smartd[1069]: Warning via /usr/share/smartmontools/smartd-runner to root: successful Jun 27 16:59:03 debian smartd[1069]: Device: /dev/sdb [SAT], Read Summary SMART Error Log failed Jun 27 16:59:03 debian smartd[1069]: Sending warning via /usr/share/smartmontools/smartd-runner to root ... Jun 27 16:59:03 debian smartd[1069]: Warning via /usr/share/smartmontools/smartd-runner to root: successful ``` -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smartmontools depends on: ii debianutils 5.7-0.2 ii libc62.33-7 ii libcap-ng0 0.8.3-1 ii libgcc-s112.1.0-4 ii libselinux1 3.4-1 ii libstdc++6 12.1.0-4 ii libsystemd0 251.2-6 ii lsb-base 11.2 smartmontools recommends no packages. Versions of packages smartmontools suggests: ii bsd-mailx [mailx] 8.1.2-0.20220412cvs-1 ii curl 7.83.1-2 ii gpg2.2.35-2 ii gsmartcontrol 1.1.4-1 ii smart-notifier 0.28-8 ii wget 1.21.3-1+b2 -- no debconf information
Bug#1012641: schroot.service: Failed at step EXEC spawning /usr/share/schroot/bin/schroot-init: Is a directory
Package: schroot Version: 1.6.10-15 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com After upgrading schroot the the schroot.service file fails to start: $ sudo journalctl --no-pager --boot=0 --unit=schroot Jun 11 11:34:24 debian systemd[1]: Starting Recover schroot sessions... Jun 11 11:34:24 debian systemd[961]: schroot.service: Failed to locate executable /usr/share/schroot/bin/schroot-init: Is a directory Jun 11 11:34:24 debian systemd[961]: schroot.service: Failed at step EXEC spawning /usr/share/schroot/bin/schroot-init: Is a directory Jun 11 11:34:24 debian systemd[1]: schroot.service: Main process exited, code=exited, status=203/EXEC Jun 11 11:34:24 debian systemd[1]: schroot.service: Failed with result 'exit- code'. Jun 11 11:34:24 debian systemd[1]: Failed to start Recover schroot sessions. Here's the aptitude log for upgrades: Aptitude 0.8.13: log report Sat, Jun 11 2022 11:26:46 +1000 IMPORTANT: this log only lists intended actions; actions which fail due to dpkg problems may not be completed. Will install 18 packages, and remove 0 packages. 96.3 kB of disk space will be freed [INSTALL, DEPENDENCIES] libsystemd-shared:amd64 251.2-4 [UPGRADE] grub-common:amd64 2.06-2 -> 2.06-3 [UPGRADE] grub-pc:amd64 2.06-2 -> 2.06-3 [UPGRADE] grub-pc-bin:amd64 2.06-2 -> 2.06-3 [UPGRADE] grub2-common:amd64 2.06-2 -> 2.06-3 [UPGRADE] libnss-systemd:amd64 251.2-2 -> 251.2-4 [UPGRADE] libpam-systemd:amd64 251.2-2 -> 251.2-4 [UPGRADE] libsystemd0:amd64 251.2-2 -> 251.2-4 [UPGRADE] libsystemd0:i386 251.2-2 -> 251.2-4 [UPGRADE] libudev1:amd64 251.2-2 -> 251.2-4 [UPGRADE] libudev1:i386 251.2-2 -> 251.2-4 [UPGRADE] schroot:amd64 1.6.10-13 -> 1.6.10-15 [UPGRADE] schroot-common:amd64 1.6.10-13 -> 1.6.10-15 [UPGRADE] systemd:amd64 251.2-2 -> 251.2-4 [UPGRADE] systemd-journal-remote:amd64 251.2-2 -> 251.2-4 [UPGRADE] systemd-sysv:amd64 251.2-2 -> 251.2-4 [UPGRADE] systemd-timesyncd:amd64 251.2-2 -> 251.2-4 [UPGRADE] udev:amd64 251.2-2 -> 251.2-4 Log complete. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages schroot depends on: ii libboost-filesystem1.74.0 1.74.0-16 ii libboost-iostreams1.74.01.74.0-16 ii libboost-program-options1.74.0 1.74.0-16 ii libc6 2.33-7 ii libgcc-s1 12.1.0-2 ii libpam0g1.4.0-13 ii libstdc++6 12.1.0-2 ii libuuid12.38-4 ii lsb-base11.2 ii schroot-common 1.6.10-15 schroot recommends no packages. Versions of packages schroot suggests: pn aufs-tools | unionfs-fuse ii btrfs-progs5.18.1-1 ii bzip2 1.0.8-5 ii debootstrap1.0.126+nmu1 pn lvm2 pn qemu-user-static ii xz-utils 5.2.5-2.1 pn zfsutils-linux ii zstd 1.5.2+dfsg-1 -- no debconf information
Bug#1009198: fonts-droid-fallback: English text broken when running programs via wine that use both Japanese and Latin characters
Package: fonts-droid-fallback Version: 1:6.0.1r16-1.1 Followup-For: Bug #1009198 X-Debbugs-Cc: konomikit...@gmail.com Please see attachments mentioned in the original bug report. -- Package-specific info: 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 +++-==-=--= ii fontconfig 2.13.1-4.4amd64generic font configuration library - support binaries ii libfreetype6:amd64 2.11.1+dfsg-1 amd64FreeType 2 font engine, shared library files ii libfreetype6:i386 2.11.1+dfsg-1 i386 FreeType 2 font engine, shared library files ii libxft2:amd64 2.3.4-1 amd64FreeType-based font drawing library for X -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fonts-droid-fallback depends on: ii dpkg 1.21.7 Versions of packages fonts-droid-fallback recommends: ii fonts-noto-mono 20201225-1 Versions of packages fonts-droid-fallback suggests: ii fonts-noto 20201225-1 -- no debconf information
Bug#1009198: fonts-droid-fallback: English text broken when running programs via wine that use both Japanese and Latin characters
Package: fonts-droid-fallback Version: 1:6.0.1r16-1.1 Severity: normal Tags: upstream X-Debbugs-Cc: konomikit...@gmail.com Currently if you have fonts-droid-fallback installed and run a program via wine that uses both Japanese characters and Latin characters you will get tofu characters for English (squares) [Broken Characters.png]. Removing the fonts-droid-fallback package fixes this problem [Working Characters.png]. This seems to occur because the font provided in fonts-droid-fallback (DroidSansFallbackFull.ttf) lacks Latin characters. This can easily be observed with Font Viewer by selecting Lorem Ipsum [Lorem Ipsum.png]. This problem only affects wine and may be due to wine partially supporting Uniscribe [1]. There's a few ways to go about fixing this issue though. First of all Google has abandoned the droid font [2] so it could be argued that the font should be removed from Debian. Another option is to go back to older versions of the font where Latin characters were present at some point in time Google removed a significant amount of characters from the droid font. I believe this change occurred in commit 034b20c102ee2e7ec1da09e2b080f35be4a5cf54 [3]. So going back to commit 0abd8a79cc19658305dae81e3eca32b45f268f96 [4] would restore many of the missing characters. Another option would be to change all packages recommending fonts-droid-fallback to suggesting it instead so it's not installed by default. Ultimately though these are just suggestions because I am unable to figure out why wine cannot handle DroidSansFallbackFull.ttf's lack of Latin characters. [1] https://wiki.winehq.org/Uniscribe [2] https://github.com/google/fonts/issues/1223 [3] https://android.googlesource.com/platform/frameworks/base/+/034b20c102ee2e7ec1da09e2b080f35be4a5cf54 [4] https://android.googlesource.com/platform/frameworks/base/+/0abd8a79cc19658305dae81e3eca32b45f268f96 -- Package-specific info: 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 +++-==-=--= ii fontconfig 2.13.1-4.4amd64generic font configuration library - support binaries ii libfreetype6:amd64 2.11.1+dfsg-1 amd64FreeType 2 font engine, shared library files ii libfreetype6:i386 2.11.1+dfsg-1 i386 FreeType 2 font engine, shared library files ii libxft2:amd64 2.3.4-1 amd64FreeType-based font drawing library for X -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fonts-droid-fallback depends on: ii dpkg 1.21.7 Versions of packages fonts-droid-fallback recommends: ii fonts-noto-mono 20201225-1 Versions of packages fonts-droid-fallback suggests: ii fonts-noto 20201225-1 -- no debconf information
Bug#982373: SyntaxWarning: "is" with a literal. Did you mean "=="?
Package: lightdm-gtk-greeter-settings Version: 1.2.2-3 Severity: minor X-Debbugs-Cc: konomikit...@gmail.com The following warning is observed when installing this package: Setting up lightdm-gtk-greeter-settings (1.2.2-3) ... /usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/helpers.py:281: SyntaxWarning: "is" with a literal. Did you mean "=="? if obj._dict[keys[i]] is (): Processing triggers for mailcap (3.68) ... -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lightdm-gtk-greeter-settings depends on: ii gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1 ii gir1.2-glib-2.0 1.66.1-1+b1 ii gir1.2-gtk-3.03.24.24-1 ii gir1.2-pango-1.0 1.46.2-3 ii lightdm-gtk-greeter 2.0.8-2 ii python3 3.9.1-1 ii python3-gi3.38.0-2 Versions of packages lightdm-gtk-greeter-settings recommends: ii policykit-1 0.105-30 lightdm-gtk-greeter-settings suggests no packages.
Bug#982150: comicthumb: NameError: name '_' is not defined
Package: mcomix
Version: 1.2.1mcomix3+git20200206-1
Severity: important
Tags: upstream
X-Debbugs-Cc: konomikit...@gmail.com
Running comicthumb results in the following error:
Traceback (most recent call last):
File "/usr/bin/comicthumb", line 24, in
from mcomix import thumbnail_tools
File "/usr/share/mcomix/mcomix/thumbnail_tools.py", line 16, in
from mcomix import archive_extractor
File "/usr/share/mcomix/mcomix/archive_extractor.py", line 7, in
from mcomix import archive_tools
File "/usr/share/mcomix/mcomix/archive_tools.py", line 14, in
from mcomix.archive import (
File "/usr/share/mcomix/mcomix/archive/__init__.py", line 5, in
from mcomix import main
File "/usr/share/mcomix/mcomix/main.py", line 14, in
from mcomix import event
File "/usr/share/mcomix/mcomix/event.py", line 10, in
from mcomix import keybindings
File "/usr/share/mcomix/mcomix/keybindings.py", line 36, in
from mcomix import keybindings_map
File "/usr/share/mcomix/mcomix/keybindings_map.py", line 5, in
'previous_page': {'title': _('Previous page'),
NameError: name '_' is not defined
Upstream bug report: https://github.com/multiSnow/mcomix3/issues/107.
Upstream commit:
https://github.com/multiSnow/mcomix3/commit/c912046ffe30f85513614775bded924546010c9c
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-3-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mcomix depends on:
ii gir1.2-gtk-3.03.24.24-1
ii python3 3.9.1-1
ii python3-cairo 1.16.2-4+b2
ii python3-gi3.38.0-2
ii python3-gi-cairo 3.38.0-2
ii python3-pil 8.1.0-1
Versions of packages mcomix recommends:
ii python3-chardet 4.0.0-1
Versions of packages mcomix suggests:
ii mupdf-tools1.17.0+ds1-1.2
ii p7zip 16.02+dfsg-8
pn unrar | libunrar5
-- no debconf information
Bug#980473: ModuleNotFoundError: No module named 'Crypto'
Control: reassign -1 python3-potr 1.0.2-3 Reassigned because I typoed the package name. Output of apt policy python3-potr: python3-potr: Installed: 1.0.2-3 Candidate: 1.0.2-3 Version table: *** 1.0.2-3 500 500 https://deb.debian.org/debian unstable/main amd64 Packages 500 https://deb.debian.org/debian unstable/main i386 Packages 100 /var/lib/dpkg/status
Bug#980473: ModuleNotFoundError: No module named 'Crypto'
Package: python3-otr Version: python3-potr Severity: grave Justification: renders package unusable X-Debbugs-Cc: konomikit...@gmail.com Trying to import potr throws the following error: $ python3 Python 3.9.1+ (default, Jan 10 2021, 15:42:50) [GCC 10.2.1 20201224] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import potr Traceback (most recent call last): File "/usr/lib/python3/dist-packages/potr/compatcrypto/pycrypto.py", line 19, in import Crypto ModuleNotFoundError: No module named 'Crypto' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/potr/__init__.py", line 21, in from potr import context File "/usr/lib/python3/dist-packages/potr/context.py", line 43, in from potr import crypt File "/usr/lib/python3/dist-packages/potr/crypt.py", line 25, in from potr.compatcrypto import SHA256, SHA1, SHA1HMAC, SHA256HMAC, \ File "/usr/lib/python3/dist-packages/potr/compatcrypto/__init__.py", line 21, in from potr.compatcrypto.pycrypto import * File "/usr/lib/python3/dist-packages/potr/compatcrypto/pycrypto.py", line 21, in import crypto as Crypto ModuleNotFoundError: No module named 'crypto' >>> -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#975726: firmware-iwlwifi: bluetooth hci0: firmware: failed to load intel/ibt-19-32-0.sfi (-2)
Package: firmware-iwlwifi Version: 20200918-1 Severity: important Recently I helped a user getting their Bluetooth working the missing firmware was: bluetooth hci0: firmware: failed to load intel/ibt-19-32-0.sfi (-2) Searching for this missing firmware provided no results we were able to download the sfi and ddc file from: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel After placing said files in /lib/firmware/intel/ the Bluetooth started working. Please include these firmware files in the firmware-iwlwifi.
Bug#968324: Provide /usr/bin/python
Package: python3 Version: 3.8.2-3 Followup-For: Bug #968324 Hi, For now if anyone wants an easy work around to this problem I just did: sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 1 Hopefully that helps people getting things working until this issue is resolved. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (120, 'stable'), (110, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-3-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3 depends on: ii libpython3-stdlib 3.8.2-3 ii python3-minimal3.8.2-3 ii python3.8 3.8.5-2 python3 recommends no packages. Versions of packages python3 suggests: pn python3-doc ii python3-tk3.8.5-1 ii python3-venv 3.8.2-3 -- no debconf information
Bug#966218: firmware: failed to load iwl-debug-yoyo.bin (-2)
Package: firmware-iwlwifi Version: 20200421-1 Severity: normal These two lines appear in the journal log indicating missing firmware, running `apt-file search iwl-debug-yoyo.bin` shows no matches for this firmware existing in any Debian package. Jul 22 23:21:52 debian kernel: iwlwifi :06:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) Jul 22 23:21:52 debian kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (120, 'stable'), (110, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.137 -- no debconf information
Bug#956576: kitty: Crashes when you drag an item over the terminal window
Package: kitty Version: 0.17.1-1 Severity: important Tags: upstream Dear Maintainer, Dragging and dropping items onto the kitty terminal causes it to crash. https://github.com/kovidgoyal/kitty/commit/759a15ccbbc1decfaec47b7968dd78f40f1ab66d There are also a significant amount of other issues fixed in the latest version. Please consider upgrading the package from 0.17.1 to 0.17.2. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (120, 'stable'), (110, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kitty depends on: ii kitty-terminfo 0.17.1-1 ii libc6 2.30-4 ii libdbus-1-3 1.12.16-2 ii libfontconfig1 2.13.1-2+b1 ii libfreetype62.10.1-2 ii libharfbuzz0b 2.6.4-1 ii libpng16-16 1.6.37-2 ii libpython3.83.8.2-1+b1 ii libwayland-client0 1.18.0-1 ii libx11-62:1.6.9-2 ii libx11-xcb1 2:1.6.9-2 ii libxkbcommon-x11-0 0.10.0-1 ii libxkbcommon0 0.10.0-1 ii python3 3.8.2-2 ii python3.8 3.8.2-1+b1 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages kitty recommends: ii kitty-doc 0.17.1-1 ii libcanberra0 0.30-7 Versions of packages kitty suggests: ii imagemagick 8:6.9.10.23+dfsg-2.1+b2 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+b2
Bug#940149: xfce4-settings: Sticky keys toast message when sticky keys are disabled
Package: xfce4-settings Version: 4.14.1-1 Severity: normal I randomly get a message now and then when using my keyboard that "Sticky keys are disabled". I believe this might be similar to bug #614939 but I do not use Sticky keys at all and I'm already on the fixed version mentioned in that bug report. Getting toast messages about a feature I don't even use is quite annoying, thanks. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (120, 'stable'), (110, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xfce4-settings depends on: ii libatk1.0-0 2.34.0-1 ii libc62.28-10 ii libcairo21.16.0-4 ii libcolord2 1.4.3-4 ii libexo-2-0 0.12.8-1 ii libfontconfig1 2.13.1-2+b1 ii libgarcon-1-00.6.4-1 ii libgarcon-common 0.6.4-1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.60.6-2 ii libgtk-3-0 3.24.11-1 ii libnotify4 0.7.8-1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0 1.42.4-7 ii libupower-glib3 0.99.11-1 ii libx11-6 2:1.6.7-1 ii libxcursor1 1:1.2.0-2 ii libxfce4ui-2-0 4.14.1-1+b1 ii libxfce4util74.14.0-1 ii libxfconf-0-34.14.1-1 ii libxi6 2:1.7.9-1 ii libxklavier165.4-4 ii libxrandr2 2:1.5.1-1 ii xfconf 4.14.1-1 Versions of packages xfce4-settings recommends: ii colord 1.4.3-4 ii x11-utils 7.7+4 pn xiccd xfce4-settings suggests no packages. -- no debconf information
Bug#939400: sddm: Auth: sddm-helper exited with 11
Package: sddm Version: 0.18.0-1 Severity: grave Tags: upstream Justification: renders package unusable Quoting the upstream bug report: "sddm-greeter needs execution rights at /var/lib/sddm/.cache/sddm-greeter/qmlcache/*.qmlc. krunner needs execution at /home/user/.cache/krunner/qmlcache/*.qmlc. It breaks when /var and /home partitions are mounted with noexec flag which is often used on hardened setups or Trusted Path Execution available on hardened linux kernels. As for now it could be fixed by disabling qml cache by setting QML_DISABLE_DISK_CACHE=1 environment variable. Is there a chance that qt will check permission rights first then quietly disable qmlcache per app instead of crashing? Alternatively it could create cachedir somewhere in /usr/lib/qt same as python3 have it's pycache dir." Upstream bug report: https://bugreports.qt.io/browse/QTBUG-58508 The work around of adding QML_DISABLE_DISK_CACHE=1 to /etc/enviroment got sddm working for me again. Without the work around sddm will start but show just a black screen, so I've marked this bug as grave since it completely breaks the package. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (120, 'stable'), (110, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/1 CPU core) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sddm depends on: ii adduser 3.118 ii debconf [debconf-2.0] 1.5.73 ii libc6 2.28-10 ii libgcc1 1:9.2.1-4 ii libpam0g1.3.1-5 ii libqt5core5a5.11.3+dfsg1-4 ii libqt5dbus5 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5network5 5.11.3+dfsg1-4 ii libqt5qml5 5.11.3-4 ii libqt5quick55.11.3-4 ii libstdc++6 9.2.1-4 ii libsystemd0 242-5 ii libxcb-xkb1 1.13.1-2 ii libxcb1 1.13.1-2 ii qml-module-qtquick2 5.11.3-4 ii x11-common 1:7.7+19 ii xserver-xorg [xserver] 1:7.7+19 Versions of packages sddm recommends: ii haveged1.9.4-2 ii libpam-systemd 242-5 ii sddm-theme-debian-elarun [sddm-theme] 0.18.0-1 ii sddm-theme-maui [sddm-theme] 0.18.0-1 Versions of packages sddm suggests: pn libpam-kwallet5 pn qtvirtualkeyboard-plugin -- debconf information: sddm/daemon_name: /usr/bin/sddm * shared/default-x-display-manager: sddm
Bug#925285: znc: Version 1.6.5-1+deb9u1 in stable still vulnerable
Source: znc Version: 1.6.5-1+deb9u1 Followup-For: Bug #925285 Hi, The stable version of znc (1.6.5-1+deb9u1) is still vulnerable to this attack. Please patch it also. -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (650, 'stable-updates'), (650, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-0.bpo.4-amd64 (SMP w/12 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#854043: smartmontools: update-smart-drivedb fails to update in stable
Package: smartmontools Version: 6.3+svn4002-2+b2 Severity: important Tags: patch Dear Maintainer, Note the following error output: $ sudo update-smart-drivedb /var/lib/smartmontools/drivedb/drivedb.h.error: rejected by /usr/sbin/smartctl, probably no longer compatible $ cat /var/lib/smartmontools/drivedb/drivedb.h.error 302 Found 302 Found The resource was found at https://sourceforge.net/p/smartmontools/code/HEAD/tree/branches/RELEASE_6_4_DRIVEDB/smartmontools/drivedb.h?format=raw;>https://sourceforge.net/p/smartmontools/code/HEAD/tree/branches/RELEASE_6_4_DRIVEDB/smartmontools/drivedb.h?format=raw; you should be redirected automatically. I have attached a patch to fix this, however the bug report has a comment mentioning that update-smart-drivedb is a security risk and has been dropped in releases above the current stable (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824149#10). I am therefor requesting the feature either be fixed in stable (whichever patch works best) or it be removed from the stable package for being a security risk. Konomi -- System Information: Debian Release: 8.7 APT prefers stable APT policy: (650, 'stable'), (550, 'testing'), (100, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smartmontools depends on: ii debianutils 4.4+b1 ii init-system-helpers 1.22 ii libc62.19-18+deb8u7 ii libcap-ng0 0.7.4-2 ii libgcc1 1:4.9.2-10 ii libselinux1 2.3-2 ii libstdc++6 4.9.2-10 ii lsb-base 4.1+Debian13+nmu1 Versions of packages smartmontools recommends: ii bsd-mailx [mailx] 8.1.2-0.20141216cvs-2 Versions of packages smartmontools suggests: ii gsmartcontrol 0.8.7-1.1 ii smart-notifier 0.28-5 -- Configuration Files: /etc/smartd.conf changed [not included] -- no debconf information --- a/update-smart-drivedb 2017-02-03 23:08:14.474323109 +1100 +++ b/update-smart-drivedb 2017-02-03 23:10:00.358327135 +1100 @@ -40,7 +40,7 @@ SMARTCTL="$sbindir/smartctl" # Download URL for sourceforge code browser -SRCEXPR='http://sourceforge.net/p/smartmontools/code/HEAD/tree/$location/smartmontools/drivedb.h?format=raw' +SRCEXPR='https://www.smartmontools.org/export/HEAD/$location/smartmontools/drivedb.h' # Parse options q="-q "
