Bug 402567 - Kwin compositor crashes consistently when awakening from suspend
Summary: Kwin compositor crashes consistently when awakening from suspend
Status: RESOLVED DUPLICATE of bug 399499
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.14.4
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-25 21:49 UTC by Buck Shockley
Modified: 2018-12-30 23:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Kwin backtrace (8.01 KB, text/plain)
2018-12-30 21:03 UTC, Buck Shockley 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Buck Shockley 2018-12-25 21:49:08 UTC 
SUMMARY
Kwin compositor crashes when awakening from suspend, visually corrupting the lock screen

STEPS TO REPRODUCE
1. Suspend
2. Wake up computer

OBSERVED RESULT
Compositor will crash and restart, showing either a black screen or a visually corrupted background for the lock screen. Some visual corruption occasionally follows to the desktop

EXPECTED RESULT
Compositor does not crash

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.14.4
Qt Version: 5.11.2
KDE Frameworks Version: 5.52.0
Kernel Version: 4.19.12-2-MANJARO
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz
Memory: 15.6 GiB of RAM


ADDITIONAL INFORMATION
Using nvidia driver version 415.25. Using OpenGL 3.1 rendering backend in Compositor settings
Comment 1 Vlad Zahorodnii 2018-12-25 22:24:14 UTC 
Please submit backtrace of the crash. https://community.kde.org/KWin/Debugging
Comment 2 Buck Shockley 2018-12-30 21:03:46 UTC 
Created attachment 117190 [details]
Kwin backtrace
Comment 3 Buck Shockley 2018-12-30 21:04:27 UTC 
My system has since upgrade to kernel 4.20 with Qt version 5.12 and KDE Frameworks 5.53. Bug still persists. See attached backtrace.
Comment 4 David Edmundson 2018-12-30 23:38:46 UTC 

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