431388 2021-01-10 13:22:15 +0000 Crash in QtWayland::wl_output::handle_geometry 2023-05-21 03:45:52 +0000 1 1 4 Plasma plasmashell generic-multiscreen 5.20.5 openSUSE Linux RESOLVED WORKSFORME https://bugs.kde.org/show_bug.cgi?id=451028 drkonqi, wayland-only NOR crash 1.0 0 jcnengel aleixpol anthony.2lannoy bertil.bonus bmezenga globalunity kde lemmyg nate plasma-bugs-null postix 0 oldest_to_newest 1992813 0 jcnengel 2021-01-10 13:22:15 +0000 Application: systemsettings5 (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.77.0 Operating System: Linux 5.10.4-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I have my laptop's internal display and a second external display connected via USB-C. Whenever kscreen2 is started, the internal display is disabled. Upon trying to reactivate it via KDE settings, this crash happens. The crash can be reproduced every time. -- Backtrace: Application: Systemeinstellungen (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x00000000000000c0 in () #5 0x00007f02f2346f9d in QtWayland::wl_output::handle_geometry(void*, wl_output*, int, int, int, int, int, char const*, char const*, int) (data=0x564f665cd5b0, object=<optimized out>, x=0, y=1080, physical_width=310, physical_height=170, subpixel=0, make=0x564f6d13dd20 "BOE", model=0x564f6d13dd28 "eDP-1-unbekannt", transform=0) at qwayland-wayland.cpp:2207 #6 0x00007f02f195d42d in ffi_call_unix64 () at ../src/x86/unix64.S:106 #7 0x00007f02f19594f9 in ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>) at ../src/x86/ffi64.c:669 #8 0x00007f02f229c8fe in wl_closure_invoke (closure=closure@entry=0x564f6d13dc30, target=<optimized out>, target@entry=0x564f6661b0b0, opcode=opcode@entry=0, data=<optimized out>, flags=<optimized out>) at src/connection.c:1018 #9 0x00007f02f229cfcb in dispatch_event (display=0x564f66618ba0, queue=<optimized out>, queue=<optimized out>) at src/wayland-client.c:1445 #10 0x00007f02f229d19c in dispatch_queue (queue=0x564f66618c70, display=0x564f66618ba0) at src/wayland-client.c:1591 #11 wl_display_dispatch_queue_pending (display=0x564f66618ba0, queue=0x564f66618c70) at src/wayland-client.c:1833 #12 0x00007f02f229d1ec in wl_display_dispatch_pending (display=<optimized out>) at src/wayland-client.c:1896 #13 0x00007f02f2325c2b in QtWaylandClient::QWaylandDisplay::flushRequests() (this=0x564f665cee40) at qwaylanddisplay.cpp:221 #14 0x00007f02f49e0900 in doActivate<false>(QObject*, int, void**) (sender=0x564f6668c5f0, signal_index=4, argv=0x7fff0e59f060, argv@entry=0x0) at kernel/qobject.cpp:3898 #15 0x00007f02f49d9c20 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x564f6668c5f0, m=m@entry=0x7f02f4c8e0e0 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #16 0x00007f02f49a6e83 in QAbstractEventDispatcher::awake() (this=this@entry=0x564f6668c5f0) at .moc/moc_qabstracteventdispatcher.cpp:149 #17 0x00007f02f4a0187c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x564f6668c5f0, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #18 0x00007f02f49a8cab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fff0e59f180, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x00007f02f49b0f20 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x0000564f6496d003 in main(int, char**) (argc=<optimized out>, argv=0x7fff0e59f2a0) at /usr/src/debug/systemsettings5-5.20.5-1.1.x86_64/app/main.cpp:209 [Inferior 1 (process 8949) detached] Possible duplicates by query: bug 429407, bug 419493, bug 416253, bug 377347, bug 377346. Reported using DrKonqi 2006500 1 nate 2021-02-25 21:11:46 +0000 *** This bug has been marked as a duplicate of bug 422418 *** 2006503 2 nate 2021-02-25 21:13:06 +0000 *** Bug 430878 has been marked as a duplicate of this bug. *** 2006505 3 nate 2021-02-25 21:13:45 +0000 *** Bug 432560 has been marked as a duplicate of this bug. *** 2006507 4 nate 2021-02-25 21:13:49 +0000 *** Bug 431842 has been marked as a duplicate of this bug. *** 2055928 5 kde 2021-08-24 13:52:06 +0000 *** Bug 436024 has been marked as a duplicate of this bug. *** 2098352 6 lemmyg 2022-01-26 15:13:09 +0000 moving to confirmed 2106629 7 nicolas.fella 2022-02-20 14:04:29 +0000 *** Bug 450604 has been marked as a duplicate of this bug. *** 2106631 8 nicolas.fella 2022-02-20 14:04:48 +0000 *** Bug 450557 has been marked as a duplicate of this bug. *** 2146111 9 postix 2022-08-16 13:38:02 +0000 Isn't this report basically about the same underlying issue as bug #451028 and as such a duplicate or are they distinct enough to track both separately? 2224334 10 nate 2023-04-21 15:37:02 +0000 An enormous amount of multimonitor fixes went into Plasma 5.27; any chance you could check to see if *this specific crash* is still an issue in Plasma 5.27.4 or newer? Thanks! 2228365 11 bug-janitor 2023-05-06 03:46:11 +0000 Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! 2232172 12 bug-janitor 2023-05-21 03:45:52 +0000 This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!