Bug 318260 - Plasma-device often crashes on resume from sleep
Summary: Plasma-device often crashes on resume from sleep
Status: RESOLVED FIXED
Alias: None
Product: Active
Classification: Plasma
Component: Plasma mobile shell (show other bugs)
Version: Integration
Platform: Other Linux
: NOR critical
Target Milestone: unscheduled
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-12 19:45 UTC by Thomas Pfeiffer
Modified: 2013-08-06 19:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Pfeiffer 2013-04-12 19:45:39 UTC
When resuming from sleep, plasma-device crashes very often. Sometimes with DrKonqi (I could not generate a backtrace yet because last time I tried, DrKonqi itself froze), sometimes without but restarting itself, sometimes it does not even restart itself.
It happens particularly often - though not only then - when Reader is open when  I send the device to sleep.

Reproducible: Sometimes

Steps to Reproduce:
1. Open a document in Reader
2. Lock screen and let it go to sleep
3. Resume
4. Unlock
Actual Results:  
Plasma crashes

Expected Results:  
No crash
Comment 1 Michael Bohlender 2013-04-12 19:56:42 UTC
I experience something similar on my nexus7. 
It freezes with a bright but black screen or reboots itself when I try to wake it from sleep.
DrKonki did not show up so far.
Comment 2 Thomas Pfeiffer 2013-05-06 18:46:16 UTC
This is still reproducible with current Integration packages. It crashed the very first time I woke my device up from sleep, and DrKonqi froze after having generated 10864 lines of backtrace. Maybe that was too much for it?
Then I went trough another sleep-resume cycle. Plasma crashed again, this time restarting itself without DrKonqi opening. Third time same problem.
Comment 3 Thomas Pfeiffer 2013-08-06 16:20:03 UTC
This still happens, and it happens every single time I resume from sleep.
Comment 4 Marco Martin 2013-08-06 17:32:17 UTC
reproduced, and indeed the backtrace seems to be recursive.

for the little ican see in it tough, the problem seems to come from  the networkmanager plasmoid
Comment 5 Marco Martin 2013-08-06 18:19:54 UTC
I pushed a more recent networkmanager applet (from devel), and here seems a bit more reliable.

to try it is enough to do zypper refresh/zypper up then reboot, is not necessary a new image
Comment 6 Thomas Pfeiffer 2013-08-06 19:10:13 UTC
I didn't have any crashes so far with the new version, so it seems to have been fixed