| Summary: | After selecting shutdown from the menu, nothing happens, ksmserver CPU usage spikes | ||
|---|---|---|---|
| Product: | [Unmaintained] ksmserver | Reporter: | soltesz.balazs.91 |
| Component: | ui | Assignee: | Lubos Lunak <l.lunak> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.4.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
soltesz.balazs.91
2015-11-19 21:31:52 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. (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. The bug seems fixed in 5.5.0 |