Bug 456232 - Spectacle crashes when I switch to "capture window underneath cursor" (does not usually crash)
Summary: Spectacle crashes when I switch to "capture window underneath cursor" (does n...
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 22.04.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-07-02 08:30 UTC by David Tonhofer
Modified: 2023-11-27 17:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Tonhofer 2022-07-02 08:30:26 UTC
Application: spectacle (22.04.1)

Qt Version: 5.15.3
Frameworks Version: 5.94.0
Operating System: Linux 5.18.7-200.fc36.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:

Switched to "capture window underneath cursor"
About to perform capture

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault

[KCrash Handler]
#4  0x000055f89955dee3 in PlatformXcb::getWindowUnderCursor (this=0x55f89b29d5b0) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Platforms/PlatformXcb.cpp:238
#5  0x000055f899560298 in PlatformXcb::grabTransientWithParent (theIncludeDecorations=true, theIncludePointer=false, this=0x55f89b29d5b0) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Platforms/PlatformXcb.cpp:585
#6  PlatformXcb::doGrabNow (this=0x55f89b29d5b0, theGrabMode=<optimized out>, theIncludePointer=<optimized out>, theIncludeDecorations=true) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Platforms/PlatformXcb.cpp:698
#7  0x00007f54a6c18066 in QtPrivate::QSlotObjectBase::call (a=0x7ffe1e2e6f70, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  QSingleShotTimer::timerEvent (this=0x55f89b91fef0) at kernel/qtimer.cpp:320
#9  0x00007f54a6c0b525 in QObject::event (this=0x55f89b91fef0, e=0x7ffe1e2e70c0) at kernel/qobject.cpp:1336
#10 0x00007f54a76afc82 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55f89b91fef0, e=0x7ffe1e2e70c0) at kernel/qapplication.cpp:3637
#11 0x00007f54a6be1658 in QCoreApplication::notifyInternal2 (receiver=0x55f89b91fef0, event=0x7ffe1e2e70c0) at kernel/qcoreapplication.cpp:1064
#12 0x00007f54a6c31681 in QTimerInfoList::activateTimers (this=0x55f89b2927b0) at kernel/qtimerinfo_unix.cpp:643
#13 0x00007f54a6c31f5c in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#14 0x00007f54a479efaf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#15 0x00007f54a47f42c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#16 0x00007f54a479c940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#17 0x00007f54a6c322fa in QEventDispatcherGlib::processEvents (this=0x55f89b288140, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#18 0x00007f54a6be00ba in QEventLoop::exec (this=this@entry=0x7ffe1e2e7360, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#19 0x00007f54a6be8162 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#20 0x00007f54a7025ee0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1860
#21 0x00007f54a76afbf9 in QApplication::exec () at kernel/qapplication.cpp:2829
#22 0x000055f89952ce86 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/spectacle-22.04.1-1.fc36.x86_64/src/Main.cpp:112
[Inferior 1 (process 46086) detached]

Reported using DrKonqi
Comment 1 Noah Davis 2023-11-22 14:47:05 UTC
I think I might have encountered this before. It happened when the window couldn't be gotten fast enough. Unfortunately, I don't have enough info to confirm this report and the code has changed a lot, so the backtrace isn't very useful anymore. Do you still have this bug?
Comment 2 David Tonhofer 2023-11-26 18:37:07 UTC
Thank you,

A cursory check indicates that the bug does not currently occur. I guess this can be closed ... 

I'm still running:

Fedora 36: 6.2.15-100.fc36.x86_64
with Qt 5.15.8
with spectacle-22.12.0-1.fc36.x86_64

Best regards,

-- David