I recently purchased an LG UltraGear 27GS60QC-B monitor and have been using it with a DisplayPort connection. My previous monitor, a Samsung S20B315B plus, was connected via DVI. Today, I decided to compare both monitors side-by-side and reconnected the old monitor for a test. The following issues occurred during and after the comparison: 1. After connecting the Samsung monitor, the display went black and the system froze. 2. I disconnected the old monitor, and after 1-2 minutes, the system recovered. 3. However, several applications (Firefox, Inkscape, Telegram Desktop) appeared to be crashed or functionally impaired, while only "Konsole" and "Dolphin" continued to work normally. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION: ``` Mar 06 14:18:09 unrivaled plasmashell[1121]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0 Mar 06 14:19:07 unrivaled kded6[1069]: Service ":1.525" unregistered Mar 06 14:19:10 unrivaled plasmashell[1121]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. Mar 06 14:19:11 unrivaled plasmashell[1121]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. Mar 06 14:19:12 unrivaled rtkit-daemon[869]: Successfully made thread 119794 of process 1775 owned by '1000' RT at priority 20. Mar 06 14:19:12 unrivaled rtkit-daemon[869]: Supervising 11 threads of 8 processes of 1 users. Mar 06 14:19:12 unrivaled kded6[1069]: Registering ":1.527/StatusNotifierItem" to system tray Mar 06 14:19:12 unrivaled plasmashell[1121]: QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0 Mar 06 14:20:18 unrivaled kded6[1069]: Service ":1.527" unregistered Mar 06 14:21:00 unrivaled kwin_wayland[915]: kwin_core: Applying output config failed! Mar 06 14:21:00 unrivaled kwin_wayland_wrapper[915]: KCrash: Application 'kwin_wayland' crashing... crashRecursionCounter = 2 Mar 06 14:21:00 unrivaled systemd-coredump[119831]: Process 915 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing... Mar 06 14:21:00 unrivaled systemd[1]: Created slice Slice /system/drkonqi-coredump-processor. Mar 06 14:21:00 unrivaled systemd[1]: Created slice Slice /system/systemd-coredump. Mar 06 14:21:00 unrivaled systemd[1]: Started Process Core Dump (PID 119831/UID 0). Mar 06 14:21:00 unrivaled systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. Mar 06 14:21:03 unrivaled systemd-coredump[119832]: [🡕] Process 915 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 915: #0 0x00007702a4ea5624 n/a (n/a + 0x0) #1 0x00007702a4e4bba0 n/a (n/a + 0x0) #2 0x00007702a872c4da n/a (n/a + 0x0) #3 0x00007702a4e4bcd0 n/a (n/a + 0x0) #4 0x00007702a823a7eb n/a (n/a + 0x0) #5 0x00007702a823c509 n/a (n/a + 0x0) #6 0x00007702a7f7ae40 n/a (n/a + 0x0) #7 0x00007702a55b1a49 n/a (n/a + 0x0) #8 0x00007702a7f90a45 n/a (n/a + 0x0) #9 0x00007702a7f95013 n/a (n/a + 0x0) #10 0x00007702a55b1a49 n/a (n/a + 0x0) #11 0x00007702a55baa75 n/a (n/a + 0x0) #12 0x00007702a55a2ef9 n/a (n/a + 0x0) #13 0x00007702a68ff0ca n/a (n/a + 0x0) #14 0x00007702a5555b00 n/a (n/a + 0x0) #15 0x00007702a56d5aff n/a (n/a + 0x0) #16 0x00007702a56de408 n/a (n/a + 0x0) #17 0x00007702a6261d93 n/a (n/a + 0x0) #18 0x00007702a55606a6 n/a (n/a + 0x0) #19 0x00007702a55591d6 n/a (n/a + 0x0) #20 0x00005cae6c1ac07f n/a (n/a + 0x0) #21 0x00007702a4e35488 n/a (n/a + 0x0) #22 0x00007702a4e3554c n/a (n/a + 0x0) #23 0x00005cae6c1b23f5 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 Mar 06 14:21:04 unrivaled systemd[1]: systemd-coredump@0-119831-0.service: Deactivated successfully. Mar 06 14:21:04 unrivaled systemd[1]: systemd-coredump@0-119831-0.service: Consumed 1.550s CPU time, 1G memory peak. Mar 06 14:21:04 unrivaled drkonqi-coredump-processor[119833]: "/usr/bin/kwin_wayland" 915 "/var/lib/systemd/coredump/core.kwin_wayland.1000.1574c48b6cf049e6ad7943efa0c6684e.915.1741258260000000.zst" Mar 06 14:21:04 unrivaled systemd[831]: Started Launch DrKonqi for a systemd-coredump crash (PID 119833/UID 0). Mar 06 14:21:04 unrivaled inkscape[46296]: Error reading events from display: Broken pipe Mar 06 14:21:04 unrivaled konsole[46395]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled konsole[46395]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled systemsettings[99133]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled systemsettings[99133]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled kwin_wayland_wrapper[997]: (EE) failed to read Wayland events: Broken pipe Mar 06 14:21:04 unrivaled kiod6[30129]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled kiod6[30129]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled dolphin[65174]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled krunner[3512]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled dolphin[65174]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled xdg-desktop-por[1392]: Error reading events from display: Broken pipe Mar 06 14:21:04 unrivaled xdg-desktop-portal-kde[1507]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled kwalletd6[847]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled kwalletd6[847]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled systemsettings[99133]: Failed to write to the pipe: Bad file descriptor. Mar 06 14:21:04 unrivaled systemsettings[99133]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 06 14:21:04 unrivaled kwalletd6[847]: Failed to write to the pipe: Bad file descriptor. Mar 06 14:21:04 unrivaled telegram-desktop[1775]: The Wayland connection broke during blocking read event. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled kwalletd6[847]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 06 14:21:04 unrivaled DiscoverNotifier[1399]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled DiscoverNotifier[1399]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled kgpg[1404]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled kgpg[1404]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled kiod6[30129]: Failed to write to the pipe: Bad file descriptor. Mar 06 14:21:04 unrivaled kiod6[30129]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 06 14:21:04 unrivaled kalarm[1713]: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled kalarm[1713]: qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled kalarm[1713]: Failed to write to the pipe: Bad file descriptor. Mar 06 14:21:04 unrivaled kalarm[1713]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 06 14:21:04 unrivaled konsole[46395]: Failed to write to the pipe: Bad file descriptor. Mar 06 14:21:04 unrivaled konsole[46395]: qt.qpa.wayland: There are no outputs - creating placeholder screen Mar 06 14:21:04 unrivaled kdeconnectd[1383]: 2025-03-06T14:21:04 default: The Wayland connection broke. Did the Wayland compositor die? Mar 06 14:21:04 unrivaled kdeconnectd[1383]: 2025-03-06T14:21:04 qt.qpa.wayland: Attempting wayland reconnect Mar 06 14:21:04 unrivaled polkit-kde-authentication-agent-1[1191]: The Wayland connection broke. Did the Wayland compositor die? ``` full log is here: https://paste.ubuntu-ir.org/oenu
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: all of them, #0-#23 Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
(In reply to cwo from comment #1) > Thank you for the bug report! Unfortunately I can't reproduce the crash > myself on current git master, and the backtrace is incomplete and missing > debug symbols for the following lines that we need to figure out exactly > what's going wrong: > > all of them, #0-#23 > > Could you please install debug symbols and attach a new symbolicated > backtrace generated by using coredumpctl gdb in a terminal window? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for details about how to do this. Thanks again! # coredumpctl --reverse TIME PID UID GID SIG COREFILE EXE SIZE Mon 2025-03-10 21:30:03 +0330 365291 1000 1000 SIGSEGV present /usr/bin/kdenlive 43.4M Sat 2025-03-08 22:36:09 +0330 145223 1000 1000 SIGSEGV present /usr/bin/telegram-desktop 266M Sat 2025-03-08 18:20:23 +0330 275828 1000 1000 SIGSEGV present /usr/bin/gwenview 8.8M Sat 2025-03-08 18:20:23 +0330 276579 1000 1000 SIGSEGV present /usr/bin/gwenview 8.8M Sat 2025-03-08 18:20:23 +0330 277136 1000 1000 SIGSEGV present /usr/bin/gwenview 9M Sat 2025-03-08 18:20:23 +0330 274840 1000 1000 SIGSEGV present /usr/bin/gwenview 8M Sat 2025-03-08 18:20:23 +0330 277234 1000 1000 SIGSEGV present /usr/bin/gwenview 9.1M Sat 2025-03-08 18:20:22 +0330 276767 1000 1000 SIGSEGV present /usr/bin/gwenview 8.8M Sat 2025-03-08 18:20:22 +0330 276081 1000 1000 SIGSEGV present /usr/bin/gwenview 8.8M Sat 2025-03-08 18:20:22 +0330 275676 1000 1000 SIGSEGV present /usr/bin/gwenview 8.9M Sat 2025-03-08 18:20:15 +0330 119887 1000 1000 SIGABRT inaccessible /usr/bin/kwin_wayland - Thu 2025-03-06 20:18:37 +0330 120623 1000 1000 SIGSEGV present /usr/bin/telegram-desktop 232.3M Thu 2025-03-06 14:21:03 +0330 915 1000 1000 SIGSEGV inaccessible /usr/bin/kwin_wayland - Fri 2025-02-28 14:26:18 +0330 133125 1000 1000 SIGABRT present /usr/bin/telegram-desktop 467.4M So when I ran "coredumpctl gdb 915" it gave me: PID: 915 (kwin_wayland) UID: 1000 (artin) GID: 1000 (artin) Signal: 11 (SEGV) Timestamp: Thu 2025-03-06 14:21:00 +0330 (4 days ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_aEiyhS --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-kwin_wayland.service Slice: user-1000.slice Owner UID: 1000 (artin) Boot ID: 1574c48b6cf049e6ad7943efa0c6684e Machine ID: 1b64070a32284972a03c08784b7c49f0 Hostname: unrivaled Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.1574c48b6cf049e6ad7943efa0c6684e.915.1741258260000000.zst (present) Size on Disk: 24.2M Message: Process 915 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 915: #0 0x00007702a4ea5624 n/a (n/a + 0x0) #1 0x00007702a4e4bba0 n/a (n/a + 0x0) #2 0x00007702a872c4da n/a (n/a + 0x0) #3 0x00007702a4e4bcd0 n/a (n/a + 0x0) #4 0x00007702a823a7eb n/a (n/a + 0x0) #5 0x00007702a823c509 n/a (n/a + 0x0) #6 0x00007702a7f7ae40 n/a (n/a + 0x0) #7 0x00007702a55b1a49 n/a (n/a + 0x0) #8 0x00007702a7f90a45 n/a (n/a + 0x0) #9 0x00007702a7f95013 n/a (n/a + 0x0) #10 0x00007702a55b1a49 n/a (n/a + 0x0) #11 0x00007702a55baa75 n/a (n/a + 0x0) #12 0x00007702a55a2ef9 n/a (n/a + 0x0) #13 0x00007702a68ff0ca n/a (n/a + 0x0) #14 0x00007702a5555b00 n/a (n/a + 0x0) #15 0x00007702a56d5aff n/a (n/a + 0x0) #16 0x00007702a56de408 n/a (n/a + 0x0) #17 0x00007702a6261d93 n/a (n/a + 0x0) #18 0x00007702a55606a6 n/a (n/a + 0x0) #19 0x00007702a55591d6 n/a (n/a + 0x0) #20 0x00005cae6c1ac07f n/a (n/a + 0x0) #21 0x00007702a4e35488 n/a (n/a + 0x0) #22 0x00007702a4e3554c n/a (n/a + 0x0) #23 0x00005cae6c1b23f5 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 GNU gdb (GDB) 16.2 Copyright (C) 2024 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/kwin_wayland... (No debugging symbols found in /usr/bin/kwin_wayland) warning: Can't open file /memfd:wayland-cursor (deleted) during file-backed mapping note processing warning: Can't open file /memfd:kwayland-shared (deleted) during file-backed mapping note processing warning: Can't open file /memfd:unknown-usage:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /home/artin/.cache/plasma_theme_default.kcache (deleted) during file-backed mapping note processing warning: Can't open file /memfd:wayland-shm (deleted) during file-backed mapping note processing warning: Can't open file /memfd:gdk-wayland (deleted) during file-backed mapping note processing warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /memfd:JITCode:QtQml (deleted) during file-backed mapping note processing [New LWP 915] [New LWP 946] [New LWP 954] [New LWP 1203] [New LWP 986] [New LWP 957] [New LWP 989] [New LWP 961] [New LWP 944] [New LWP 925] [New LWP 1213] [New LWP 947] [New LWP 1218] [New LWP 948] [New LWP 953] [New LWP 1187] [New LWP 955] [New LWP 68738] [New LWP 1224] [New LWP 988] [New LWP 1204] [New LWP 956] [New LWP 987] [New LWP 949] [New LWP 1202] [New LWP 945] [New LWP 1225] [New LWP 950] [New LWP 985] [New LWP 1300] [New LWP 102043] [New LWP 68739] [New LWP 102042] [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_aEiyhS --xwayland'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007702a4ea5624 in ?? () from /usr/lib/libc.so.6 [Current thread is 1 (Thread 0x77029ee0ca40 (LWP 915))] (gdb)
Hm, this didn't add any symbols apparently. I'm not too familiar with Arch and what might have gone wrong here unfortunately. Resetting this to Reported so that someone else can have a look, but there might not be anything we can do here. There are some fixes for crashes that can appear with multi-monitor setups coming in 6.3.3 in a few hours; these also tend to contain some of the log lines that are in your crash (but that's only a very weak indicator as they are so generic, a backtrace would really help in identifying them).
IIRC you need to install debuginfod to get debug info for Arch packages
Based on the textual description of the problem, I suspect this may be Bug 499383, but we need a backtrace with at least *some* debug symbols to be able to determine that.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.