Bug 359465 - plasmashell unresponsive/freezes after resuming from suspend to RAM
Summary: plasmashell unresponsive/freezes after resuming from suspend to RAM
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.5.3
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-16 14:46 UTC by Jürgen Scholz
Modified: 2017-02-18 00:41 UTC (History)
1 user (show)

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


Attachments
Back trace of plasmashell 5.5.3 freeze after resume (63.27 KB, text/plain)
2016-02-16 14:47 UTC, Jürgen Scholz
Details
Backtrace of kwin_x11. (39.88 KB, text/plain)
2016-02-16 14:49 UTC, Jürgen Scholz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jürgen Scholz 2016-02-16 14:46:16 UTC
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
Comment 1 Jürgen Scholz 2016-02-16 14:47:26 UTC
Created attachment 97247 [details]
Back trace of plasmashell 5.5.3 freeze after resume
Comment 2 Jürgen Scholz 2016-02-16 14:49:08 UTC
Created attachment 97248 [details]
Backtrace of kwin_x11.
Comment 3 Thomas Lübking 2016-02-16 15:13:47 UTC
Not exactly what I meant ;-)

See bug #359467 for the kwin issue (it's not related to the plasmashell issue)
I'm closing this one as it's rather confusing.