Bug 482940 - Nvidia + additional monitor immediately crashes kwin_wayland
Summary: Nvidia + additional monitor immediately crashes kwin_wayland
Status: REPORTED
Alias: None
Product: kwin
Classification: Plasma
Component: multi-screen (show other bugs)
Version: 6.0.1
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: multiscreen, qt6, wayland
Depends on:
Blocks:
 
Reported: 2024-03-09 02:07 UTC by myristica
Modified: 2024-03-14 13:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Syslog of crash after login when monitor is connected from boot (1.75 MB, text/plain)
2024-03-09 02:07 UTC, myristica
Details
Dmesg of crash after login when monitor is connected from boot (91.28 KB, text/plain)
2024-03-09 02:08 UTC, myristica
Details
Syslog of crash after login when monitor is connected after successful login (1.66 MB, text/plain)
2024-03-09 02:09 UTC, myristica
Details
Dmesg of crash after login when monitor is connected after successful login (91.23 KB, text/plain)
2024-03-09 02:09 UTC, myristica
Details
Backtrace of crash from `coredumpctl gdb` (45.31 KB, text/plain)
2024-03-13 22:12 UTC, myristica
Details

Note You need to log in before you can comment on or make changes to this bug.
Description myristica 2024-03-09 02:07:55 UTC
Created attachment 166751 [details]
Syslog of crash after login when monitor is connected from boot

SUMMARY

Upon having a monitor connected under Wayland and Nvidia proprietary, wayland
and/or kwin_wayland immediately crashes.

Having the monitor disconnected allows normal login and usage. GPU can be used
as normal.

Having the monitor connected, even if it is disabled through KDE settings,
immedietely crashes and sends me back to the login screen. Disconnecting the
monitor allows logging back in without issue. Disconnecting the monitor during
the crash allows plasma to recover, probably from the retries.

Suspending to ram, connecting the monitor, and waking the computer back up does
not have any effect, nor is the monitor recognised as being plugged in.

This monitor works on other computers. I have tried HDMI and HDMI over USB-C,
both with the same result.

Modeset DRM and FBDev are turned on in grub kernel parameters. I have also
attempted these tests with FBDev off and both off. I have also attempted
renaming the kwin settings folder to force a re-generation.

To my knowledge, this did not occur under Plasma 5

This crash does not occur on Nouveau drivers, nor on X11.

Attached are two sets of logs, one with the monitor connected from boot and
logging in, and the other plugging in the monitor after boot and login. Crash
dumps are included within. Debug symbols are being an absolute pain to install,
and are right now not included. I will continue attempting to get a proper
backtrace and will update this post.

STEPS TO REPRODUCE
1. Plug in an external monitor
2. Log into Plasma using wayland
3. (optionally, plug in the monitor here instead)

OBSERVED RESULT
kwin_wayland crashes and user is sent back to the login screen

EXPECTED RESULT
Plasma recognises a monitor is connected and displays an image.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 6.0
(available in About System)
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.0.2
Kernel Version: 6.5.0-25-generic (64-bit)
Nvidia Drivers: 550.54.14 (using an RTX 2070)
Computer name: ROG Strix G731GW_G731GW

ADDITIONAL INFORMATION
These bugs are possibly related: 478700, 477738, 481986
Comment 1 myristica 2024-03-09 02:08:26 UTC
Created attachment 166752 [details]
Dmesg of crash after login when monitor is connected from boot
Comment 2 myristica 2024-03-09 02:09:06 UTC
Created attachment 166753 [details]
Syslog of crash after login when monitor is connected after successful login
Comment 3 myristica 2024-03-09 02:09:23 UTC
Created attachment 166754 [details]
Dmesg of crash after login when monitor is connected after successful login
Comment 4 Nate Graham 2024-03-11 22:14:02 UTC
Even just a clean backtrace all on its own (not interspersed with syslog messages) would be helpful See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 5 myristica 2024-03-13 22:12:38 UTC
Created attachment 167131 [details]
Backtrace of crash from `coredumpctl gdb`

I have attached a plain backtrace from the crash following the guidelines
Comment 6 David Edmundson 2024-03-14 13:54:31 UTC
Pasting inline

           #3  0x000074c9b9a2871b __assert_fail_base (libc.so.6 + 0x2871b)
                #4  0x000074c9b9a39e96 __GI___assert_fail (libc.so.6 + 0x39e96)
                #5  0x000074c9bd30421f n/a (libepoxy.so.0 + 0xc521f)
                #6  0x000074c9bd2b19ba n/a (libepoxy.so.0 + 0x729ba)
                #7  0x000074c9bccf2613 _ZN4KWin10EglContextD1Ev (libkwin.so.6 + 0x2f2613)