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

--- Comment #3 from Stefan Hoffmeister <stefan.hoffmeis...@econos.de> ---
I got the reject on the Intel card ("/dev/dri/card0") again this morning, on a
modified system configuration. I had tried to mitigate this issue by modifying
the following two configuration parts on my system:

* modified sddm configuration to remove KWIN_DRM_DEVICES (i.e. sddm may now use
primary card0 == Intel and card1 == nvidia) - it is still force-configured to
use Wayland
* added all nvidia modules to `/etc/modules-load.d/nvidia.conf` and rebuilt
initramfs via `dracut --regenerate-all --force` (cf `lsinitrd`)

Additionally, other than before, the NVIDIA GPU did not have any output
connected.

In the logs (excerpt below) this is what I see:

* the session for user sddm comes up fine
* dbus-broker.service seems to have successfully started
* there is SELinux denial for sys_admin on systemd-modules (triggered by AVC
`avc:  denied  { sys_admin } for  pid=1483 comm="nv_queue"`), but that would be
NVIDIA matching the nv_queue kernel thread, if at all (and frankly, I suspect
that this is a defect elsewere, because the whole point of systemd-modules _is_
loading modules as an admin?)
* kwin_wayland terminates with an error while trying to get hold of the Intel
card "/dev/dri/card0"
* sddm? kwin? tries again on the NVIDIA card (`sddm-helper-start-wayland[2526]:
"OpenGL vendor string:                   NVIDIA Corporation`)
* sddm-greeter does not find a screen (correct, the NVIDIA GPU does not have a
screen attached, and I don't think it would be reasonable for the NVIDIA GPU to
be able to talk to the apparently not-so-happy Intel GPU at this stage)

So, right now I am mostly interested in maximizing relevant log output from

* sddm
* dbus (traffic)
* systemd-logind (accessing /dev/dri/card0)

in the hope to get more context.

FWIW, I recall one more peculiarity on this system: I am forcing the
non-default Intel GPU firmware loading for guc and huc (`options i915
enable_guc=3`), see https://wiki.archlinux.org/title/intel_graphics . Turning
this off for now.

 ```
Dec 17 08:24:37 dell.home systemd-logind[1684]: New session c1 of user sddm.
Dec 17 08:24:37 dell.home systemd[1]: Started uresourced.service - User
resource assignment daemon.
Dec 17 08:24:37 dell.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=uresourced
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:24:37 dell.home systemd[1]: Finished user-runtime-dir@988.service -
User Runtime Directory /run/user/988.
Dec 17 08:24:37 dell.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user-runtime-dir@988
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:24:37 dell.home systemd[1]: Starting user@988.service - User Manager
for UID 988...
Dec 17 08:24:37 dell.home dbus-broker-launch[1599]: Activation request for
'org.freedesktop.home1' failed: The systemd unit
'dbus-org.freedesktop.home1.service' could not be found.
Dec 17 08:24:37 dell.home audit[2508]: USER_ACCT pid=2508 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:accounting
grantors=pam_unix acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Dec 17 08:24:37 dell.home audit[2508]: CRED_ACQ pid=2508 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=?
acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=failed'
Dec 17 08:24:37 dell.home audit[2508]: USER_ROLE_CHANGE pid=2508 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='pam:
default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 17 08:24:37 dell.home (systemd)[2508]: pam_unix(systemd-user:session):
session opened for user sddm(uid=988) by sddm(uid=0)
Dec 17 08:24:37 dell.home audit[2508]: USER_START pid=2508 uid=0 auid=988 ses=1
subj=system_u:system_r:init_t:s0 msg='op=PAM:session_open
grantors=pam_selinux,pam_selinux,pam_loginuid,pam_keyinit,pam_namespace,pam_systemd_home,pam_umask,pam_keyinit,pam_limits,pam_systemd,pam_unix
acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:24:37 dell.home uresourced[2484]: Setting resources on user.slice
(MemoryMin: 262144000, MemoryLow: 0, CPUWeight: -, IOWeight: -)
Dec 17 08:24:37 dell.home uresourced[2484]: Setting resources on user-988.slice
(MemoryMin: 262144000, MemoryLow: 0, CPUWeight: 500, IOWeight: 500)
Dec 17 08:24:37 dell.home uresourced[2484]: Setting resources on
user@988.service (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
Dec 17 08:24:37 dell.home systemd[2508]: Queued start job for default target
default.target.
Dec 17 08:24:37 dell.home systemd[2508]: Created slice app.slice - User
Application Slice.
Dec 17 08:24:37 dell.home systemd[2508]: grub-boot-success.timer - Mark boot as
successful after the user session has run 2 minutes was skipped because of an
unmet condition check (ConditionUser=!@system).
Dec 17 08:24:37 dell.home systemd[2508]: Started systemd-tmpfiles-clean.timer -
Daily Cleanup of User's Temporary Directories.
Dec 17 08:24:37 dell.home systemd[2508]: Reached target paths.target - Paths.
Dec 17 08:24:37 dell.home systemd[2508]: Reached target timers.target - Timers.
Dec 17 08:24:37 dell.home systemd[2508]: Starting dbus.socket - D-Bus User
Message Bus Socket...
Dec 17 08:24:37 dell.home systemd[2508]: Listening on pipewire-pulse.socket -
PipeWire PulseAudio.
Dec 17 08:24:37 dell.home systemd[2508]: Listening on pipewire.socket -
PipeWire Multimedia System Sockets.
Dec 17 08:24:37 dell.home systemd[2508]: Starting
systemd-tmpfiles-setup.service - Create User's Volatile Files and
Directories...
Dec 17 08:24:37 dell.home systemd[2508]: Listening on dbus.socket - D-Bus User
Message Bus Socket.
Dec 17 08:24:37 dell.home systemd[2508]: Reached target sockets.target -
Sockets.
Dec 17 08:24:37 dell.home systemd[2508]: Finished
systemd-tmpfiles-setup.service - Create User's Volatile Files and Directories.
Dec 17 08:24:37 dell.home systemd[2508]: Reached target basic.target - Basic
System.
Dec 17 08:24:37 dell.home systemd[2508]: Reached target default.target - Main
User Target.
Dec 17 08:24:37 dell.home systemd[2508]: Startup finished in 125ms.
Dec 17 08:24:37 dell.home systemd[1]: Started user@988.service - User Manager
for UID 988.
Dec 17 08:24:37 dell.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=user@988
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:24:37 dell.home systemd[1]: Started session-c1.scope - Session c1 of
User sddm.
Dec 17 08:24:37 dell.home systemd[1]: Startup finished in 8.663s (firmware) +
7.186s (loader) + 1.020s (kernel) + 4.798s (initrd) + 8.032s (userspace) =
29.701s.
Dec 17 08:24:37 dell.home audit[2443]: USER_START pid=2443 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023
msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct="sddm"
exe="/usr/libexec/sddm-helper" hostname=dell.home addr=? terminal=/dev/tty1
res=success'
Dec 17 08:24:37 dell.home sddm-helper-start-wayland[2526]: "No backend
specified, automatically choosing drm\n"
Dec 17 08:24:37 dell.home systemd[2508]: Created slice session.slice - User
Core Session Slice.
Dec 17 08:24:37 dell.home systemd[2508]: Starting dbus-broker.service - D-Bus
User Message Bus...
Dec 17 08:24:37 dell.home dbus-broker-launch[2533]: Service file
'/usr/share//dbus-1/services/imsettings-daemon.service' is not named after the
D-Bus name 'com.redhat.imsettings'.
Dec 17 08:24:37 dell.home dbus-broker-launch[2533]: Service file
'/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the
D-Bus name 'org.kde.KScreen'.
Dec 17 08:24:37 dell.home dbus-broker-launch[2533]: Service file
'/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named
after the D-Bus name 'org.freedesktop.FileManager1'.
Dec 17 08:24:37 dell.home dbus-broker-launch[2533]: Service file
'/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named
after the D-Bus name 'org.freedesktop.Notifications'.
Dec 17 08:24:37 dell.home dbus-broker-launch[2533]: Policy to allow
eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is
deprecated and ignored
Dec 17 08:24:37 dell.home dbus-broker-launch[2533]: Policy to allow
eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is
deprecated and ignored
Dec 17 08:24:37 dell.home systemd[2508]: Started dbus-broker.service - D-Bus
User Message Bus.
Dec 17 08:24:37 dell.home dbus-broker-launch[2533]: Ready
Dec 17 08:24:38 dell.home kernel: thunderbolt 0-1: new device found,
vendor=0x16b device=0x9010
Dec 17 08:24:38 dell.home kernel: thunderbolt 0-1: i-tec TB3CDUALDPDOCKPD
Dec 17 08:24:38 dell.home boltd[1931]: [004158c8-bd26-TB3CDUALDPDOCKPD         
 ] parent is 9096ea89-ad77...
Dec 17 08:24:38 dell.home boltd[1931]: [004158c8-bd26-TB3CDUALDPDOCKPD         
 ] connected: authorized (/sys/devices/pci0000:00/0000:00:0d.2/domain0/0-0/0-1)
Dec 17 08:24:38 dell.home boltd[1931]: [004158c8-bd26-TB3CDUALDPDOCKPD         
 ] udev: device changed: authorized -> authorized
Dec 17 08:24:38 dell.home chronyd[1962]: Selected source 85.195.224.28
(2.fedora.pool.ntp.org)
Dec 17 08:24:38 dell.home chronyd[1962]: System clock TAI offset set to 37
seconds
Dec 17 08:24:44 dell.home systemd[1]:
dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@0.service: Deactivated
successfully.
Dec 17 08:24:44 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@0 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 17 08:24:45 dell.home systemd[1]: setroubleshootd.service: Deactivated
successfully.
Dec 17 08:24:45 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=setroubleshootd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:24:45 dell.home systemd[1]: NetworkManager-dispatcher.service:
Deactivated successfully.
Dec 17 08:24:45 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 17 08:24:53 dell.home audit[1483]: AVC avc:  denied  { sys_admin } for 
pid=1483 comm="nv_queue" capability=21 
scontext=system_u:system_r:systemd_modules_load_t:s0
tcontext=system_u:system_r:systemd_modules_load_t:s0 tclass=capability
permissive=0
Dec 17 08:24:55 dell.home systemd[1]: Starting setroubleshootd.service -
SETroubleshoot daemon for processing new SELinux denial logs...
Dec 17 08:24:55 dell.home systemd[1]: Started setroubleshootd.service -
SETroubleshoot daemon for processing new SELinux denial logs.
Dec 17 08:24:55 dell.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=setroubleshootd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:24:55 dell.home systemd[1]: Started
dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@1.service.
Dec 17 08:24:55 dell.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@1 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 17 08:24:56 dell.home setroubleshoot[2542]: SELinux is preventing
systemd-modules from using the sys_admin capability. For complete SELinux
messages run: sealert -l 8cabac7f-032b-4161-8b08-01cbd2cfef2d
Dec 17 08:24:56 dell.home setroubleshoot[2542]: SELinux is preventing
systemd-modules from using the sys_admin capability.

                                                *****  Plugin catchall (100.
confidence) suggests   **************************

                                                If you believe that
systemd-modules should have the sys_admin capability by default.
                                                Then you should report this as
a bug.
                                                You can generate a local policy
module to allow this access.
                                                Do
                                                allow this access for now by
executing:
                                                # ausearch -c 'systemd-modules'
--raw | audit2allow -M my-systemdmodules
                                                # semodule -X 300 -i
my-systemdmodules.pp

Dec 17 08:25:02 dell.home sddm-helper-start-wayland[2526]: "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"
Dec 17 08:25:03 dell.home systemd[1]: systemd-hostnamed.service: Deactivated
successfully.
Dec 17 08:25:03 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:25:03 dell.home audit: BPF prog-id=77 op=UNLOAD
Dec 17 08:25:03 dell.home audit: BPF prog-id=76 op=UNLOAD
Dec 17 08:25:03 dell.home audit: BPF prog-id=75 op=UNLOAD
Dec 17 08:25:05 dell.home systemd[1]:
dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@1.service: Deactivated
successfully.
Dec 17 08:25:05 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@1 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 17 08:25:06 dell.home systemd[1]: setroubleshootd.service: Deactivated
successfully.
Dec 17 08:25:06 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=setroubleshootd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:25:11 dell.home sddm-helper-start-wayland[2526]: "OpenGL vendor
string:                   NVIDIA Corporation\nOpenGL renderer string:          
      NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2\nOpenGL version string:     
            3.1.0 NVIDIA 545.29.06\nOpenGL shading language version string:
1.40 NVIDIA via Cg compiler\nDriver:                                
NVIDIA\nDriver version:                         545.29.6\nGPU class:           
                  Unknown\nOpenGL version:                         3.1\nGLSL
version:                           1.40\nLinux kernel version:                 
 6.6.6\nRequires strict binding:                no\nGLSL shaders:              
            yes\nTexture NPOT support:                   yes\nVirtual Machine: 
                      no\n"
Dec 17 08:25:12 dell.home sddm-helper-start-wayland[2526]:
"kf.service.services: The desktop entry file
\"/usr/share/applications/qemu.desktop\" has Type= \"Application\" but has no
Exec field.\n"
Dec 17 08:25:12 dell.home sddm-helper-start-wayland[2526]:
"kf.service.services: The desktop entry file
\"/usr/share/applications/org.freedesktop.Xwayland.desktop\" has Type=
\"Application\" but has no Exec field.\n"
Dec 17 08:25:12 dell.home sddm-helper-start-wayland[2526]:
"kf.service.services: The desktop entry file
\"/usr/share/applications/logmgr.desktop\" has Type= \"Application\" but has no
Exec field.\n"
Dec 17 08:25:12 dell.home sddm-greeter[2529]: Creating a fake screen in order
for Qt not to crash
Dec 17 08:25:22 dell.home audit[1483]: AVC avc:  denied  { sys_admin } for 
pid=1483 comm="nv_queue" capability=21 
scontext=system_u:system_r:systemd_modules_load_t:s0
tcontext=system_u:system_r:systemd_modules_load_t:s0 tclass=capability
permissive=0
Dec 17 08:25:24 dell.home systemd[1]: Starting setroubleshootd.service -
SETroubleshoot daemon for processing new SELinux denial logs...
Dec 17 08:25:24 dell.home systemd[1]: Started setroubleshootd.service -
SETroubleshoot daemon for processing new SELinux denial logs.
Dec 17 08:25:24 dell.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=setroubleshootd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:25:24 dell.home systemd[1]: Started
dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@2.service.
Dec 17 08:25:24 dell.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@2 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 17 08:25:25 dell.home setroubleshoot[2577]: SELinux is preventing
systemd-modules from using the sys_admin capability. For complete SELinux
messages run: sealert -l 8cabac7f-032b-4161-8b08-01cbd2cfef2d
Dec 17 08:25:25 dell.home setroubleshoot[2577]: SELinux is preventing
systemd-modules from using the sys_admin capability.

                                                *****  Plugin catchall (100.
confidence) suggests   **************************

                                                If you believe that
systemd-modules should have the sys_admin capability by default.
                                                Then you should report this as
a bug.
                                                You can generate a local policy
module to allow this access.
                                                Do
                                                allow this access for now by
executing:
                                                # ausearch -c 'systemd-modules'
--raw | audit2allow -M my-systemdmodules
                                                # semodule -X 300 -i
my-systemdmodules.pp

Dec 17 08:25:34 dell.home systemd[1]:
dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@2.service: Deactivated
successfully.
Dec 17 08:25:34 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dbus-:1.3-org.fedoraproject.SetroubleshootPrivileged@2 comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 17 08:25:35 dell.home systemd[1]: setroubleshootd.service: Deactivated
successfully.
Dec 17 08:25:35 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=setroubleshootd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:25:44 dell.home chronyd[1962]: Selected source 192.33.214.47
(2.fedora.pool.ntp.org)
Dec 17 08:26:37 dell.home systemd[1]: virtlxcd.service: Deactivated
successfully.
Dec 17 08:26:37 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=virtlxcd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:26:37 dell.home systemd[1]: virtqemud.service: Deactivated
successfully.
Dec 17 08:26:37 dell.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=virtqemud
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Dec 17 08:26:52 dell.home chronyd[1962]: Selected source
2a02:1210:249e:f00:1eb0:44ff:fefa:ec90

... it just goes downhill from here ...

Dec 17 08:29:40 dell.home systemd-logind[1684]: Power key pressed short.
Dec 17 08:29:40 dell.home systemd-logind[1684]: Powering off...
Dec 17 08:29:40 dell.home systemd-logind[1684]: System is powering down.
Dec 17 08:29:40 dell.home systemd[1]: Stopping session-c1.scope - Session c1 of
User sddm...
Dec 17 08:29:40 dell.home sddm[2368]: Error from greeter session: "Process
crashed"
Dec 17 08:29:40 dell.home sddm[2368]: Auth: sddm-helper (--socket
/tmp/sddm-auth-fb32114e-e536-4e4f-a8ad-e6000f61baa8 --id 2 --start
/usr/bin/sddm-greeter --socket /tmp/sddm--CAFWSv --theme
/usr/share/sddm/themes/01-breeze-fedora --user sddm --display-server
kwin_wayland --no-lockscreen --greeter) crashed (exit code 1)
Dec 17 08:29:40 dell.home sddm[2368]: Error from greeter session: "Process
crashed"
Dec 17 08:29:40 dell.home sddm[2368]: Auth: sddm-helper exited with 1
```

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

Reply via email to