Application: spectacle (23.04.2) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.8-200.fc38.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 38.20230705.0 (Kinoite) DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: This is just from this update, a few versions prior it worked normally. Now it doesnt even start, when launching the window and clicking "screenshot" nothing happens. The transparent overlay doeynt show anymore. After crashing the app runs in background and stays there, I have to kill it. Specified App: spectacle-23.04.2-1.fc38.x86_64 --- Software --- OS: Fedora Linux 38.20230705.0 (Kinoite) KDE Plasma: 5.27.6 KDE Frameworks: 5.107.0 Qt: 5.15.10 Kernel: 6.3.8-200.fc38.x86_64 Compositor: wayland --- Hardware --- CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx RAM: 13.5 GB GPU: AMD Radeon Vega 8 Graphics Video memory: 2048MB The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x00005585f2f94055 in QtPrivate::QFunctorSlotObject<SpectacleCore::SpectacleCore(QObject*)::{lambda(QScreen*)#1}, 1, QtPrivate::List<QScreen*>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] () #5 0x00007fe888ce8461 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x00007fe88915f894 in QGuiApplication::screenRemoved(QScreen*) () from /lib64/libQt5Gui.so.5 #7 0x00007fe889194f30 in QScreen::~QScreen() () from /lib64/libQt5Gui.so.5 #8 0x00007fe8891950a5 in QScreen::~QScreen() () from /lib64/libQt5Gui.so.5 #9 0x00007fe88914a3b3 in QWindowSystemInterface::handleScreenRemoved(QPlatformScreen*) () from /lib64/libQt5Gui.so.5 #10 0x00007fe88adca854 in QtWaylandClient::QWaylandDisplay::registry_global_remove(unsigned int) () from /lib64/libQt5WaylandClient.so.5 #11 0x00007fe88a3bcbe6 in ffi_call_unix64 () from /lib64/libffi.so.8 #12 0x00007fe88a3b94bf in ffi_call_int.lto_priv () from /lib64/libffi.so.8 #13 0x00007fe88a3bc18e in ffi_call () from /lib64/libffi.so.8 #14 0x00007fe88b451f0e in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #15 0x00007fe88b452793 in dispatch_event.isra () from /lib64/libwayland-client.so.0 #16 0x00007fe88b452a3c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #17 0x00007fe88adc5b4d in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #18 0x00007fe888cded0b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x00007fe88a5aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x00007fe888cb4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x00007fe888cb7635 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x00007fe888d06c3f in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x00007fe88691339c in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x00007fe886971438 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #25 0x00007fe886910a23 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x00007fe888d06729 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #27 0x00007fe888cb2b4b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #28 0x00007fe888cbaddb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x00005585f2f6d952 in main () [Inferior 1 (process 5214) detached] Reported using DrKonqi
I've been having major issues on Manjaro KDE with the shortcut to capture rectangular area. Mine had a delay over 30 secs every time. What worked for me was disabling the compositor with ALT-SHT-F12, and then it came up properly and instantly. But disabling the compositor is not a workable solution for me. But see if this maybe the same issue.
*** This bug has been marked as a duplicate of bug 469527 ***
*** This bug has been marked as a duplicate of bug 468694 ***