Bug 355609 - After selecting shutdown from the menu, nothing happens, ksmserver CPU usage spikes
Summary: After selecting shutdown from the menu, nothing happens, ksmserver CPU usage ...
Status: RESOLVED FIXED
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: ui (show other bugs)
Version: 5.4.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-19 21:31 UTC by soltesz.balazs.91
Modified: 2015-12-14 20:53 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description soltesz.balazs.91 2015-11-19 21:31:52 UTC
After selecting Shutdown from the Kmenu/leave page, nothing happens - the menu closes, but the shutdown promt does not appear. Ksmserver CPU usage jumps (100% on a single core).
Reselecting shutdown does not help.
Shutdown goes smoothly (no error is visible) by using systemctl shutdown or shutdown -h now.
After killing ksmserver process, the screen goes black then the login screen appears.

Reproducible: Sometimes

Steps to Reproduce:
1. Open Kmenu
2. Select shutdown
3. ???

Actual Results:  
Nothing happens, except ksmserver start using 100% cpu on a single core.

Expected Results:  
The system should present the shutdown dialog, then shut down.

I have no shutdown scripts registered.

The issue was present on previous versions too, but was rarer.
Comment 1 soltesz.balazs.91 2015-11-19 23:15:40 UTC
I've just experienced the bug again, and I've got to make some changes:
After ksmserver CPU usage jumped to 100%, trying to bring up systemmonitor or Ksysguard was unsuccessful (Ctrl+esc did not work, krunner hanged).
After killing ksmserver by sending TERM signal, window decorations disappeared, but  both the system monitor and ksysguard opened up.

I could not recover the session, had to restart it by restarting X.
Comment 2 soltesz.balazs.91 2015-11-19 23:17:45 UTC
(In reply to soltesz.balazs.91 from comment #1)
> I've just experienced the bug again, and I've got to make some changes:
> After ksmserver CPU usage jumped to 100%, trying to bring up systemmonitor
> or Ksysguard was unsuccessful (Ctrl+esc did not work, krunner hanged).
> After killing ksmserver by sending TERM signal, window decorations
> disappeared, but  both the system monitor and ksysguard opened up.
> 
> I could not recover the session, had to restart it by restarting X.

After restarting X and signing in, shutdown worked flawlessly.
Comment 3 soltesz.balazs.91 2015-12-14 20:53:45 UTC
The bug seems fixed in 5.5.0