Bug#1050863: r8168-dkms: module fails to compile against kernel 6.4.x
Package: r8168-dkms Version: 8.051.02-3 Severity: normal Tags: ftbfs X-Debbugs-Cc: de...@roosoft.ltd.uk Dear Maintainer, * What led up to the situation? Normal apt upgrade on Debian Testing * What exactly did you do (or not do) that was effective (or ineffective)? Nothing, dkms fails according to this log. DKMS make.log for r8168-8.051.02 for kernel 6.4.0-3-amd64 (x86_64) Wed 30 Aug 12:41:03 BST 2023 make: Entering directory '/usr/src/linux-headers-6.4.0-3-amd64' CC [M] /var/lib/dkms/r8168/8.051.02/build/r8168_n.o CC [M] /var/lib/dkms/r8168/8.051.02/build/r8168_asf.o CC [M] /var/lib/dkms/r8168/8.051.02/build/rtl_eeprom.o CC [M] /var/lib/dkms/r8168/8.051.02/build/rtltool.o /var/lib/dkms/r8168/8.051.02/build/r8168_n.c: In function ‘r8168_csum_workaround’: /var/lib/dkms/r8168/8.051.02/build/r8168_n.c:29212:24: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘skb_gso_reset’? [-Werror=implicit-function-declaration] 29212 | segs = skb_gso_segment(skb, features); |^~~ |skb_gso_reset /var/lib/dkms/r8168/8.051.02/build/r8168_n.c:29212:22: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint- conversion] 29212 | segs = skb_gso_segment(skb, features); | ^ cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.4.0-3-common/scripts/Makefile.build:257: /var/lib/dkms/r8168/8.051.02/build/r8168_n.o] Error 1 make: *** [/usr/src/linux-headers-6.4.0-3-common/Makefile:2057: /var/lib/dkms/r8168/8.051.02/build] Error 2 make: Leaving directory '/usr/src/linux-headers-6.4.0-3-amd64' * What was the outcome of this action? initrd fails to build and so new kernel updates cannot be installed. Could potentially leave the system without network access * What outcome did you expect instead? Clean module build. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'oldoldstable-updates'), (500, 'oldoldstable-debug'), (500, 'oldoldstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages r8168-dkms depends on: ii dkms 3.0.11-3 r8168-dkms recommends no packages. r8168-dkms suggests no packages. -- debconf-show failed
Bug#982850: duperemove: first run fails errror 13?
Package: duperemove Version: 0.11.2-3 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: de...@roosoft.ltd.uk Dear Maintainer, So running duperemove for the first run. duperemove -r -A -h --skip-zeroes --hashfile=/var/cache/duperemove-home-user /home/user/ At the end this happened. Total files: 2261918 Total extent hashes: 4666300 create_indexes()/45330: Database error 13 while creating database index: database or disk is full the folder is not full df -h /var Filesystem Size Used Avail Use% Mounted on /dev/mapper/pulseforn--vg-var 9.4G 7.4G 1.8G 81% /var ls -lah /var/cache/duperemove-home-user* -rw-r--r-- 1 root root 5.0G Feb 13 17:04 /var/cache/duperemove-home-user -rw-r--r-- 1 root root 4.6K Feb 13 17:03 /var/cache/duperemove-home-user- journal EDIT: For reference. Platform: Debian 10/Testing Kernel: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) x86_64 GNU/Linux duperemove v0.11.2 btrfs-progs v5.10.1 -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages duperemove depends on: ii libc6 2.31-9 ii libglib2.0-0 2.66.6-2 ii libsqlite3-0 3.34.1-1 duperemove recommends no packages. duperemove suggests no packages. -- debconf-show failed
Bug#910392: fontconfig: fc-cache regeneration fails unless EPOC time is set.
Package: fontconfig Version: 2.13.1-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? apt upgrade. Regenerating fonts breaks other configurations like libreoffice etc. * What exactly did you do (or not do) that was effective (or ineffective)? Following this ARCH thread (https://bugs.archlinux.org/task/59889) they recommended running fc-cache with "sudo SOURCE_DATE_EPOCH=$(date +%s)" which as explained from the fontconfig documentation "SOURCE_DATE_EPOCH is used to ensure fc-cache(1) generates files in a deterministic manner in order to support reproducible builds. When set to a numeric representation of UNIX timestamp, fontconfig will prefer this value over using the modification timestamps of the input files in order to identify which cache files require regeneration." * What was the outcome of this action? Patching /var/lib/dpkg/fontconfig.postinst with that command worked * What outcome did you expect instead? fc-cache: failed -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fontconfig depends on: ii fontconfig-config 2.13.1-1 ii libc6 2.27-6 ii libfontconfig1 2.13.1-1 ii libfreetype6 2.8.1-2 fontconfig recommends no packages. fontconfig suggests no packages. -- debconf-show failed
Bug#898991: deja-dup: Deja-Dup backups failing. Calls to dbus service timing out.
Package: deja-dup Version: 38.0-1 Severity: important Dear Maintainer, Launching a scheduled back up or one manually fails with the warning: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms) It has been 8 days since the last successful backup occurred. *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages deja-dup depends on: ii dconf-gsettings-backend [gsettings-backend] 0.28.0-2 ii duplicity0.7.17-1 ii libatk1.0-0 2.28.1-1 ii libc62.27-3 ii libglib2.0-0 2.56.1-2 ii libgoa-1.0-0b3.28.0-1 ii libgoa-backend-1.0-1 3.28.0-1 ii libgtk-3-0 3.22.29-3 ii libnautilus-extension1a 3.26.3.1-1 ii libpackagekit-glib2-18 1.1.10-1 ii libpango-1.0-0 1.42.0-1 ii libpeas-1.0-01.22.0-2 ii libsecret-1-00.18.6-1 Versions of packages deja-dup recommends: ii gvfs-backends 1.36.1-1 ii packagekit 1.1.10-1 ii policykit-10.105-20 Versions of packages deja-dup suggests: ii python-boto 2.44.0-1 ii python-cloudfiles 1.7.11-3 pn python-swiftclient -- debconf-show failed
Bug#871629: thunderbird UI unusable with many widgets not drawn
Package: thunderbird Version: 1:52.2.1-4+b1 Followup-For: Bug #871629 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages thunderbird depends on: ii debianutils 4.8.1.1 ii fontconfig2.12.3-0.2 ii libatk1.0-0 2.24.0-1 ii libc6 2.24-12 ii libcairo-gobject2 1.14.10-1 ii libcairo2 1.14.10-1 ii libdbus-1-3 1.11.16+really1.10.22-1 ii libdbus-glib-1-2 0.108-2 ii libevent-2.1-62.1.8-stable-4 ii libffi6 3.2.1-6 ii libfontconfig12.12.3-0.2 ii libfreetype6 2.8-0.2 ii libgcc1 1:7.1.0-10 ii libgdk-pixbuf2.0-02.36.5-2 ii libglib2.0-0 2.53.4-3 ii libgtk-3-03.22.17-1 ii libhunspell-1.6-0 1.6.1-2 ii libpango-1.0-01.40.6-1 ii libpangocairo-1.0-0 1.40.6-1 ii libpangoft2-1.0-0 1.40.6-1 ii libpixman-1-0 0.34.0-1 ii libstartup-notification0 0.12-4+b2 ii libstdc++67.1.0-10 ii libvpx4 1.6.1-3 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb-shm0 1.12-1 ii libxcb1 1.12-1 ii libxcomposite11:0.4.4-2 ii libxdamage1 1:1.1.4-2+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes31:5.0.3-1 ii libxrender1 1:0.9.10-1 ii libxt61:1.1.5-1 ii psmisc23.1-1 ii x11-utils 7.7+3+b1 ii zlib1g1:1.2.8.dfsg-5 Versions of packages thunderbird recommends: ii hunspell-en-gb [hunspell-dictionary] 1:5.2.5-1 ii hunspell-en-us [hunspell-dictionary] 20070829-7 ii lightning 1:52.2.1-4+b1 Versions of packages thunderbird suggests: pn apparmor ii fonts-lyx 2.2.3-1 ii libgssapi-krb5-2 1.15.1-2 Can confirm. Initial rending of windows appear blank but when rolling mouse over it artifacts begin to be drawn. Makes Thunderbird unsable. However when running the official Mozilla build http://download.cdn.mozilla.net/pub/thunderbird/releases/52.2.1/linux-x86_64/en- GB/thunderbird-52.2.1.tar.bz2 on the same system, no such errors occur. Suggest you compare the two builds and discover what has changed.
