https://bugs.kde.org/show_bug.cgi?id=478616

            Bug ID: 478616
           Summary: System hangs dead on sddm start: "kwin_core: Failed to
                    open /dev/dri/card0 device (Did not receive a reply.
                    ..."
    Classification: Plasma
           Product: kwin
           Version: 5.27.10
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: core
          Assignee: kwin-bugs-n...@kde.org
          Reporter: stefan.hoffmeis...@econos.de
  Target Milestone: ---

SUMMARY

On Fedora 39 + KDE Plasma 5.27.10 + Wayland on native notebook hardware
including

* NVIDIA 3060 RTX mobile GPU
* Intel Tiger Lake 11800H iGPU

I seem to start getting random system hands on boot to a graphical desktop; the
log then contains
```
Dec 15 18:25:24 dell-7610.home sddm-helper-start-wayland[2560]: "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_wayland_drm: failed to open drm device at
\"/dev/dri/card0\"\n"
```

In such a state, the system simply hangs dead with a blank screen for a handful
of seconds (15? 25?). It will then show on screen the notebook vendor's boot
logo. And stay there. The logs for this are

```
Dec 16 20:19:03 dell.home sddm-helper-start-wayland[2515]: "No backend
specified, automatically choosing drm\n"
...
Dec 16 20:19:30 dell.home sddm-helper-start-wayland[2515]: "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_wayland_drm: failed to open drm device at
\"/dev/dri/card0\"\nkwin_wayland_drm: No suitable DRM devices have been
found\n"
Dec 16 20:19:30 dell.home sddm-greeter[2518]: Creating a fake screen in order
for Qt not to crash
Dec 16 20:19:30 dell.home sddm-greeter[2518]: The Wayland connection broke. Did
the Wayland compositor die?
Dec 16 20:19:30 dell.home sddm-helper-start-wayland[2515]: Stopping...
"/usr/bin/sddm-greeter"
Dec 16 20:19:30 dell.home sddm-helper[2420]: pam_unix(sddm-greeter:session):
session closed for user sddm
```

The "native" GPU sequence (which I cannot change in the BIOS) is, 

* /dev/dri/card0 == Intel
* /dev/dri/card1 == NVIDIA

Now, SDDM has peculiar configuration to force on Wayland and to exclude the
NVIDIA card in /etc/sddm.conf.d/someconfig.conf

```
[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell,KWIN_DRM_DEVICES=/dev/dri/card0
```

Physically connected are
* the notebooks's internal display and an HDMI screen are alive and alight on
Intel GPU (card0)
* a 2.5K screen is on Thunderbolt -> DisplayPort on the NVIDIA GPU  (card1)


STEPS TO REPRODUCE
1. have setup as described above
2. boot

OBSERVED RESULT

Every once in a while, the system hangs dead with the above symptoms.

EXPECTED RESULT

Reliable start to SDDM greeter.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to