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 skanpa
This bug was silently fixed in sddm-theme-breeze 4:5.26.0-2 .
Control: reassign sddm-theme-breeze 4:5.25.5-1
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 f
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
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
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 ;-
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!!!
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.
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 afte
10 matches
Mail list logo
