https://bugs.kde.org/show_bug.cgi?id=359465
Bug ID: 359465
Summary: plasmashell unresponsive/freezes after resuming from
suspend to RAM
Product: kwin
Version: 5.5.3
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: juergen.scholz...@gmail.com
I am using ubuntu 15.10/wily with the kubuntu backports PPA, which at the
moment provides plasmashell 5.5.3.
Every time I resume my computer from suspend to RAM plasmashell freezes and
does not react to any input. At the same time krunner is working fine and I can
start applications or use already open ones normally.
The situation can be resolved by issuing killall plasmashell; plasmashell in
krunner.
Additionally the mouse cursor is reacting with a lot of jitter to mouse
movements, until a notification that eth0 has been re-connected appears.
Sometimes there is a notification that eth0 has gone down (probably a delayed
notification from the suspend process).
Thomas Lübking noted that this behaviour is caused by a deadlock between kwin
and plasmashell. Please see https://bugs.kde.org/show_bug.cgi?id=358245#c6 for
details.
I will attach the backtraces.
Reproducible: Always
Steps to Reproduce:
1. Start KDE session.
2. Suspend machine to RAM.
3. Resume machine.
There seems to be a possibility to circumvent the crash:
1. Log in normally on boot (Terminal 7)
2. Use the session manager (krunner -> sessions) to create a second session for
another user
3. Log in on second session (Terminal 8) and stay on that terminal
4. Suspend system
5. Resume system
6. Switch from Terminal 8 to Terminal 7 with the original session and find the
screen locked and plasmashell not crashed.
Actual Results:
kwin/Plasmashell does not react to input. Applications and krunner work.
Expected Results:
kwin/Plasmashell does react to inputs. Applications and krunner work.
Possibly related bugs:
https://bugs.kde.org/show_bug.cgi?id=352423
https://bugs.kde.org/show_bug.cgi?id=355457
--
You are receiving this mail because:
You are watching all bug changes.
