Bug 470009 - Crashed when disabling primary monitor
Summary: Crashed when disabling primary monitor
Status: RESOLVED DUPLICATE of bug 468694
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 23.04.1
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-05-19 16:14 UTC by Daisy Thomas
Modified: 2023-08-11 17:02 UTC (History)
2 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 Daisy Thomas 2023-05-19 16:14:36 UTC
Application: spectacle (23.04.1)

Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.2-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
While spectacle was open in the background, I used the KDE system settings to disable the primary monitor and exclusively use my second monitor. This is when spectacle crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Spectacle (spectacle), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>}
[KCrash Handler]
#6  0x0000000000000020 in  ()
#7  0x00007f8a8fcbeb41 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffdc735c5f0, r=<optimized out>, this=0x5608924612f0, this=<optimized out>, r=<optimized out>, a=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false>(QObject*, int, void**) (sender=0x7ffdc735d050, signal_index=10, argv=0x7ffdc735c5f0) at kernel/qobject.cpp:3923
#9  0x00007f8a901420e7 in QGuiApplication::screenRemoved(QScreen*) (this=<optimized out>, _t1=<optimized out>) at .moc/moc_qguiapplication.cpp:396
#10 0x00007f8a9016a994 in QScreen::~QScreen() (this=0x56089347fa40, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:116
#11 0x00007f8a901289e7 in QScreen::~QScreen() (this=0x56089347fa40, this=<optimized out>) at kernel/qscreen.cpp:140
#12 QWindowSystemInterface::handleScreenRemoved(QPlatformScreen*) (platformScreen=0x560892749610) at kernel/qwindowsysteminterface.cpp:844
#13 0x00007f8a91d387be in QtWaylandClient::QWaylandDisplay::registry_global_remove(unsigned int) (this=0x5608923ae860, id=59) at /usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddisplay.cpp:571
#14 0x00007f8a90c174f6 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#15 0x00007f8a90c13f5e in ffi_call_int (cif=cif@entry=0x7ffdc735c8b0, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#16 0x00007f8a90c16b73 in ffi_call (cif=cif@entry=0x7ffdc735c8b0, fn=<optimized out>, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffdc735c980) at ../src/x86/ffi64.c:710
#17 0x00007f8a923a9645 in wl_closure_invoke (closure=closure@entry=0x7f8a70003e60, target=<optimized out>, target@entry=0x5608923b28f0, opcode=opcode@entry=1, data=<optimized out>, flags=1) at ../wayland-1.22.0/src/connection.c:1025
#18 0x00007f8a923a9e73 in dispatch_event (display=display@entry=0x5608923b2770, queue=0x5608923b2860) at ../wayland-1.22.0/src/wayland-client.c:1631
#19 0x00007f8a923aa13c in dispatch_queue (queue=0x5608923b2860, display=0x5608923b2770) at ../wayland-1.22.0/src/wayland-client.c:1777
#20 wl_display_dispatch_queue_pending (display=0x5608923b2770, queue=0x5608923b2860) at ../wayland-1.22.0/src/wayland-client.c:2019
#21 0x00007f8a91d33c06 in QtWaylandClient::QWaylandDisplay::flushRequests() (this=<optimized out>) at /usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddisplay.cpp:255
#22 0x00007f8a8fcb1c80 in QObject::event(QEvent*) (this=0x5608923ae860, e=0x7f8a6c001a60) at kernel/qobject.cpp:1347
#23 0x00007f8a91578b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x5608923ae860, e=0x7f8a6c001a60) at kernel/qapplication.cpp:3640
#24 0x00007f8a8fc8e028 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5608923ae860, event=0x7f8a6c001a60) at kernel/qcoreapplication.cpp:1064
#25 0x00007f8a8fc8e093 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1462
#26 0x00007f8a8fc8eb33 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x5608923a96f0) at kernel/qcoreapplication.cpp:1821
#27 0x00007f8a8fcd4f58 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5608923c4ae0) at kernel/qeventdispatcher_glib.cpp:277
#28 0x00007f8a8d90f53b in g_main_dispatch (context=0x7f8a74000ee0) at ../glib/glib/gmain.c:3460
#29 g_main_context_dispatch (context=0x7f8a74000ee0) at ../glib/glib/gmain.c:4200
#30 0x00007f8a8d96c219 in g_main_context_iterate.constprop.0 (context=0x7f8a74000ee0, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4276
#31 0x00007f8a8d90e1a2 in g_main_context_iteration (context=0x7f8a74000ee0, may_block=1) at ../glib/glib/gmain.c:4343
#32 0x00007f8a8fcd8d3c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x560892392a10, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#33 0x00007f8a8fc8668c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ffdc735cf60, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#34 0x00007f8a8fc912f9 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#35 0x00007f8a9013b052 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1870
#36 0x00007f8a91576f2a in QApplication::exec() () at kernel/qapplication.cpp:2832
#37 0x00005608909e3b65 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/spectacle/spectacle-23.04.1/src/Main.cpp:127
[Inferior 1 (process 3913) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2023-05-19 19:43:39 UTC

*** This bug has been marked as a duplicate of bug 469527 ***
Comment 2 Nate Graham 2023-08-11 17:02:32 UTC

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