Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more
This bug was silently fixed in sddm-theme-breeze 4:5.26.0-2 .
Bug#1039907: apt-cacher-cleanup.pl clears/removes all cached packages on trixie
Package: apt-cacher Version: 1.7.29 As far as I can see, calling /usr/share/apt-cacher/apt-cacher-cleanup.pl (e.g. after apt-get dist-upgrade which stores some packages to the cache) under debian testing/trixie seems to remove ALL package files in the cache /var/cache/apt-cacher/packages/ftp.xx.debian.org_debian, instead of only removing superseeded packages which are not in the index any more. I did not change my config (= nearly default), which used to operate on bookworm. Nevertheless, after bookworm got stable (and I stayed on testing), I manually cleared the cache by replacing /var/cache/apt-cacher with a vanilla version like it once was created by apt-get install apt-cacher . I hope that I have not overseen any (new?) configuration option... Thanks for apt-cacher! Chris
Bug#1039907: apt-cacher-cleanup.pl clears/removes all cached packages on trixie
Dear Mark, > Can you clarify exactly what you did here? Was that before or after the > dist-upgrade? I am ways on testing and never changes that. On Sat 10th of June ~20:00 (the day testing switched to trixie) I simply replaced the directory /var/cache/apt-cacher (with all content like cached packages files, indexes, headers, etc.) by /var/cache/apt-cacher/ ├── headers ├── import ├── packages └── private with headers, import, packages, private beeing completly empty subdirectories. Not less and not more. As it is the same structure as apt-get install apt-cacher inititally has created it was never a problem before and also should imho not be the culprit now. Calling /usr/share/apt-cacher/apt-cacher-cleanup.pl removes ALL downloaded/cached package files. I know about that at least a week ago. It can but needs not have to be related to testing's switch to trixie. The bug is fully reproducable (on my system) and also shows up today: $ apt-get update $ ls -la /var/cache/apt-cacher/packages/ftp.de.debian.org_debian total 60 drwxr-xr-x 2 www-data www-data 20480 2. Jul 10:52 . drwxr-xr-x 3 www-data www-data 32768 2. Jul 10:52 .. $ apt-get dist-upgrade $ ls -la /var/cache/apt-cacher/packages/ftp.de.debian.org_debian total 324 drwxr-xr-x 2 www-data www-data 20480 2. Jul 10:55 . drwxr-xr-x 3 www-data www-data 32768 2. Jul 10:52 .. -rw-r--r-- 1 www-data www-data 396 2. Jul 10:54 chromium%5f114.0.5735.198-1%5famd64.deb -rw-r--r-- 1 www-data www-data 401 2. Jul 10:54 chromium-common%5f114.0.5735.198-1%5famd64.deb -rw-r--r-- 1 www-data www-data 397 2. Jul 10:54 chromium-l10n%5f114.0.5735.198-1%5fall.deb -rw-r--r-- 1 www-data www-data 399 2. Jul 10:54 chromium-sandbox%5f114.0.5735.198-1%5famd64.deb -rw-r--r-- 1 www-data www-data 421 2. Jul 10:54 firmware-amd-graphics%5f20230515-2%5fall.deb -rw-r--r-- 1 www-data www-data 417 2. Jul 10:54 firmware-linux-nonfree%5f20230515-2%5fall.deb -rw-r--r-- 1 www-data www-data 421 2. Jul 10:54 firmware-misc-nonfree%5f20230515-2%5fall.deb -rw-r--r-- 1 www-data www-data 402 2. Jul 10:55 gstreamer1.0-gl%5f1.22.4-1%5famd64.deb -rw-r--r-- 1 www-data www-data 398 2. Jul 10:55 gstreamer1.0-pipewire%5f0.3.71-2+b2%5famd64.deb -rw-r--r-- 1 www-data www-data 412 2. Jul 10:55 gstreamer1.0-plugins-base%5f1.22.4-1%5famd64.deb -rw-r--r-- 1 www-data www-data 414 2. Jul 10:55 gstreamer1.0-plugins-good%5f1.22.4-1%5famd64.deb -rw-r--r-- 1 www-data www-data 409 2. Jul 10:55 gstreamer1.0-pulseaudio%5f1.22.4-1%5famd64.deb -rw-r--r-- 1 www-data www-data 401 2. Jul 10:55 gstreamer1.0-x%5f1.22.4-1%5famd64.deb -rw-r--r-- 1 www-data www-data 402 2. Jul 10:55 kf5-messagelib-data%5f22.12.3-2%5fall.deb -rw-r--r-- 1 www-data www-data 401 2. Jul 10:55 libcolorcorrect5%5f5.27.5-2+b1%5famd64.deb -rw-r--r-- 1 www-data www-data 382 2. Jul 10:55 libexecs0%5f1.3-3%5famd64.deb -rw-r--r-- 1 www-data www-data 383 2. Jul 10:55 libflac++10%5f1.4.3+ds-1%5famd64.deb -rw-r--r-- 1 www-data www-data 383 2. Jul 10:54 libflac12%5f1.4.3+ds-1%5famd64.deb -rw-r--r-- 1 www-data www-data 377 2. Jul 10:55 libgps30%5f3.25-1%5famd64.deb -rw-r--r-- 1 www-data www-data 407 2. Jul 10:55 libgstreamer-gl1.0-0%5f1.22.4-1%5famd64.deb -rw-r--r-- 1 www-data www-data 417 2. Jul 10:55 libgstreamer-plugins-base1.0-0%5f1.22.4-1%5famd64.deb -rw-r--r-- 1 www-data www-data 409 2. Jul 10:55 libkf5messagecomposer5abi1%5f22.12.3-2%5famd64.deb -rw-r--r-- 1 www-data www-data 404 2. Jul 10:55 libkf5messagecore5abi1%5f22.12.3-2%5famd64.deb -rw-r--r-- 1 www-data www-data 405 2. Jul 10:55 libkf5messagelist5abi1%5f22.12.3-2%5famd64.deb -rw-r--r-- 1 www-data www-data 407 2. Jul 10:55 libkf5messageviewer5abi1%5f22.12.3-2%5famd64.deb -rw-r--r-- 1 www-data www-data 408 2. Jul 10:55 libkf5mimetreeparser5abi1%5f22.12.3-2%5famd64.deb -rw-r--r-- 1 www-data www-data 403 2. Jul 10:55 libkf5templateparser5%5f22.12.3-2%5famd64.deb -rw-r--r-- 1 www-data www-data 409 2. Jul 10:55 libkf5webengineviewer5abi1%5f22.12.3-2%5famd64.deb -rw-r--r-- 1 www-data www-data 398 2. Jul 10:55 libkfontinst5%5f5.27.5-2+b1%5famd64.deb -rw-r--r-- 1 www-data www-data 400 2. Jul 10:55 libkfontinstui5%5f5.27.5-2+b1%5famd64.deb -rw-r--r-- 1 www-data www-data 402 2. Jul 10:55 libkworkspace5-5%5f5.27.5-2+b1%5famd64.deb -rw-r--r-- 1 www-data www-data 382 2. Jul 10:55 liblc3-1%5f1.0.3-4%5famd64.deb -rw-r--r-- 1 www-data www-data 410 2. Jul 10:55 libnotificationmanager1%5f5.27.5-2+b1%5famd64.deb -rw-r--r-- 1 www-data www-data 381 2. Jul 10:55 libparted2%5f3.6-3%5famd64.deb -rw-r--r-- 1 www-data www-data 389 2. Jul 10:55 libparted-fs-resize0%5f3.6-3%5famd64.deb -rw-r--r-- 1 www-data www-data 396 2. Jul 10:55 libpipewire-0.3-0%5f0.3.71-2+b2%5famd64.deb -rw-r--r-- 1 www-data www-data 402 2. Jul 10:55 libpipewire-0.3-modules%5f0.3.71-2+b2%5famd64.deb -rw-r--r-- 1 www-data www-data 417 2. Jul 10:55 libplasma-geolocation-interface5%5f5.27.5-2+b1%5famd6
Bug#1039907: Aw: Bug#1039907 closed by Debian FTP Masters (reply to Mark Hindley ) (Bug#1039907: fixed in apt-cacher 1.7.30)
Many thanks @Mark for the quick and effective reaction! The new version works as desired.
Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more
Package: sddm Version: 0.19.0-4 Severity: normal X-Debbugs-Cc: chris...@gmx.de Dear Maintainer, immediately after upgrading my bookworm/testing installation on Monday October 17th morning the sddm login screen shows a white background instead the breeze wallpaper. Further no controls different to the login prompt, i.e., shutdown, dropdown to choose desktop environment, etc., are displayed. The same happend to my bookwork kvm instance. As far I can see there were von packages upgraded with sddm in its name, despite of kdm-config-sddm, see below snippet of apt's history.log. I use the sddm-theme-breeze, which is the only one installed. It used to show the colored rocket the last months. Please note, I did not change any configuration in KDE's SDDM settings app. The breeze theme shows up twice, but this is for many years the case (another bug?). Choosing the other one does not change anything. > dpkg -l | grep sddm ii kde-config-sddm 4:5.26.0-1 amd64KCM module for SDDM ii sddm 0.19.0-4 amd64modern display manager for X11 ii sddm-theme-breeze 4:5.25.5-1 amd64Breeze SDDM theme > update-alternatives --display sddm-debian-theme sddm-debian-theme - auto mode link best version is /usr/share/sddm/themes/breeze link currently points to /usr/share/sddm/themes/breeze link sddm-debian-theme is /usr/share/sddm/themes/debian-theme /usr/share/sddm/themes/breeze - priority 30 > cd /usr/share/sddm/themes/ > ls -a total 12 drwxr-xr-x 3 root root 4096 Nov 12 2020 . drwxr-xr-x 7 root root 4096 Oct 9 2015 .. drwxr-xr-x 4 root root 4096 Oct 17 18:49 breeze lrwxrwxrwx 1 root root 35 Jun 25 11:59 debian-theme -> /etc/alternatives/sddm-debian-theme > cd breeze/ > ls -la total 780 drwxr-xr-x 4 root root 4096 Oct 17 18:49 . drwxr-xr-x 3 root root 4096 Nov 12 2020 .. -rw-r--r-- 1 root root 1391 Sep 6 14:35 Background.qml -rw-r--r-- 1 root root 1627 Sep 6 14:35 KeyboardButton.qml -rw-r--r-- 1 root root 5085 Sep 6 14:35 Login.qml -rw-r--r-- 1 root root 23199 Sep 6 14:35 Main.qml -rw-r--r-- 1 root root 1467 Sep 6 14:35 SessionButton.qml drwxr-xr-x 4 root root 4096 Sep 25 14:36 components -rw-r--r-- 1 root root 5681 Sep 6 14:35 default-logo.svg drwxr-xr-x 2 root root 4096 Sep 25 14:36 faces -rw-r--r-- 1 root root 2516 Sep 6 14:35 metadata.desktop -rw-r--r-- 1 root root 717013 Sep 6 14:35 preview.png -rw-r--r-- 1 root root208 Sep 9 23:22 theme.conf > cat theme.conf [General] showlogo=hidden logo=/usr/share/sddm/themes/breeze/default-logo.svg type=image color=#1d99f3 fontSize=10 background=/usr/share/wallpapers/Next/contents/images/5120x2880.jpg needsFullUserModel=false > cd usr/share/wallpapers/Next/contents/images/ > ls -la total 31512 drwxr-xr-x 2 root root4096 Oct 17 08:36 . drwxr-xr-x 4 root root4096 Oct 17 08:36 .. -rw-r--r-- 1 root root 656342 Oct 6 14:07 1024x768.png -rw-r--r-- 1 root root 1073831 Oct 6 14:07 1080x1920.png -rw-r--r-- 1 root root 947830 Oct 6 14:07 1280x1024.png -rw-r--r-- 1 root root 844607 Oct 6 14:07 1280x800.png -rw-r--r-- 1 root root 876586 Oct 6 14:07 1366x768.png -rw-r--r-- 1 root root 1011086 Oct 6 14:07 1440x900.png -rw-r--r-- 1 root root 1270494 Oct 6 14:07 1600x1200.png -rw-r--r-- 1 root root 1265636 Oct 6 14:07 1680x1050.png -rw-r--r-- 1 root root 1463093 Oct 6 14:07 1920x1080.png -rw-r--r-- 1 root root 1534398 Oct 6 14:07 1920x1200.png -rw-r--r-- 1 root root 2245178 Oct 6 14:07 2560x1440.png -rw-r--r-- 1 root root 2362192 Oct 6 14:07 2560x1600.png -rw-r--r-- 1 root root 3125482 Oct 6 14:07 3200x1800.png -rw-r--r-- 1 root root 3238221 Oct 6 14:07 3200x2000.png -rw-r--r-- 1 root root 223019 Oct 6 14:07 360x720.png -rw-r--r-- 1 root root 4097873 Oct 6 14:07 3840x2160.png -rw-r--r-- 1 root root 135430 Oct 6 14:07 440x247.png -rw-r--r-- 1 root root 5200588 Oct 6 14:07 5120x2880.png -rw-r--r-- 1 root root 639660 Oct 6 14:07 720x1440.png > cat /var/log/apt/history.log (shortened to that day) root@betty:/temp# cat history.log Start-Date: 2022-10-17 08:34:20 Commandline: apt-get dist-upgrade Install: node-acorn:amd64 (8.8.0+ds+~cs25.17.7-1, automatic), polkitd-pkla:amd64 (121+compat0.1-6, automatic), node-cjs-module-lexer:amd64 (1.2.2+dfsg-4, automatic), systemd-coredump:amd64 (251.5-2, automatic), node-xtend:amd64 (4.0.2-3, automatic), libduktape207:amd64 (2.7.0-1+b1, automatic), node-undici:amd64 (5.10.0+dfsg1+~cs18.9.18.10-2, automatic) Upgrade: dpkg:amd64 (1.21.9, 1.21.9+b1), libkdecorations2-5v5:amd64 (4:5.25.5-1, 4:5.26.0-1), breeze:amd64 (4:5.25.5-1, 4:5.26.0-1), libtext-unidecode-perl:amd64 (1.30-2, 1.30-3), librados2:amd64 (16.2.10+ds-2+b2, 16.2.10+ds-2+b3), libnode108:amd64 (18.7.0+dfsg-5, 18.10.0+dfsg-6), libcups2:amd64 (2.4.2-1+b1, 2.4.2-1+b2), libmailutils9:amd64 (1:3.15-3, 1:3.15-3+b1), libpolkit-a
Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more
Here some entries from an sddm start in /var/log/syslog, filtered by grep sddm:
Oct 18 08:46:21 betty sddm[925]: Initializing...
Oct 18 08:46:21 betty sddm[925]: Starting...
Oct 18 08:46:21 betty sddm[925]: Logind interface found
Oct 18 08:46:21 betty sddm[925]: Adding new display on vt 7 ...
Oct 18 08:46:21 betty sddm[925]: Loading theme configuration from ""
Oct 18 08:46:21 betty sddm[925]: Display server starting...
Oct 18 08:46:21 betty sddm[925]: Adding cookie to
"/var/run/sddm/{aa4bb32b-dbfe-438e-8bde-4348c400857f}"
Oct 18 08:46:21 betty sddm[925]: Running: /usr/bin/X -dpi 0 -auth
/var/run/sddm/{aa4bb32b-dbfe-438e-8bde-4348c400857f} -background none -noreset
-displayfd 17 -seat seat0 vt7
Oct 18 08:46:22 betty sddm[925]: Setting default cursor
Oct 18 08:46:22 betty sddm[925]: Running display setup script
"/usr/share/sddm/scripts/Xsetup"
Oct 18 08:46:22 betty sddm[925]: Display server started.
Oct 18 08:46:22 betty sddm[925]: Socket server starting...
Oct 18 08:46:22 betty sddm[925]: Socket server started.
Oct 18 08:46:22 betty sddm[925]: Loading theme configuration from
"/usr/share/sddm/themes/breeze/theme.conf"
Oct 18 08:46:22 betty sddm[925]: Greeter starting...
Oct 18 08:46:22 betty sddm-helper[1386]: [PAM] Starting...
Oct 18 08:46:22 betty sddm-helper[1386]: [PAM] Authenticating...
Oct 18 08:46:22 betty sddm-helper[1386]: [PAM] returning.
Oct 18 08:46:23 betty systemd[1388]: Cleanup lingering KCrash metadata was
skipped because of a failed condition check
(ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Oct 18 08:46:23 betty systemd[1388]: Cleanup lingering KCrash metadata was
skipped because of a failed condition check
(ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini).
Oct 18 08:46:23 betty systemd[1]: Started Session 1 of User sddm.
Oct 18 08:46:23 betty sddm[925]: Greeter session started successfully
Oct 18 08:46:23 betty sddm-greeter[1408]: High-DPI autoscaling not Enabled
Oct 18 08:46:23 betty sddm-greeter[1408]: Reading from
"/usr/share/xsessions/plasma.desktop"
Oct 18 08:46:23 betty sddm-greeter[1408]: Loading theme configuration from
"/usr/share/sddm/themes/breeze/theme.conf"
Oct 18 08:46:23 betty sddm-greeter[1408]: Connected to the daemon.
Oct 18 08:46:23 betty sddm[925]: Message received from greeter: Connect
Oct 18 08:46:23 betty sddm-greeter[1408]: QFont::fromString: Invalid
description '(empty)'
Oct 18 08:46:23 betty sddm-greeter[1408]: Loading
file:///usr/share/sddm/themes/breeze/Main.qml...
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject: Cannot create children for a
parent that is in a different thread.#012(Parent is
QGuiApplication(0x7fffced42270), parent's thread is QThread(0x55c623077060),
current thread is QThread(0x55c62319ad10)
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject: Cannot create children for a
parent that is in a different thread.#012(Parent is
QGuiApplication(0x7fffced42270), parent's thread is QThread(0x55c623077060),
current thread is QThread(0x55c62319ad10)
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject: Cannot create children for a
parent that is in a different thread.#012(Parent is
QGuiApplication(0x7fffced42270), parent's thread is QThread(0x55c623077060),
current thread is QThread(0x55c62319ad10)
Oct 18 08:46:23 betty sddm-greeter[1408]: QObject::installEventFilter(): Cannot
filter events for objects in a different thread.
Oct 18 08:46:23 betty dbus-daemon[674]: [system] Activating via systemd:
service name='org.freedesktop.UPower' unit='upower.service' requested by
':1.34' (uid=115 pid=1408 comm="/usr/bin/sddm-greeter --socket
/tmp/sddm-:0-PRpPZo")
Oct 18 08:46:23 betty sddm-greeter[1408]: Failed to find a Kirigami platform
plugin
Oct 18 08:46:23 betty sddm-greeter[1408]:
file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:12:1: Type
InputPanel unavailable
Oct 18 08:46:23 betty sddm-greeter[1408]:
qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:127:5: Type Keyboard
unavailable
Oct 18 08:46:23 betty sddm-greeter[1408]:
qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:38:1: module
"QtQuick.VirtualKeyboard.Plugins" is not installed
Oct 18 08:46:23 betty sddm-greeter[1408]:
file:///usr/share/sddm/themes/breeze/Background.qml:21:5: QML Image: Cannot
open: file:///usr/share/wallpapers/Next/contents/images/5120x2880.jpg
Oct 18 08:46:23 betty sddm-greeter[1408]: Adding view for "HDMI-1" QRect(0,0
1600x1200)
Oct 18 08:46:23 betty sddm-greeter[1408]: Qt Quick Layouts: Polish loop
detected. Aborting after two iterations.
Oct 18 08:46:24 betty sddm-greeter[1408]: Message received from daemon:
Capabilities
Oct 18 08:46:24 betty sddm-greeter[1408]: Message received from daemon: HostName
Bug#1021985: Re. sddm login screen changed to white and does not display the breeze theme any more
I think I have identified the bug now. The breeze package (was upgraded, see above) changed the wallpaper file types from jpg to png. Now the default config of sddm/sddm-theme-breeze does not find it, as it wants a jpg in the file theme.conf . Please fix theme.conf in package sddm-theme-breeze from background=/usr/share/wallpapers/Next/contents/images/5120x2880.jpg to background=/usr/share/wallpapers/Next/contents/images/5120x2880.png The controls, e.g., shutdown et al. are not visible as they are drawn white on default background white (this is a sperarate bug, if you are asking me). Maybe this could be more smart and detect such a border case.
Bug#1021985: sddm login screen changed to white and does not display the breeze theme any more
Control: reassign sddm-theme-breeze 4:5.25.5-1
Bug#1024447: Actual problem is grub-efi-amd64-signed is not updated to 2.06-7
Dear all, > doing an apt upgrade, the grub-efi-amd64-signed package remained at 2.06-5 I can confirm that behavior. A manual call of grub-install/update-grab is necessary after the package upgrade to 2.06-7. Otherwise the grub version which will be used on booting stays 2.06-5 . Maybe the grub packages forget to call update-grub on upgrade? Otherwise the fix seems to work well. @Steve Thanks for mainting grub! Best, Chris
Bug#1024093: pipewire: Upgrade to pipewire 0.3.60-1 breaks sound
Package: pipewire Version: 0.3.60-1 Severity: important X-Debbugs-Cc: chris...@gmx.de Dear Maintainer, using pipewire 0.59-1 under debian testing (with pusleaudio package uninstalled if this should matter) makes no problem. I have copied /usr/share/doc/pipewire/examples/alsa.conf.d to /etc/alsa . However, after upgrading today to pipewire 0.3.60-1 (and rebooting) sound is broken. KDE notifications, firefox on yoputube or a aplay x.wav do not make any sound to come out of my speakers. After downgrading again, everything seems to work fine again. Thanks, Chris -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire depends on: ii adduser 3.129 ii init-system-helpers 1.65.2 ii libpipewire-0.3-modules 0.3.60-1 ii pipewire-bin 0.3.60-1 pipewire recommends no packages. pipewire suggests no packages. -- no debconf information
Bug#1024093: pipewire: Upgrade to pipewire 0.3.60-1 breaks sound
I am using a kvm virtualized installation of bookworm (I did not try it yet on my bare metal installation). Below see some informations which may help. Within syslog I find no spefic entries via 'grep pipewire' which could give me a hint, but I can provide conrete log snippets if you tell what to search for. $aplay -l List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: Generic Analog [Generic Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pactl list sinks Sink #46 State: SUSPENDED Name: alsa_output.pci-_00_1b.0.analog-stereo Description: Internes Audio Analog Stereo Driver: PipeWire Sample Specification: s16le 2ch 48000Hz Channel Map: front-left,front-right Owner Module: 4294967295 Mute: no Volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 Base Volume: 65536 / 100% / 0,00 dB Monitor Source: alsa_output.pci-_00_1b.0.analog-stereo.monitor Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.card = "0" alsa.card_name = "HDA Intel" alsa.class = "generic" alsa.device = "0" alsa.driver_name = "snd_hda_intel" alsa.id = "Generic Analog" alsa.long_card_name = "HDA Intel at 0xc194 irq 48" alsa.name = "Generic Analog" alsa.resolution_bits = "16" alsa.subclass = "generic-mix" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" api.alsa.card.longname = "HDA Intel at 0xc194 irq 48" api.alsa.card.name = "HDA Intel" api.alsa.headroom = "8192" api.alsa.path = "front:0" api.alsa.pcm.card = "0" api.alsa.pcm.stream = "playback" api.alsa.period-size = "256" audio.channels = "2" audio.position = "FL,FR" card.profile.device = "3" device.api = "alsa" device.class = "sound" device.id = "40" device.profile.description = "Analog Stereo" device.profile.name = "analog-stereo" device.routes = "1" factory.name = "api.alsa.pcm.sink" media.class = "Audio/Sink" device.description = "Internes Audio" node.name = "alsa_output.pci-_00_1b.0.analog-stereo" node.nick = "Generic Analog" node.pause-on-idle = "false" object.path = "alsa:pcm:0:front:0:playback" priority.driver = "1009" priority.session = "1009" factory.id = "18" clock.quantum-limit = "8192" client.id = "32" node.driver = "true" factory.mode = "merge" audio.adapt.follower = "" library.name = "audioconvert/libspa-audioconvert" object.id = "45" object.serial = "46" api.acp.auto-port = "false" api.acp.auto-profile = "false" api.alsa.card = "0" api.alsa.use-acp = "true" api.dbus.ReserveDevice1 = "Audio0" device.bus = "pci" device.bus_path = "pci-:00:1b.0" device.enum.api = "udev" device.form_factor = "internal" device.icon_name = "audio-card-analog-pci" device.name = "alsa_card.pci-_00_1b.0" device.nick = "HDA Intel" device.plugged.usec = "3649773" device.product.id = "0x293e" device.product.name = "82801I (ICH9 Family) HD Audio Controller (QEMU Virtual Machine)" device.subsystem = "sound" sysfs.path = "/sys/devices/pci:00/:00:1b.0/sound/card0" device.vendor.id = "0x8086" device.vendor.name = "Intel Corporation" device.string = "0" Ports: analog-output-lineout: Line-Ausgang (type: Line, priority: 9000, availability group: Legacy 2, availability unknown) Active Port: analog-output-lineout Formats: pcm
Bug#1024093: pipewire: Upgrade to pipewire 0.3.60-1 breaks sound
Hi Dylan, thanks for maintaining pipewire and your hint! Now I did the upgrade on my bare metal installation and there the problem does not show up (in contrast to the virtualized one). So it is most likely the upstream issue you have mentioned. However, it is unclear/difficult for me how to try out the in the upstream issue mentioned "pushed fix" in my vm. As you have suggested, I have made an entry to the upstream bug report that I am probably also affected, although the issue seems to be already closed. Chris
Bug#1024093: Aw: Bug#1024093 closed by Debian FTP Masters (reply to Dylan Aïssi ) (Bug#1024093: fixed in pipewire 0.3.60-2)
Hi Dylan, indeed, version 0.3.60-2 solves the virtualization sound problem. Thanks for building the package! All the best, Chris
Bug#1024447: grub-efi-amd64: No box border characters in boot menu
Package: grub-efi-amd64
Version: 2.06-5
Severity: normal
X-Debbugs-Cc: chris...@gmx.de
Dear Maintainer,
I am running debian testing/bookworm. After the updates from grub 2.06-4 to
grub 2.06-5 (about November 18th) in the grub boot menu the box border
characters are not shown as they should. Insteadn one sees only a boxed
question mark for each character. Further, an error message is shown as text
for a fraction of a second directly before the boot menu arsises:
"error: prohibited by secure boot policy."
I believe this is new in 2.06-5.
When I disable secure boot with the mainboard firmware, the characters/boot
menu shows
up correctly.
I can trigger this in my kvm virtualized installtion and on my bare metal
machine with an ASUS H170 Gaming main board (and latest firmware).
Best,
Chris
*** 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 ***
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/sda2 / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sda1 /boot/efi vfat
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
/dev/sdb1 /bak ext4 rw,relatime,errors=remount-ro 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
a959f586-d0e1-4254-84f7-5350df65edb3
else
search --no-floppy --fs-uuid --set=root a959f586-d0e1-4254-84f7-5350df65edb3
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=de_DE
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
a959f586-d0e1-4254-84f7-5350df65edb3
else
search --no-floppy --fs-uuid --set=root a959f586-d0e1-4254-84f7-5350df65edb3
fi
insmod png
if background_image /usr/share/desktop-base/homeworld-theme/grub/grub-16x9.png;
then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-a959f586-d0e1-4254-84f7-5350df65edb3' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2
a959f586-d0e1-4254-84f7-5350df65edb3
else
search --no-floppy --fs-uuid --set=root
a959f586-d0e1-4254-84f7-5350df65edb3
Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail
Meanwhile my Debian Testing systems have (per default) upgraded to libbsd 0.9.1 (and kernel 4.16.0-2). Unfortunaetly, this does not fix the problem (long ssdm start) under virtualization by kvm, although according to #898088 libvirt 0.9.0-1 should have alredy fixed this. On productive bare metal I cannot say anything, as I have set kernel 4.16 on hold by apt. Thx, Chris
Bug#866823: Reproduce "samba: does not follow symbolic links"
Dear Mathieu, sorry for the late reply. > Are you able to reproduce this bug on latest buster (2:4.9.4+dfsg-2 or -3)? Yes, I still can reproduce it on latest buster with samba 2:4.9.5+dfsg-4 . > If yes, can you provide your smb.conf? However, now the bug seems to only show up if I set path=/ (and then of course first navigate to the tmp directroy in windows explorer) instead of path=/tmp in the [share] section of the smb.conf provided in my initial post. Again setting wide links = Yes and allow insecure wide links = Yes functionally helps, although this should not be necessary as even /tmp is an ordinary subdirectory of / and no different/mounted file system. (To get 100% sure of the latter I also created another top level directory /mytopdir next to /tmp with the same results.) Thank you for your interest and help, Chris
Bug#918358: libsane:amd64: Missing permissions for scanner group on usb device
On my Buster machine I can completely reproduce that. However, things are more
complicated. For any somehow newer Epson scanner one needs to install the
vendor drivers from http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
, e.g., like it i the case for my Perfection V37.
While installing the package iscan-data-xx.deb (among others of them),
/lib/udev/60-iscan.rules was generated which is basically a copy of the
60-libsane.rules file of the machine, enriched with some own rules. Once I
installed iscan-data there was the old operating version of 60-libsance.rules
and thus the generated 60-iscan.rules contains the rule to set the ACL right on
the device file.
Thus, until now installing a new version iscan 2.30.4, I noticed nothing,
although I have had updated libsane continuously. But now the dance started.
During installation of iscan-data the (contained and quite naive) post-install
script /usr/lib/iscan-data/make-policy-file tried to generate a new version of
60-iscan.rules but silently failed as the structure of the parsed
60-libsane.conf changed. It copied something, but could not manage to include
alle rules, like the ones about vendor or product ids. And of course no
ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"
as this was not contained any more.
Of course, I know that it is not Debian's fault if a proprietary script of
Epson fails, however, I think that many people will fall over this and have
then to find and fix TWO interacting failures. As a workaround I now list a
manually created version of 60-iscan.conf to put into /etc/udev/rules.6 which
overrules the not operable version under /lib/...:
ACTION!="add", GOTO="iscan_rules_end"
ENV{DEVTYPE}=="usb_device", GOTO="iscan_create_usb_dev"
SUBSYSTEMS=="scsi", GOTO="iscan_scsi_rules_begin"
SUBSYSTEM=="usb_device", GOTO="iscan_usb_rules_begin"
SUBSYSTEM!="usb_device", GOTO="iscan_usb_rules_end"
# Kernel >= 2.6.22 jumps here
LABEL="iscan_create_usb_dev"
# For Linux >= 2.6.22 without CONFIG_USB_DEVICE_CLASS=y
# If the following rule does not exist on your system yet, uncomment it
# ENV{DEVTYPE}=="usb_device", MODE="0664", OWNER="root", GROUP="root"
# Kernel < 2.6.22 jumps here
LABEL="iscan_usb_rules_begin"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0101", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0102", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0103", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0104", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0105", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0106", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0107", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0108", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0109", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010a", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010b", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010c", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010d", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010e", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="010f", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0110", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0112", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0114", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0116", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0118", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0119", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011a", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011b", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011c", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011d", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011e", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011f", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0120", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0121", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0122", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0126", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0128", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0129", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012a", ENV{libsane_matched}="yes"
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="012b", ENV{libsane_matched}="yes"
ATTRS
Bug#928300: secure boot via removable media path unavailable
Dear Steve, I know that this bug is not closed yet, but maybe the following is of interest for you. I noticed your report of bug #930531 which was recently fixed in grub2 version 2.02+dfsg1-19. Thus, I decided to give secure boot another try on my Intel DH77KC board. Meanwhile grub2 2.02+dfsg1-20 was installed on my system. So what I did is $ apt-get install shim-signed grub-efi-amd64-signed (and automatically all deendencies). Then, to be sure, $ update-grub2 $ dpkg-reconfigure grub-efi-amd64 of course with force_efi_extra_removable set to/left on true. $ update-grub2 $ shutdown -r now Then I turned secure-boot on within the mainboard's UEFI Firmware. However, the system then won't boot and shows an error message about security violations. Pretty the same as with my first tries, which led to the initial posting. (A Windows media can be booted in secure mode.) Chris
Bug#928300: secure boot via removable media path unavailable
Dear Steve, I try to deliver missing informations. > Can you get in to the system? I'm guessing (hoping!) just by disabling > SB for now. Fortunately, that is possible. > Then please do a listing of the EFi System Partition and > show us what boot variables are set: > # ls -lR /boot/efi /boot/efi: insgesamt 4 drwx-- 4 root root 4096 Mär 7 2016 EFI /boot/efi/EFI: insgesamt 8 drwx-- 2 root root 4096 Jul 1 18:04 BOOT drwx-- 2 root root 4096 Jul 1 18:04 debian /boot/efi/EFI/BOOT: insgesamt 3968 -rwx-- 1 root root 1322936 Jul 1 18:04 BOOTX64.EFI -rwx-- 1 root root 1206824 Jul 1 18:04 fbx64.efi -rwx-- 1 root root 1529200 Jul 1 18:04 grubx64.efi /boot/efi/EFI/debian: insgesamt 5208 -rwx-- 1 root root 108 Jul 1 18:04 BOOTX64.CSV -rwx-- 1 root root 1206824 Jul 1 18:04 fbx64.efi -rwx-- 1 root root 126 Jul 1 18:04 grub.cfg -rwx-- 1 root root 1529200 Jul 1 18:04 grubx64.efi -rwx-- 1 root root 1261192 Jul 1 18:04 mmx64.efi -rwx-- 1 root root 1322936 Jul 1 18:04 shimx64.efi > # efibootmgr -v BootCurrent: Timeout: 1 seconds BootOrder: ,0008,0009,000A Boot* debian HD(1,GPT,ce8d01bc-8e1e-4bab-bd3f-10a56a1346cd,0x800,0x10)/File(\EFI\debian\shimx64.efi) Boot0008* UEFI : LAN : IP4 Intel(R) 82579V Gigabit Network Connection PciRoot(0x0)/Pci(0x19,0x0)/MAC(4c72b926a1c7,0)/IPv4(0.0.0.00.0.0.0,0,0)AMBO Boot0009* UEFI : LAN : IP6 Intel(R) 82579V Gigabit Network Connection PciRoot(0x0)/Pci(0x19,0x0)/MAC(4c72b926a1c7,0)/IPv6([::]:<->[::]:,0,0)AMBO Boot000A* UEFI : SATA : PORT 6G 0 : SAMSUNG SSD 830 Series : PART 0 : OS Bootloader PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,65535,0)/HD(1,GPT,ce8d01bc-8e1e-4bab-bd3f-10a56a1346cd,0x800,0x10)AMBO # umount /boot/efi (if that should be of interest) # ls -lR /boot/efi /boot/efi: insgesamt 4 drwxr-xr-x 4 root root 4096 Mär 7 2016 EFI /boot/efi/EFI: insgesamt 8 drwxr-xr-x 2 root root 4096 Feb 23 2018 BOOT drwxr-xr-x 2 root root 4096 Feb 23 2018 debian /boot/efi/EFI/BOOT: insgesamt 128 -rwx-- 1 root root 131072 Jun 29 06:15 BOOTX64.EFI /boot/efi/EFI/debian: insgesamt 128 -rwx-- 1 root root 131072 Jun 29 06:15 grubx64.efi The exact error message during booting with SB on is: Image Autorization Fail. System cannot boot to this device due to Security Violation. Press Enter key to continue. Booting the live image like https://cdimage.debian.org/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-xfce.iso with SB on is also not possible (actually I teststed last week's build). Win 10 by installer DVD is (and long time ago an installed system on (another) HDD was) no problem with SB on. Note, I have not a dual boot system or something like that, solely Buster is on my system. # gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.3 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 1000215216 sectors, 476.9 GiB Model: SAMSUNG SSD 830 Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 1F83AB09-033C-4FA1-80CB-8DD29163E919 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1000215182 Partitions will be aligned on 2048-sector boundaries Total free space is 2669 sectors (1.3 MiB) Number Start (sector)End (sector) Size Code Name 12048 1050623 512.0 MiB EF00 2 1050624 933314559 444.5 GiB 8300 3 933314560 1000214527 31.9 GiB8200 # sgdisk --info=1 /dev/sda Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI System) Partition unique GUID: CE8D01BC-8E1E-4BAB-BD3F-10A56A1346CD First sector: 2048 (at 1024.0 KiB) Last sector: 1050623 (at 513.0 MiB) Partition size: 1048576 sectors (512.0 MiB) Attribute flags: Partition name: '' Thank you again for your interest and commitment! Chris
Bug#928300: secure boot via removable media path unavailable
Dear Steve, > It's odd that you have files in /boot/efi but on a separate filesystem > (the rootfs?), not within the ESP. yep, on the rootfs on /dev/sda2. Must have been done by the deb-installer. Now I removed the files from the root partition as ESP is mounted over them. As expected, no change. >> The exact error message during booting with SB on is: >> Image Autorization Fail. > *Exactly* that, including the missing "h" in Authorization ? Or is > that a typo on your part? Defintively, I made the typo, since no cut&paste on the boot screen... > So, I'm curious what keys your system claims to recognise then. The > mokutil tool can dump the public keys in each of the key lists on your > system, as listed in the man page: # mokutil --pk [key 1] SHA1 Fingerprint: 77:a8:28:ba:0c:72:b4:49:79:5c:c0:5a:47:10:cf:a7:29:1c:0f:79 Certificate: Data: Version: 3 (0x2) Serial Number: c3:1d:39:ca:ef:3d:8b:dd Signature Algorithm: sha256WithRSAEncryption Issuer: CN=Intel(R) Desktop Boards Validity Not Before: Feb 2 00:09:49 2013 GMT Not After : Jan 31 00:09:49 2023 GMT Subject: CN=Intel(R) Desktop Boards Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) Modulus: 00:e0:32:77:4d:a5:f3:31:41:5f:9f:36:39:d1:93: ce:b2:16:f8:45:7f:4e:65:c1:42:2c:65:d5:96:5e: 99:22:5d:8a:16:2d:89:52:e3:e6:15:23:c7:7d:b8: 1e:55:84:7b:ca:2a:27:5d:ee:a4:33:6a:52:ff:39: a9:d4:81:21:8f:c2:f5:b8:f8:3c:85:43:60:61:68: 23:72:f1:82:b1:6d:68:ad:69:0b:fb:d1:5a:ed:d2: cd:c1:c4:81:d3:d2:ba:6f:ce:6f:ad:58:25:6f:39: 32:c5:06:ff:57:80:52:d6:8b:63:90:ec:a7:4b:cf: 2a:b0:2e:f7:13:2e:fc:a7:5b:6c:79:86:0d:d2:b3: 04:13:75:18:6d:8b:7a:35:b8:9c:71:00:1c:19:72: a4:8c:24:d4:0d:d5:e9:ca:d0:3b:a0:36:c6:55:4b: 58:b3:f3:7d:58:2d:7b:92:f0:38:e3:3f:06:8d:aa: 79:32:2e:6e:50:dc:8c:1d:e1:f7:db:0f:4b:af:61: bc:bd:d2:ba:d6:5f:ec:8f:79:3e:b8:c8:37:dc:a9: 5a:4d:80:ec:5b:ce:eb:6c:54:68:74:2a:5c:aa:bc: 25:d2:69:e1:c1:51:5b:35:c5:fb:cf:a6:58:a9:6c: f8:73:33:c6:f5:a8:d2:0a:ef:eb:e2:1f:ec:f3:aa: 84:0b Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Subject Key Identifier: D2:EE:76:04:80:00:C1:E6:56:D2:FE:D7:EF:8B:5A:D8:0C:3C:B1:39 X509v3 Authority Key Identifier: keyid:D2:EE:76:04:80:00:C1:E6:56:D2:FE:D7:EF:8B:5A:D8:0C:3C:B1:39 X509v3 Basic Constraints: CA:TRUE Signature Algorithm: sha256WithRSAEncryption 38:e7:c3:21:94:97:9a:0c:96:5b:2d:0e:8a:77:1d:91:da:95: 7f:c6:d2:bc:84:cc:9d:ec:84:7c:8c:09:36:27:2c:08:d2:90: 8a:32:39:3e:4e:46:d9:42:ec:2d:90:94:38:34:24:e6:10:d9: 2e:a5:f2:ce:b2:8e:c0:51:7f:1e:b0:79:17:8b:40:1e:2c:d5: 8d:cb:70:89:ea:f9:2e:63:b1:23:80:c9:41:49:de:d0:5f:5a: bf:86:30:33:c4:57:c6:4e:2f:1a:b3:e9:63:5d:69:90:0d:b9: 00:f6:b4:3e:89:d7:97:0f:d3:ee:2c:6e:ca:a8:cb:ba:d8:4a: 38:46:de:01:6f:e1:8d:2e:6d:fe:ed:e2:55:f8:1a:6f:c7:7a: b8:7d:db:db:34:7f:3e:9e:9e:37:f7:3b:81:0e:52:ef:45:ac: d4:0b:ce:8c:f8:3d:36:ff:2f:9b:f4:e5:bc:9f:5f:d7:6b:8d: 8b:fd:63:d4:b1:69:43:cb:ae:04:07:a1:1a:e8:ed:69:09:3a: 09:3d:d2:b0:e8:b2:b7:6f:25:2c:9c:3e:24:a5:8a:5e:b6:0d: c5:1a:10:90:3f:8b:83:33:7d:d3:37:42:80:cb:6e:23:f8:09: dd:57:16:59:df:e3:8b:b4:fa:f7:82:42:90:d8:b1:71:c6:fe: 16:79:1b:87 # mokutil --kek [key 1] SHA1 Fingerprint: 31:59:0b:fd:89:c9:d7:4e:d0:87:df:ac:66:33:4b:39:31:25:4b:30 Certificate: Data: Version: 3 (0x2) Serial Number: 61:0a:d1:88:00:00:00:00:00:03 Signature Algorithm: sha256WithRSAEncryption Issuer: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation Third Party Marketplace Root Validity Not Before: Jun 24 20:41:29 2011 GMT Not After : Jun 24 20:51:29 2026 GMT Subject: C=US, ST=Washington, L=Redmond, O=Microsoft Corporation, CN=Microsoft Corporation KEK CA 2011 Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) Modulus: 00:c4:e8:b5:8a:bf:ad:57:26:b0:26:c3:ea:e7:fb: 57:7a:44:02:5d:07:0d:da:4a:e5:74:2a:e6:b0:0f: ec:6d:eb:ec:7f:b9:e3:5a:63:32:7c:11:17:4f:0e: e3:0b:a7:38:15:93:8e:c6:f5:e0:84:b1:9a:9b:2c: e7:f5:b7:91:d6:09:e1:e2:c0:04:a8:ac:30:1c:df: 48:f3:06:50:9a:64:a7:51:7f:c8:85
Bug#998386: mesa 21.2.4-1 makes graphical desktop (plasma) unusable
Package: mesa Version: 20.3.5-1 Severity: critical Justification: breaks graphical system like KDE After updateing mesa from 20.3.5 to 21.2.4 in bookworm (migrated on October 21th to testing) my graphical KDE plasma 5.21 under x11 renders unusable. Note plasma 5.23 is currently unusable in testing, see, e.g., bug #996670. There are many more or less longer horizontal lines flying around, and changes of content, like typing text within a terminal, makes just written characters unreadable. The system is very slow to redraw the characters afterwards. Highlighting of elements like menus is slow and ugly. My System is a Core i7-6700 system with integrated CPU grahics Intel HD Graphics 530 rev 06. The login manager sddm works with both versions as desired, as (I believe) it does not use mesa. Hotfix: dowgrade all installed mesa packages to 21.2.4 Thanks fpr looking into it, Chris
Bug#998386: mesa 21.2.4-1 makes graphical desktop (plasma) unusable
Unfortunately, mesa 21.2.4-1 shows the same problem under plasma 5.23 in testing. The latter has finally migrated to testing with all packages yesterday. The combination works fine within my libvirt vm, as I think, it does not use hw accelleration there. However, on bare metal (see above) it stays unusable exactly as described. (OT: As plasma 5.23 depends on mesa >= 21.2.4 it still can't be used and package upgrades are even more difficult regarding the even larger mass of packes now to distiguish). Chris
Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma
Today all packages of plasma 5.23 migrated to testing, and it works fine in my (libvirt) vm. However, on bare metal mesa makes problems (see my bug report #998386), so in fact there plasma 5.23 stays unusable.
Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma
Hi Norbert, thanks to your repsonse! > Can you try/check the following: > * In the Plasma Settings app, go to > Display and Monitor > Compositor > and check whether > Enable compositor on startup > is selected (on). Indeed, turning that switch to on and restarting helps. Great!!! I cannot remeber that I ever turned it on or off. However, if I turn it back to off, then the problems come back (immedeiately). So at least the latter seems to be a bug, right? (Personally I would not need any 3d effects). In my similar kvm virtualized installtion the switch also is/was off, but there it seems to make no problems, even after a couple of changes and restartings. > Also the rendering backend etc is an important information. Same on bare metal and in vm: skaling method: exact redering backend: OpenGL 3.1 latency: Balance of latency and smoothness tearing: automatic holding available window preview images: only for visible windows allow applications to block compositing: enabled > If the above (after logout/login, or better reboot) does not help: > * Is the behaviour reproducible with a **clean** **new** user? Yes, as turning on Enable compositor on startup immediately helped, I did not try that. Chris
Bug#996670: Bug #998386 Plasma gets very slow when compositor is disabled on bare metal
Hi Norbert, > But I guess you had, or some cosmic radiation induced bit switch did it > for you on your hard disk ;-) The default for all installations is being > on. yeah, then lets say "maybe" or "probably" I did that, nevertheless, at least it was a couple of years ago and I cannot remeber ;-) > > In my similar kvm virtualized installtion the switch also is/was off, > > but there it seems to make no problems, even after a couple of changes and > > restartings. > > Hmm, that is indeed strange, though. > > I suggest that *you* create a bug report at upstream (I guess kwin?) > because I cannot reproduce it on my systems (AMD based), and upstream > devs will need detailed informations. Ok, just did that now as suggested, see https://bugs.kde.org/show_bug.cgi?id=444940 Best, Chris
Bug#998386: Bug #998386 Plasma gets very slow when compositor is disabled on bare metal
Mesa 21.2.5-1, today release in debian testing shows the same problem.
Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma
KDE/Plasma (package dependencies) are currently completely broken under testing. Is there currently a chance to (somehow simply) block the partial transition of plasma 5.23 to testing (so that not related package updates are easy)? Selectively upgrading single packages with dependencies one after the other from the mass provided in testing is rather cumbersome. Currently I get the following (sorry for the german locale): root@xxx:~# apt-get dist-upgrade Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Paketaktualisierung (Upgrade) wird berechnet… Fertig Die folgenden NEUEN Pakete werden installiert: libkdecorations2private9 Die folgenden Pakete werden aktualisiert (Upgrade): bluedevil breeze breeze-cursor-theme breeze-gtk-theme drkonqi kactivitymanagerd kde-config-gtk-style kde-config-sddm kde-config-updates kde-style-breeze kgamma5 kinfocenter kmenuedit kscreen ksshaskpass kwayland-integration kwin-style-breeze kwrited libkdecorations2-5v5 libkf5screen-bin libkf5screen7 libpam-kwallet-common libpam-kwallet5 milou oxygen-sounds plasma-discover plasma-discover-common plasma-disks plasma-integration plasma-pa polkit-kde-agent-1 31 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen 96,2 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 47,1 MB Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] n Abbruch. All packages shown above are from version 4:5.23.0 whereas the others would stay on 4:5.21.x. Unfortunately, it is not sufficient to set libkdecorations2-5v5 on hold, as it would remove plasma-desktop: root@xxx:~# apt-mark hold libkdecorations2-5v5 libkdecorations2-5v5 auf Halten gesetzt. root@xxx:~# apt-get dist-upgrade Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Paketaktualisierung (Upgrade) wird berechnet… Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: accountsservice apt-config-icons-hidpi apt-config-icons-large apt-config-icons-large-hidpi bluedevil bluez bluez-obexd breeze-gtk-theme bup bup-doc gtk2-engines-pixbuf ibus-data ieee-data kde-config-gtk-style kde-config-sddm kde-config-updates kgamma5 khotkeys khotkeys-data kinfocenter kmenuedit kscreen kup-backup kwrited libaccountsservice0 libibus-1.0-5 libkpmcore11 libqt5designer5 libqt5help5 libscim8v5 libxcb-record0 oxygen-sounds par2 partitionmanager plasma-desktop-data plasma-discover plasma-discover-common plasma-disks python3-fuse python3-pylibacl python3-pyqt5 python3-pyqt5.sip python3-pyxattr python3-software-properties python3-tornado qml-module-org-kde-activities qml-module-org-kde-kcm qml-module-org-kde-kitemmodels smartmontools software-properties-common software-properties-kde systemsettings xsettings-kde Verwenden Sie »apt autoremove«, um sie zu entfernen. Die folgenden Pakete werden ENTFERNT: kde-plasma-desktop plasma-desktop Die folgenden Pakete sind zurückgehalten worden: breeze breeze-cursor-theme kde-config-gtk-style kde-style-breeze kwin-style-breeze libkdecorations2-5v5 plasma-integration Die folgenden Pakete werden aktualisiert (Upgrade): bluedevil breeze-gtk-theme drkonqi kactivitymanagerd kde-config-sddm kde-config-updates kgamma5 kinfocenter kmenuedit kscreen ksshaskpass kwayland-integration kwrited libkf5screen-bin libkf5screen7 libpam-kwallet-common libpam-kwallet5 milou oxygen-sounds plasma-discover plasma-discover-common plasma-disks plasma-pa polkit-kde-agent-1 24 aktualisiert, 0 neu installiert, 2 zu entfernen und 7 nicht aktualisiert. Es müssen 14,9 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 14,9 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] n Abbruch. When will it be save to switch to 5.23 in testing, or what could be the indicator to do that? When kwin 5.23 will be available in the testing repos? Or would you be so kind to post a corresponding message, e.g., here? Tanks, Chris
Bug#1001640: thunderbird does not use language pack installed from debian repo
Package: thunderbird Version: 91.4.0-1 Severity: normal Today the new thunderbird version migrated to testing und I did a upgrade. However, the translation package (at least for german) does not work although installed. Thunderbird uses englisch language after starting it (menus items and so on). chris@sauron:~$ dpkg -l | grep thunderbird ii thunderbird 1:91.4.0-1 amd64mail/news client with RSS, chat and integrated spam filter support ii thunderbird-l10n-de 1:91.4.0-1 all German language package for Thunderbird Removing ~/.thunderbird for starting completely clean does not help. The integrated Add-ons Manager shows the Deutsch (De) Language Pack as enabled without any problems. Thanks for looking into it, Chris
Bug#1001641: thunderbird does not use debian language pack
Package: thunderbird Version: 91.4.0-1 Severity: normal Today the new thunderbird version migrated to testing und I did a upgrade. However, the translation package (at least for german) does not work although installed. Thunderbird uses englisch language after starting it (menus items and so on). chris@sauron:~$ dpkg -l | grep thunderbird ii thunderbird 1:91.4.0-1 amd64 mail/news client with RSS, chat and integrated spam filter support ii thunderbird-l10n-de 1:91.4.0-1 all German language package for Thunderbird Removing ~/.thunderbird for starting completely clean does not help. The integrated Add-ons Manager shows the Deutsch (De) Language Pack as enabled without any problems. Thanks for looking into it, Chris
Bug#908022: xemacs is not in testing/buster repo any more
Dear Mark, unfortunately the problem still exists, although you have closed the bug. Is there any time esitmation, as xemacs is my favorite editor? Thanks again, Chris
Bug#949444: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/[...]/modules.builtin.bin'
I can perfectly confirm the issue with my two bullseye instances, one on bare metal and the other virtualized with kvm. Chris
Bug#918358: libsane:amd64: Missing permissions for scanner group on usb device
Dear Maintainer, dear Jörg, the bug is closed since a couple of weeks. However, there was no patch released at least for debian testing. The (lib)sane version is still 1.0.27 and the bug(s) still exists. $ dpkg -l | grep sane ii libcommon-sense-perl 3.75-1+b1 amd64module that implements some sane defaults for Perl programs ii libkf5sane-data 19.08.1-1 all scanner library (data files) ii libkf5sane5:amd64 19.08.1-1+b1 amd64scanner library (runtime) ii libsane:amd64 1.0.27-3.2+b1 amd64API library for scanners ii libsane:i386 1.0.27-3.2+b1 i386 API library for scanners ii libsane-common1.0.27-3.2 all API library for scanners -- documentation and support files ii libsane-hpaio:amd64 3.20.5+dfsg0-3 amd64HP SANE backend for multi-function peripherals ii sane 1.0.14-15 amd64scanner graphical frontends ii sane-utils1.0.27-3.2+b1 amd64API library for scanners -- utilities ii xsane 0.999-8 amd64featureful graphical frontend for SANE (Scanner Access Now Easy) ii xsane-common 0.999-8 all xsane architecture independent files Are there any remaining quirks which are not documented here preventing a patch release? If not, please release the new version to testing. Thanks for maintaining sane, Chris
Bug#1085741: Allow also more modern version of Java instead of only Java 21
Package: pdftk-java Version: 3.3.3-2 Severity: normal Currently package pdftk-java requires openjdk-21-jre-headless 21.0.5+11-1 in Debian testing. It is not sufficient to only have a more modern version like openjdk-23-jre-headless 23.0.1+11-1 installed, although the latter should be as good. Java is rather good in backward compatibility. Yes I know 21 is LTS. But I think/hope this is an unnecessary restriction. Thanks, Chris
Bug#1087616: linux-image-6.11.7-amd64: Can't boot (boot freezes after [or maybe during] cryptsetup unlocks drive)
Dear Salvatore, that seems to be a wired thing!? No matter of temporarily within grub bootmenu e and F10 or permanently by changing /etc/default/grub and update-grub, as soon I replace kernel parameter quit by -- systemd.log_level=debug the system boots successfully on ever trie. I did more than 25 boots (warm and cold) and every single one was successfull then. On the first boot after restoring the default boot parameters and booting, the system has run into the hang situation again :( Also in some few cases where I only did remove quit (and not adding -- systemd.log_level=debug ), this suffices for correct booting. Can this be by coincidence, or timing behaviour/race conditions? Chris
Bug#1087616: Can't boot
I also can confirm that booting is not possible in testing any more: Kernel 6.11.9 and 6.11.7 and systemd v257~rc2-3 in a standard grub/efi/ext setup without cryptofs or similar on a sata ssd (so probably better to change the title of the thread). This happens since the upgrade which (among others) installed systemd v257~rc2-3, which may be the culprit. There is a hang which shows "/dev/sda2 clean ..." (probably the output of fsck). After rebooting several times with CTRL+ALT+DEL, from time to time the system boots successfully. But that is rather seldom. As far as I can see, What helps ist pressing one or two times the return key after you see "/dev/sda2 clean ...", then the boot process continues. However, that "hot fix" is no real option, as I mostly start via LAN/magic packet and login via ssh from remote. So I cannot press a key/control that in the early boot process. I think this is in fact a _serious_ bug. As there is no obvious logging entry or similar I initially thought, the root cause is a hardware defect. Unfortunately this costed many hours. Interestingly, rather the same configuration boots very well kvm virtualized. Thanks for looking into it, Chris
Bug#1087616: Aw: Re: Bug#1087616: linux-image-6.11.7-amd64: Can't boot (boot freezes after [or maybe during] cryptsetup unlocks drive)
Dear Salvatore, now up to date with testing's kernel 6.11.10-1 and systemd 257rc3-1, the same issue. In that config I saw the hang even once with my kvm virtualized system. > Would you still as well be able to configure a netconsole so we see if > we get more information of it Of course, however, without success again to trigger the hang in debug mode for many warm amd cold boot attempts. First netcosole kernel log with default quiet parameter and a hang. There is only one line in it: [ 0.079491 x86/cpu: SGX disabled by BIOS.] Attached in file log.txt you can find the version without quiet and with netconsole=... followed by -- systemd.log_level=debug . However, again each time without hang :( Again many thanks for looking into it, Chris[0.00] Linux version 6.11.10-amd64 (debian-ker...@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-8) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.1) #1 SMP PREEMPT_DYNAMIC Debian 6.11.10-1 (2024-11-23) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.11.10-amd64 root=UUID=a959f586-d0e1-4254-84f7-5350df65edb3 ro netconsole=@192.168.0.2/enp0s31f6,9353@192.168.0.5/84:7b:eb:16:a2:cc -- systemd.log_level=debug [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0fff] reserved [0.00] BIOS-e820: [mem 0x1000-0x00057fff] usable [0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved [0.00] BIOS-e820: [mem 0x00059000-0x0008] usable [0.00] BIOS-e820: [mem 0x0009-0x00090fff] reserved [0.00] BIOS-e820: [mem 0x00091000-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xb3908fff] usable [0.00] BIOS-e820: [mem 0xb3909000-0xb393efff] ACPI data [0.00] BIOS-e820: [mem 0xb393f000-0xb3ce8fff] usable [0.00] BIOS-e820: [mem 0xb3ce9000-0xb3ce9fff] ACPI NVS [0.00] BIOS-e820: [mem 0xb3cea000-0xb3ceafff] reserved [0.00] BIOS-e820: [mem 0xb3ceb000-0xc0aa] usable [0.00] BIOS-e820: [mem 0xc0ab-0xc2210fff] reserved [0.00] BIOS-e820: [mem 0xc2211000-0xc226afff] ACPI data [0.00] BIOS-e820: [mem 0xc226b000-0xc2a1cfff] ACPI NVS [0.00] BIOS-e820: [mem 0xc2a1d000-0xc32fefff] reserved [0.00] BIOS-e820: [mem 0xc32ff000-0xc32f] usable [0.00] BIOS-e820: [mem 0xc330-0xc7ff] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x000836ff] usable [0.00] NX (Execute Disable) protection: active [0.00] APIC: Static calls initialized [0.00] extended physical RAM map: [0.00] reserve setup_data: [mem 0x-0x0fff] reserved [0.00] reserve setup_data: [mem 0x1000-0x00057fff] usable [0.00] reserve setup_data: [mem 0x00058000-0x00058fff] reserved [0.00] reserve setup_data: [mem 0x00059000-0x0008] usable [0.00] reserve setup_data: [mem 0x0009-0x00090fff] reserved [0.00] reserve setup_data: [mem 0x00091000-0x0009dfff] usable [0.00] reserve setup_data: [mem 0x0009e000-0x000f] reserved [0.00] reserve setup_data: [mem 0x0010-0xadb55017] usable [0.00] reserve setup_data: [mem 0xadb55018-0xadb65e57] usable [0.00] reserve setup_data: [mem 0xadb65e58-0xadb66017] usable [0.00] reserve setup_data: [mem 0xadb66018-0xadb76057] usable [0.00] reserve setup_data: [mem 0xadb76058-0xb3908fff] usable [0.00] reserve setup_data: [mem 0xb3909000-0xb393efff] ACPI data [0.00] reserve setup_data: [mem 0xb393f000-0xb3ce8fff] usable [0.00] reserve setup_data: [mem 0xb3ce9000-0xb3ce9fff] ACPI NVS [0.00] reserve setup_data: [mem 0xb3cea000-0xb3ceafff] reserved [0.00] reserve setup_data: [mem 0xb3ceb000-0xc0aa] usable [0.00] reserve setup_data: [mem 0xc0ab-0xc2210fff] reserved [0.00] reserve setup_data: [mem 0xc2211000-0x00
Bug#1087616: confirm linux-image-6.11.7-amd64 boot failure
ian_br...@mail.ru wrote at Mon, 2 Dec 2024 22:56:25 -0800 > However, having now installed systemd v257~rc3-1, the problem seems to > have gone away, without altering the boot parameters. This is the case > at least with kernel linux-image-6.11.10-amd64. I cannot confirm that. The hang in with systemd v257-rc3-1 and kernel 6.11.10-1 is definitly still present on my physical and virtual systems. However, it seems to occur slightly not so often as before, but that may be misleading. However, I am quite happy that someone can reproduce, that it mainly (always?) occurs with (solely?) kernel parameter quiet set. Chris
Bug#1091001: skanlite does not run/cannot be installed with plasma 6
Package: skanlite Version: 22.12.3-1+b1 Severity: normal Dear maintainers, after the transition from plasma 5 to 6 skanlite does not start any more in trixie, at least under now default wayland mode. As skanlite has kept package skanpage on hold, I uninstalled skanlite and then installed skanpage. skanpage works. Now installing skanlite is inpossible, as far I can see, because of the dependency libsanecore1 instead of liksanecore6-1: $ dpkg -l | grep skanpage ii skanpage24.12.0-1amd64Multi-page scanning and saving of documents and images $ apt-cache policy skanlite skanlite: Installed: (none) Candidate: 22.12.3-1+b1 Version table: 22.12.3-1+b1 500 500 http://ftp.de.debian.org/debian testing/main amd64 Packages $ apt-get install skanlite Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libksanecore6-1 : Breaks: libksanecore1 but 23.08.1-2+b1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. $ dpkg -l | grep plasma-desktop ii kde-plasma-desktop5:151amd64KDE Plasma Desktop and minimal set of applications ii plasma-desktop4:6.2.4-1amd64Tools and widgets for the desktop ... $ dpkg -l | grep plasma-framework ii plasma-framework 5.115.0-7amd64Plasma Runtime components Thanks for looking into it. Chris
Bug#1039129: apt-cacher: ships sysv-init script without systemd unit
Dear Marc, I think it is time now to supply systemd unit files to start apt-cacher, as /usr/share/doc/systemd/NEWS.gz shows: ``` systemd System and Service Manager CHANGES WITH 257: ... Announcements of Future Feature Removals: ... * Support for System V service scripts is deprecated and will be removed in v258. Please make sure to update your software *now* to include a native systemd unit file instead of a legacy System V script to retain compatibility with future systemd releases. ... ``` That is with the next system (major) version v258 apt-cacher does not start any more. Currently, we already have systemd v257 on testing. Many thanks for maintaing apt-cacher, great job! Chris
