Arch Linux

dschopf

Member

Registered: 2021-03-15

Posts: 2

Xrdp fails due to /dev/dri/card0: Operation not permitted

My remote connection has been working reliably for quite some time but broke on Friday last week. I tried to identify the package upgrades which might cause this but I could not find any.

In my .xorgxrdp.11.log I can see the following

[   548.226] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted

and startplasma-x11 is stuck here:

#0  0x00007f268e10f347 in poll () from /usr/lib/libc.so.6
#1  0x00007f268dfa27b4 in ?? () from /usr/lib/libxcb.so.1
#2  0x00007f268dfa0465 in xcb_connect_to_fd () from /usr/lib/libxcb.so.1
#3  0x00007f268dfa45c4 in xcb_connect_to_display_with_auth_info () from /usr/lib/libxcb.so.1
#4  0x00007f268ec2042b in _XConnectXCB () from /usr/lib/libX11.so.6
#5  0x00007f268ec10b29 in XOpenDisplay () from /usr/lib/libX11.so.6
#6  0x0000563e4d29abf9 in ?? ()
#7  0x0000563e4d2960be in ?? ()
#8  0x00007f268e042b25 in __libc_start_main () from /usr/lib/libc.so.6
#9  0x0000563e4d29649e in ?? ()

I have tried all potential solutions for this (known) issue from the forums and the systemd issue tracker: https://github.com/systemd/systemd/issues/14322
but nothing helps.

Adding

ExecStartPre=/bin/ls -l /dev/dri

to systemd-logind.service shows that that device is already up by the time systemd-logind is started:

Mar 15 09:17:24 <> systemd[1]: Starting User Login Management...
Mar 15 09:17:24 <> ls[570]: total 0
Mar 15 09:17:24 <> ls[570]: drwxr-xr-x 2 root root         80 Mar 15 09:17 by-path
Mar 15 09:17:24 <> ls[570]: crw-rw---- 1 root video  226,   0 Mar 15 09:17 card0
Mar 15 09:17:24 <> ls[570]: crw-rw-rw- 1 root render 226, 128 Mar 15 09:17 renderD128
Mar 15 09:17:24 <> systemd-logind[593]: New seat seat0.
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event2: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event1: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event0: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event4: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event10: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event11: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event12: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event13: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event7: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event8: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event9: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event6: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to pin reserved VT: Operation not permitted
Mar 15 09:17:24 <> systemd[1]: Started User Login Management.
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event15: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event18: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event19: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event16: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event14: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event17: Operation not permitted
Mar 15 09:17:24 <> systemd-logind[593]: Failed to open /dev/input/event20: Operation not permitted
Mar 15 09:17:27 <> systemd-logind[593]: Failed to open file system "/dev/block/8:1": Operation not permitted
Mar 15 09:17:58 <> systemd-logind[593]: New session 2 of user dschopf.

And setting

DevicePolicy=auto

also did not help.

Drm seems to be loaded properly

$ dmesg | grep drm
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=31337353-ad76-4e79-a1aa-047300d81207 rw loglevel=3 quiet nvidia-drm.modeset=1
[    0.049196] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=31337353-ad76-4e79-a1aa-047300d81207 rw loglevel=3 quiet nvidia-drm.modeset=1
[    1.392076] [drm] [nvidia-drm] [GPU ID 0x00006500] Loading driver
[    2.521874] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:65:00.0 on minor 0
[    3.888871] systemd[1]: Starting Load Kernel Module drm...
[    3.897186] systemd[1]: modprobe@drm.service: Succeeded.
[    3.897388] systemd[1]: Finished Load Kernel Module drm.

Currently I am running testing/systemd 247.4-2, downgrading to systemd-247.3 did not resolve the issue.

dschopf

Member

Registered: 2021-03-15

Posts: 2

Re: Xrdp fails due to /dev/dri/card0: Operation not permitted

I have found out that downgrading mesa from 21.0.0-1 to 20.3.4-3 fixes this issue.