| Summary: | kwin crashes on active window screenshot (X11) | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Mikel Pérez <io> |
| Component: | general | Assignee: | Vlad Zahorodnii <vlad.zahorodnii> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | me, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.15.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Mikel Pérez
2019-05-10 01:40:28 UTC
it takes a proper window-shot and doesn't crash with GTK apps tho (!!) Hmm, I thought it was fixed. Will look into it. Backtrace of the crash:
(lldb) bt
* thread #1, name = 'kwin_x11', stop reason = signal SIGABRT
* frame #0: 0x00007fcff0b1d82f libc.so.6`__GI_raise + 271
frame #1: 0x00007fcff0b08672 libc.so.6`__GI_abort + 293
frame #2: 0x00007fcff10408b2 libQt5Core.so.5`::qt_message_fatal((null)=<unavailable>, context=<unavailable>, message=<unavailable>) at qlogging.cpp:1904:15
frame #3: 0x00007fcff10414fd libQt5Core.so.5`QMessageLogger::fatal(this=<unavailable>, msg=<unavailable>) const at qlogging.cpp:888:21
frame #4: 0x00007fcff1039ca6 libQt5Core.so.5`qt_assert(assertion=<unavailable>, file=<unavailable>, line=<unavailable>) at qglobal.cpp:3254:46
frame #5: 0x00007fcfdbf1ba8c KWinSceneOpenGL.so`KWin::DecorationShadowTextureCache::~DecorationShadowTextureCache(this=0x00007fcfdbf41e60) at scene_opengl.cpp:2035:5
frame #6: 0x00007fcff0b1ff2c libc.so.6`__run_exit_handlers + 316
frame #7: 0x00007fcff0b2005e libc.so.6`__GI_exit + 30
frame #8: 0x00007fcfeaf55550 libQt5XcbQpa.so.5`QXcbConnection::processXcbEvents(this=0x00005555d4b8dcd0, flags=(i = 36)) at qxcbconnection.cpp:1003:13
frame #9: 0x00007fcfeaf878e0 libQt5XcbQpa.so.5`QXcbUnixEventDispatcher::processEvents(this=0x00005555d4be6ee0, flags=(i = 36)) at qxcbeventdispatcher.cpp:61:35
frame #10: 0x00007fcff121dea5 libQt5Core.so.5`QEventLoop::processEvents(this=<unavailable>, flags=<unavailable>) at qeventloop.cpp:138:64
frame #11: 0x00007fcff121e2fd libQt5Core.so.5`QEventLoop::exec(this=0x00007ffe4e928790, flags=(i = 0)) at qeventloop.cpp:225:22
frame #12: 0x00007fcff12285fa libQt5Core.so.5`QCoreApplication::exec() at qcoreapplication.cpp:1368:36
frame #13: 0x00007fcff160cc02 libQt5Gui.so.5`QGuiApplication::exec() at qguiapplication.cpp:1788:34
frame #14: 0x00007fcff1c4ffb9 libQt5Widgets.so.5`QApplication::exec() at qapplication.cpp:2896:33
frame #15: 0x00007fcff521ff51 libkdeinit5_kwin_x11.so`::kdemain(argc=2, argv=0x00007ffe4e928a28) at main_x11.cpp:470:18
frame #16: 0x00005555d347b17b kwin_x11`main(argc=2, argv=0x00007ffe4e928a28) at kwin_x11_dummy.cpp:3:50
frame #17: 0x00007fcff0b09ce3 libc.so.6`__libc_start_main + 243
frame #18: 0x00005555d347b06e kwin_x11`_start + 46
I think that screenshots we're sending using x pixmaps are just too big. @Mikel Do you have a 4K screen? Hmm, I think the only way to fix this is to send screenshots over pipe. *** This bug has been marked as a duplicate of bug 388182 *** |