stellarsolver is marked for autoremoval from testing
stellarsolver 2.5-1 is marked for autoremoval from testing on 2024-04-26 It is affected by these RC bugs: 1066275: stellarsolver: FTBFS: os-features.h:123:17: error: implicit declaration of function âqsort_râ; did you mean âqsortâ? [-Werror=implicit-function-declaration] https://bugs.debian.org/1066275 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
Bug#1068785: Sometimes the keyboard is turned off when waking from standby after upgrading to Debian12
Package: sddm Version: 0.19.0-5 This could also be an issue of the Sleep function. I'm using a laptop that suspends to swap partition. After upgrading to Debian12 with KDE, sometimes the keyboard of a laptop is turned off while the touchpad still works. It doesn't work again after putting it back into standby and then waking it from standby. It really is in standby as one could hear if it wasn't. After waking from Hibernate or when just locking the screen the keyboard does work. Moreover, often if not always under some conditions (which I'll try to find out and then add) the laptop shows the prior screen for 0.2-4.0 seconds before it shows the lockscreen. This obviously is a privacy issue and could be linked to the prior problem. It hasn't occurred the last two days. When I just Log Out the keyboard works fine at the lockscreen. It only doesn't work when resuming from sleep (opening the lid after it was closed or pressing the power button after clicking Sleep). Once I started testing and asking about this the problem the keyboard didn't just stop working sometimes but never worked after resuming from Sleep for at least 10 different kinds tries. Now first clicking Sleep in the bottom left caused a shutdown (instead of sleep) again (I think it did some disk check when waking), and afterwards the keyboard now works again when resuming from sleep in two tries but I think it's only back to sometimes rather than always being dysfunctional. Please go here for further details: https://unix.stackexchange.com/questions/773987/sometimes-the-keyboard-is-turned-off-when-waking-from-standby-after-upgrading-to Also it may be useful to test or develop tests whether it's fully and without problems going to Sleep, see: https://unix.stackexchange.com/q/774151/233262
Bug#1068784: When configuring Wayland to be the default at the login screen this doesn't change the session the user is automatically logged into
Package: sddm Version: 0.19.0-5 When configuring Wayland to be the default at the login screen (dropdown in the upper left) as recommended at places where people asked about how to switch from X11 to Wayland, this doesn't change the session the user is automatically logged into. I think it should be changed or the user be asked if they'd like to change the default after auto-login if they changed it at the lockscreen. Here I got this reply https://github.com/sddm/sddm/issues/1912 : >If you set > >[Autologin] >Session= > >it'll use the last used session for autologin. kcm_sddm does not support that, >so you'll have to put that into /etc/sddm.conf.d/y_autologin.conf to override >the value from kde_settings.conf.
Bug#1068783: After upgrading to Debian12 the session SDDM automatically logs in to is changed
Package: sddm Version: 0.19.0-5 On one of the machines upgraded from Debian11 to Debian12 I had configured that it automatically logs in. But it seems like in the dropdown next to "with session" after the upgrade this was changed to "Kodi" instead of "Plasma (X11)" (there was no noticeable difference to the standard X11 session and Kodi didn't autostart). It's probably because "Kodi" is the first value in the dropdown which seems to be sorted alphabetically. Please either make it so that the value before the upgrade is set there or that it's Wayland in specific.
Bug#1068780: Two login screens with the same name and with no preview/image
Package: sddm Version: 0.19.0-5 In Debian12 with KDE5 (SDDM v0.19.0-5) after an Upgrade from Debian11 under System Settings -> Startup and Shutdown -> Login Screen (SDDM) there are two Login screens with the same name and no preview. Screenshot in the link below (this issue tracking system is outdated by decades). When hovering on the second login screen the trashbin button is also greyed out. Screenshot and some info that could be relevant: https://github.com/sddm/sddm/issues/1912 If I start systemsettings from the console when opening up this page to view the login screens this is the new output: QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:257:13: QML SelectableLabel: Binding loop detected for property "implicitWidth" file:///usr/share/kpackage/kcms/kcm_sddm/contents/ui/main.qml:54:20: QML Image: Cannot open: file:///usr/share/sddm/themes/debian-maui/maui.jpg file:///usr/share/kpackage/kcms/kcm_sddm/contents/ui/main.qml:54:20: QML Image: Cannot open: file:///usr/share/sddm/themes/debian-maui/maui.jpg file:///usr/share/kpackage/kcms/kcm_sddm/contents/ui/main.qml:54:20: QML Image: Cannot open: file:///usr/share/sddm/themes/debian-maui/maui.jpg file:///usr/share/kpackage/kcms/kcm_sddm/contents/ui/main.qml:54:20: QML Image: Cannot open: file:///usr/share/sddm/themes/debian-theme/maui.jpg file:///usr/share/kpackage/kcms/kcm_sddm/contents/ui/main.qml:54:20: QML Image: Cannot open: file:///usr/share/sddm/themes/debian-maui/maui.jpg file:///usr/share/kpackage/kcms/kcm_sddm/contents/ui/main.qml:54:20: QML Image: Cannot open: file:///usr/share/sddm/themes/debian-theme/maui.jpg qml: The item SubCategoryPage_QMLTYPE_74(0x55b0a5ab7d50) is already in the PageRow Maybe this is because two display monitors are configured? I previously had a problem of a second smaller login screen above a larger one (mirrored content where I could login in either) before I disabled the other powered-off display monitor under "Display Configuration". Bug report in need of more info if anybody can provide it here: https://bugs.kde.org/show_bug.cgi?id=485199 I would expect that there only is one login screen and that it has a preview image.
Bug#1068779: Shortcuts for systemmonitor and plasma-systemmonitor are missing after upgrade or when installing it
Package: plasma-systemmonitor Version: 5.27.5-2 On one of the machines I upgraded to Debian12 from Deb11/KDE the Default shortcut Ctrl+Esc for "Show System Activity" in "KDE Daemon" under Shortcuts is disabled but not on the other. This meant that the process manager didn't show anymore when pressing ctrl+esc after upgrading which can be quite annoyance to users and seems like a problem that is easy to solve: just make sure that shortcut doesn't get disabled. Note that Ctrl+Esc is also set as a shortcut under File->Close. I don't know why it was disabled. It could also be enabled whenever plasma-systemmonitor / systemmonitor gets installed. That this is hard to find under "KDE Daemon" where most users wouldn't expect this entry makes it an even bigger problem but the shortcuts should be working by default without requiring any configuration in general anyway. In addition, the shortcut Ctrl+Shift+Esc should be set for opening plasma-systemmonitor; currently this has to be configured under Custom Shortcuts. It should be there by default or right after installing plasma-systemmonitor which should be installed by default. Related issue: plasma-systemmonitor with the process manager is not installed anymore after upgrading to Debian12 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068777
Bug#1068777: plasma-systemmonitor with the process manager is not installed anymore after upgrading to Debian12
Package: kde-plasma-desktop Version: 5:142 After upgrading from Debian11/KDE to Debian12, plasma-systemmonitor was not installed. This should definitely be an installed package and I think it is configured to be. On Debian11, KSysGuard was used. Now there only is KSysguard in "Background Services" which "Launches KSysguard on Ctrl + Escape" and launches systemd->systemmonitor. While this shortcut was kept, ctrl+shift+esc wasn't set anymore so one has to configure it again under "Custom Shortcuts" with command "plasma-systemmonitor". I checked /var/log/apt/history.log and there it says "plasma-systemmonitor:amd64 (5.27.5-2, automatic)" underneath apt-get full-upgrade in the packages next to "Install: ". However that process exited with "Error: Sub-process /usr/bin/dpkg returned an error code (1)" because of "FATAL ERROR: Both /lib/udev/mtp-probe and /usr/lib/udev/mtp-probe exist." after which I ran "apt --fix-broken install" before running "apt-get full-upgrade" again. Right after all this (that is upgrading to Debian12) I noticed this package was not installed and installed this specific package. plasma-systemmonitor, which includes the process manager, should always be installed by default on a new KDE setup as well as when upgrading from the prior Debian version which had KSysguard installed. In addition, the widely known and much used shortcut ctrl+shift+esc should also be there by default and launch plasma-systemmonitor (or alternatively systemmonitor).
Processed: Bug#1053409 marked as pending in qtwebengine-opensource-src
Processing control commands: > tag -1 pending Bug #1053409 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS with re2 >= 20230601 (which requires abseil) Added tag(s) pending. -- 1053409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053409: qtwebengine-opensource-src: FTBFS with re2 >= 20230601 (which requires abseil)
Control: tags -1 patch I created a merge request at: https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/merge_requests/ 26[1] -- Soren Stoutner so...@debian.org [1] https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/merge_requests/ 26 signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1053409: qtwebengine-opensource-src: FTBFS with re2 >= 20230601 (which requires abseil)
Processing control commands: > tags -1 patch Bug #1053409 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS with re2 >= 20230601 (which requires abseil) Added tag(s) patch. -- 1053409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053409: qtwebengine-opensource-src: FTBFS with re2 >= 20230601 (which requires abseil)
As Chromium has supported the updated RE2 since around 116, that will likely be included in the Qt WebEngine 6.7.0 release. https://wiki.qt.io/QtWebEngine/ChromiumVersions[1] It is unlikely to ever make it back to Qt WebEngine 5.15.x. Currently, Qt WebEngine 6 has switched to building against the embedded copy of RE2, which can be reverted once 6.7.0 is packaged. https://salsa.debian.org/qt-kde-team/qt6/qt6-webengine/-/commit/ d4ea2d870d0db1afc9c16668bf537f8fac28f3d7[2] I think I will make a similar adjustment to Qt WebEngine 5, but without the plan to ever switch it back as Qt WebEngine 5 is reaching end-of-life. -- Soren Stoutner so...@debian.org [1] https://wiki.qt.io/QtWebEngine/ChromiumVersions [2] https://salsa.debian.org/qt-kde-team/qt6/qt6-webengine/-/commit/ d4ea2d870d0db1afc9c16668bf537f8fac28f3d7 signature.asc Description: This is a digitally signed message part.
