Bug 349271 - Plasmashell crashed after putting the computer into a docking station and waking it up from suspend-to-RAM
Summary: Plasmashell crashed after putting the computer into a docking station and wak...
Status: RESOLVED DUPLICATE of bug 348812
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.2.2
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-17 06:33 UTC by Arne Henningsen
Modified: 2015-06-17 15:25 UTC (History)
2 users (show)

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

Attachments
Backtrace and other collected information (81.32 KB, text/plain)
2015-06-17 06:34 UTC, Arne Henningsen 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Arne Henningsen 2015-06-17 06:33:15 UTC 
I suspended my laptop computer (HP EliteBook 8560w) to RAM when it was *not* in a docking station. Some hours later, I put it into a docking station (with external monitor) and waked it up from suspend-to-RAM. The external monitor did not show the screen. After unlocking the screen, the bug reporting assistant appeared (and the external monitor is still "black"). This bug may be related to bug #348873, bug #349197, and the following bug, which I experience from time to time on the same computer:

https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1461001

I will attach the information (including a 2-star-backtrace) that was collected by the bug reporting assistant (that refused to post the bug report here due to error "114").

Reproducible: Always
Comment 1 Arne Henningsen 2015-06-17 06:34:55 UTC 
Created attachment 93206 [details]
Backtrace and other collected information
Comment 2 Arne Henningsen 2015-06-17 06:37:12 UTC 
For some reason, I overlooked the "reproducibility" menu. The bug is *not* always but *sometimes* reproducible. Sorry!
Comment 3 David Edmundson 2015-06-17 15:25:25 UTC 
Thanks, found another bug with the same trace. Marking as duplicate

*** This bug has been marked as a duplicate of bug 348812 ***