https://bugs.kde.org/show_bug.cgi?id=478616
--- Comment #7 from Stefan Hoffmeister <stefan.hoffmeis...@econos.de> --- This does not seem to be related to NVIDIA. Right now I suspect multi-monitor support on the Intel 11800H iGPU (there is a 4K screen attached to that GPU, but the monitor has been working very fine going through all of the Plymouth "nice animated system boot" graphics fun) Reason: I have now had a cold boot on this notebook (power on after having been turned off for six hours) and got the same problem, again. With more logging enabled, it is now clear that systemd_logind simply does not respond in time: * 09:35:52 - kwin_wayland (apparently) sends the TakeDevice request via dbus * 09:35:52 - systemd_logind acks request [25 secs after request] * 09:36:17 - kwin_wayland gives up waiting, "Failed to open /dev/dri/card0 device"; sddm is toast [34 secs after request] * 09:36:26 - systemd_logind sends response, apparently a success ``` Dec 20 09:35:52 dell.home systemd[2417]: Started dbus-broker.service - D-Bus User Message Bus. Dec 20 09:35:52 dell.home dbus-broker-launch[2448]: Ready Dec 20 09:35:52 dell.home systemd-logind[1531]: Got message type=method_call sender=:1.36 destination=org.freedesktop.login1 path=/org/freedesktop/login1/session/c1 interface=org.freedesktop.login1.Session member=TakeDevice cookie=15 reply_cookie=0 signature=uu error-name=n/a error-message=n/a Dec 20 09:35:54 dell.home kernel: thunderbolt 0-1: new device found, vendor=0x16b device=0x9010 Dec 20 09:35:54 dell.home kernel: thunderbolt 0-1: i-tec TB3CDUALDPDOCKPD Dec 20 09:35:54 dell.home boltd[1725]: [004158c8-bd26-TB3CDUALDPDOCKPD ] parent is f07211eb-5a97... Dec 20 09:35:54 dell.home boltd[1725]: [004158c8-bd26-TB3CDUALDPDOCKPD ] connected: authorized (/sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/0-1) Dec 20 09:35:54 dell.home boltd[1725]: [004158c8-bd26-TB3CDUALDPDOCKPD ] udev: device changed: authorized -> authorized Dec 20 09:36:01 dell.home systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Dec 20 09:36:01 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 20 09:36:17 dell.home sddm-helper-start-wayland[2433]: "kwin_core: Failed to open /dev/dri/card0 device (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)\nkwin_waylan> Dec 20 09:36:17 dell.home sddm-greeter[2444]: Creating a fake screen in order for Qt not to crash Dec 20 09:36:17 dell.home sddm-greeter[2444]: The Wayland connection broke. Did the Wayland compositor die? Dec 20 09:36:17 dell.home sddm-helper-start-wayland[2433]: Stopping... "/usr/bin/sddm-greeter" Dec 20 09:36:17 dell.home sddm-helper[2323]: pam_unix(sddm-greeter:session): session closed for user sddm ... Dec 20 09:36:26 dell.home systemd-logind[1531]: Sent message type=method_return sender=n/a destination=:1.36 path=n/a interface=n/a member=n/a cookie=73 reply_cookie=15 signature=hb error-name=n/a error-message=n/a ``` -- You are receiving this mail because: You are watching all bug changes.
