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 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'
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#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 "
