[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?

2017-09-28 Thread David Edmundson
https://bugs.kde.org/show_bug.cgi?id=362589 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?

2016-05-02 Thread PGillespie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362589 --- Comment #4 from PGillespie --- Okay. I attached GDB to plasmashell and the appropriate PID. I suspended and resumed twice while GDB was attached. The KDE panel locked up after the second suspend. Had to kill GDB and

[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?

2016-05-02 Thread PGillespie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362589 --- Comment #3 from PGillespie --- I'm sorry, scratch that last question (and you only have to confirm this with me once and we're on our way) . Would plasma-workspace be the component in question? gdb plasma-workspace -- You

[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?

2016-05-02 Thread PGillespie via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362589 --- Comment #2 from PGillespie --- It's not something I've done before, but I'm just reading about it here: https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports In regards to the problem

[plasmashell] [Bug 362589] After resume from Suspend / Compositing Failure?

2016-05-02 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362589 --- Comment #1 from Thomas Lübking --- backtrace or it didn't happen, but it's most likely just bug #341497 -- You are receiving this mail because: You are watching all bug changes.