Plasma logout oddness possible systemd-homed involvement
by Ian Malone
I'm not motivated to investigate this further, but in case anyone else
is having a similar problem. After recent updates (currently
sddm-0.19.0^git20230201.3ee57e9-2.fc37.x86_64) I had a number of
issues, the most annoying of which was inability to log out on
First the login screen only showed a password dialogue, white
background and a small (apparently power) icon at the bottom right,
user selection was not possible, no response to Esc key, power icon
not clickable. Login via password for my normal user worked. This
appears to have been fixed by using system settings to change the
Second wallpaper setting was lost, but as this frequently happens with
Plasma upgrades recently it may be unconnected. More unusually the
lock screen background has changed to black, which I have not seen
Lastly, as in the subject, logging out became an issue. Both
Plasma+X11 and Plasma+Wayland sessions simply hung on log out, whether
or not the logout screen option was selected. Without logout screen
this happened immediately on clicking logout, with logout screen it
happened after confirming logout. Whether the display blanked or just
froze appeared variable. Restarting and shutdown were fine. I was
unable to find any particularly noteable journal messages, however
there was a mention of systemd-homed being unable to find home for
sddm user and my account (Not a user managed by systemd-homed: No home
for user sddm known). On a whim I tried stopping systemd-homed during
a frozen logout (from a virtual terminal) then stopping
graphical.target and starting it again. After this I was able to log
out successfully from Plasma, and this has persisted across reboots
despite systemd-homed still running. Prior to this I had tried an
.autorelabel (without success) and, as mentioned, both X11 and Wayland
sessions had the same issue.
3 weeks, 5 days
welcome dialog on a Live image?
by Kamil Paral
There's a new Welcome dialog in KDE on F38. However, it's also started on a
Live image. Some part of it makes sense (basic info about the desktop), but
some part doesn't (usage collection request, online accounts
configuration). I wonder if it's supposed to start on a Live image or not?
KDE Plasma (Fedora 37) performance on Raspberry Pi 4
by Syam Krishnan
I got a Raspberry Pi 4 board with 8 GB RAM today, and tried both KDE
Plasma and Fedora Workstation images on it. While the workstation (with
Gnome) works pretty well, the Plasma desktop is quite sluggish when it
comes to graphics. Moving windows around a bit fast, tool-tip popups on
taskbar elements etc. are noticeably sluggish and have significant
response delays. Gnome desktop does not have any such issues.
Both are running the same kernel versions. But they are two different
images (both downloaded from Fedora website), so I don't know if there
are any relevant differences in the pre-installed packages.
Any ideas on how to rectify this? I was on KDE/X11 most of the time, and
during a brief testing with KDE/Wayland, it didn't fare any better.
Window moving virtual desktop
by Mark ＠ GMail
Now (since F37, I think), clicking on a URL in an email (in Evolution,
3.46.3-1.fc37) moves my browser (FireFox) to the same virtual desktop
that Evolution is in.
It didn't used to do this, and it's not what I want, but I can see some
might want that, so is it an option somewhere? If so, where?
Fedora Linux 37, Workstation
KDE Plasma 5.26.5
KDE Frameworks 5.102.0
Graphics Platform X11
Dolphin not saving state
by Patrick O'Callaghan
For years I've had a fixed set of three Dolphin windows opened (in a
saved session) when I log in, each of them in a specific directory, two
with split panels and one with a single panel. The single-panelled one
also has the terminal pane open.
Since installing dolphin-22.12.2-1.fc37.x86_64 this no longer works. I
still get the three windows in the right places, but they are all
showing my home directory and a single panel. None has the terminal
Where does Dolphin store its session state? Or is this a wider problem?
I'm on X11 because of general issues with session restore on Wayland,
but this looks like a regression.
1 month, 1 week
Screen locker fails after update to F37
by Tim Landscheidt
I use a plain black screen as the screen locker in KDE/Way-
land, and I have "linger" enabled in systemd for my user. I
updated from F35 to F37 three days ago; there are parts of
my KDE configuration that are a decade old.
Whenever the time comes for the screen to lock up, a trans-
lated message appears on the screen instead informing that
the screen locker is broken and that I should use "loginctl
unlock-session $nr" in a plain shell (which works).
I searched for this error, and one suggestion was to exe-
| [tim@vagabond ~]$ /usr/libexec/kscreenlocker_greet --testing
| kscreenlocker_greet: Lockscreen QML outdated, falling back to default
| kf.kirigami: Failed to find a Kirigami platform plugin
| Speicherzugriffsfehler (Speicherabzug geschrieben)
| [tim@vagabond ~]$
(last line meaning core dumped).
So I went to the KDE "Systemeinstellungen" (system set-
tings?) to rewrite any relevant configuration in the current
format, disabled the lock screen, applied the configuration,
enabled it again, applied the configuration, no luck. Re-
booted, no luck.
There is a package kf5-kirigami2-5.102.0-1.fc37.x86_64
installed, and with
https://api.kde.org/frameworks/kirigami/html/ using "plat-
form" as referring to "Plasma Mobile, Desktop Linux, An-
droid, iOS and Windows", I don't see another package that
could be expected to provide a "Kirigami platform plugin".
On a whim, I also installed
kf5-kirigami-1.1.0-18.fc37.x86_64 because the error message
only referred to "Kirigami", not "Kirigami2", but this does
not change the failure.
So I would appreciate any ideas where to start looking for
a solution. Is "kscreenlocker_greet --testing" supposed to
work in Fedora? Fedora 37? Fedora 37 with Wayland?
1 month, 1 week