Steps to reproduce: 1. Press Print Screen. Spectacle launches. 2. In its settings, select: - Area: Active Window - Delay: On Click checked - Include mouse pointer: unchecked - Include window titlebar and borders: checked - Capture the current popup only: unchecked, greyed out 3. Click Take a New Screenshot. 4. With the cross mouse cursor, click on the panel (e.g. on the task list area). 5. KWin crashes. Kubuntu 18.04, Plasma 5.12.5, KDE Frameworks 5.44.0, Qt 5.9.5.
Please provide a backtrace of the crash.
Apparently, it's not a crash per se but the kwin process exiting. In gdb, when I reproduce the issue, I can see the following: [Thread 0x7f07ad7f4700 (LWP 19391) exited] [Thread 0x7f078df0b700 (LWP 19479) exited] [Thread 0x7f078cd0d700 (LWP 19396) exited] [Thread 0x7f079ee9e700 (LWP 19393) exited] [Thread 0x7f07afe4f700 (LWP 19390) exited] [Thread 0x7f07c9900cc0 (LWP 19389) exited] [Inferior 1 (process 19389) exited with code 01]
Setting a breakpoint on `exit` shows this backtrace: #0 0x00007f760c4e5120 in __GI_exit (status=1) at exit.c:139 #1 0x00007f7602930b05 in _XDefaultIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #2 0x00007f75f405ac97 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #3 0x00007f7602930d3e in _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #4 0x00007f760292e058 in () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #5 0x00007f760292e835 in _XFlush () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #6 0x00007f760290fffa in XFlush () at /usr/lib/x86_64-linux-gnu/libX11.so.6 #7 0x00007f75f010ae5e in KWin::GlxBackend::present() (this=0x56151a4d8c70) at ./plugins/platforms/x11/standalone/glxbackend.cpp:737 #8 0x00007f75f0103059 in KWin::GlxBackend::endRenderingFrame(QRegion const&, QRegion const&) (this=0x56151a4d8c70, renderedRegion=..., damagedRegion=...) at ./plugins/platforms/x11/standalone/glxbackend.cpp:809 #9 0x00007f75dc731587 in KWin::SceneOpenGL::paint(QRegion, QList<KWin::Toplevel*>) () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #10 0x00007f760c109252 in KWin::Compositor::performCompositing() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #11 0x00007f76099930db in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007f760a6e182c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x00007f760a6e90f4 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x00007f76099639a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007f76099bbd8e in QTimerInfoList::activateTimers() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007f76099b9f42 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f75f40c05cd in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #18 0x00007f76099619ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x00007f760996aa84 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007f760c89bdbb in kdemain(int, char**) (argc=<optimized out>, argv=0x7ffd41b452c8) at ./main_x11.cpp:468 #21 0x00007f760c4c3b97 in __libc_start_main (main=0x56151905b730 <main>, argc=1, argv=0x7ffd41b452c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd41b452b8) at ../csu/libc-start.c:310 #22 0x000056151905b76a in _start ()
Could it be that the window you screenshot is rather large. E.g. high dpi display.
The total screen area is 5760x2160, which is two displays (3840x2160 and 1920x1080) combined. The panel I'm clicking on is on the 3840x2160 display. But the screenshot is configured to an Active Window, not the full screen. I'm not sure what is the active window in this case.
Created attachment 119410 [details] A shell log with GDB output, versions, config info, etc. I'm also experiencing this bug in Kubuntu 18.10, with kwin 5.13.5 and Spectacle version 18.04.3. Set up is essentially identical to the previous report. I can add that I have two 4K monitors, and that I'm taking a screenshot of a window that fills perhaps 75% of one of the two monitors. GDB does not produce a useful backtrace (no stack), but does report: The X11 connection broke: Maximum allowed requested length exceeded (code 4) XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 17472 requests (17472 known processed) with 0 events remaining.
*** This bug has been marked as a duplicate of bug 338489 ***