Bug 497009 - ksmserver-logout-greeter doesn't show up
Summary: ksmserver-logout-greeter doesn't show up
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Session Management (other bugs)
Version First Reported In: 6.2.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-03 20:20 UTC by Avraham Hollander
Modified: 2024-12-15 16:32 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Avraham Hollander 2024-12-03 20:20:12 UTC
SUMMARY
ksmserver-logout-greeter doesn't show up. From some debugging, it is being appropriately activated over dbus when clicking the power and session buttons in Kickoff, but nothing happens. This only affects actions which need confirmation. Disabling confirmation in System Settings > Desktop Session allows the buttons to work as expected.

STEPS TO REPRODUCE
1. Make sure confirmation is enabled in System Settings > Desktop Session.
2. Try to log out, shut down, or reboot.

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
The ksmserver-logout-greeter shows up as usual.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.10-300.fc41.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION
This is on a pretty much brand new Fedora 41 installation. I have an older installation (both are currently up to date) that works just fine.
Comment 1 Nate Graham 2024-12-13 20:28:43 UTC
Does it work in a Wayland session?
Comment 2 Avraham Hollander 2024-12-15 16:32:51 UTC
(In reply to Nate Graham from comment #1)
> Does it work in a Wayland session?

I just updated the system, pulling in Qt 6.8.1, and now it's working again. So I'm calling this fixed.