Wayland broke in Kinoite - SELinux Issue?

I’ve been having this issue since mid-January, and I’ve been having to use an old (pinned) deployment for my system to work. Upon trying to log into my system with Wayland, either it goes to black screen or the login screen comes back. I’ve been able to find this using journalctl -r:

Jan 25 08:32:45 fedora-pc sddm-helper[1546]: pam_unix(sddm:session): session closed for user yosuke
Jan 25 08:32:45 fedora-pc audit[1546]: CRED_DISP pid=1546 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grant>
Jan 25 08:32:45 fedora-pc audit[1546]: USER_END pid=1546 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close >
Jan 25 08:32:45 fedora-pc audit[1546]: CRED_DISP pid=1546 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grant>
Jan 25 08:32:45 fedora-pc audit[1546]: USER_END pid=1546 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close >
Jan 25 08:32:45 fedora-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredu>
Jan 25 08:32:45 fedora-pc systemd[1]: systemd-coredump@0-1597-0.service: Deactivated successfully.
Jan 25 08:32:45 fedora-pc systemd-coredump[1598]: [🡕] Process 1596 (kwin_wayland_wr) of user 1000 dumped core.
                                                  
                                                  Found module linux-vdso.so.1 with build-id: 5adf6bc52f5c51e10c5d1229124d27eebdae3b02
                                                  Found module libpcre2-8.so.0 with build-id: 67d78ee981939e51fee33d8885ff8000552e7a3d
                                                  Found module libgpg-error.so.0 with build-id: 081975d0a3416374b4883b2f1639fd3c9df42390
                                                  Found module libselinux.so.1 with build-id: f805394f993c704b949315b56c344d22dfad801f
                                                  Found module libpcre.so.1 with build-id: fcbdb4731e50f20a47b62341a6841dd616fe495d
                                                  Found module libicudata.so.69 with build-id: fae0a612a5535b81eaec823e8cedb06c89719d94
                                                  Found module libgcrypt.so.20 with build-id: 711d41580c5a8649a79a8430a985dac3e25b5ba2
                                                  Found module libcap.so.2 with build-id: 0214aa9cc6a8646eb9ec27ab7dda6a2219da6500
                                                  Found module liblz4.so.1 with build-id: fd02c4542a1ce1ad6c503b958447be1c37a4afee
                                                  Found module libzstd.so.1 with build-id: 7984add4b0ab24869c30e19cfba3637ca295dd7b
                                                  Found module liblzma.so.5 with build-id: 7fec53ce7cba9489f130c99cfd3ace82e9dde0ee
                                                  Found module libresolv.so.2 with build-id: 057b93718c09e93c39c7945cdbeb314445b21fd6
                                                  Found module libkeyutils.so.1 with build-id: 2560a16099ad1875f7ea2195ae25b97ea168a758
                                                  Found module libkrb5support.so.0 with build-id: 03649849c4d1813c307624a711b03fb15e7124cb
                                                  Found module libcom_err.so.2 with build-id: a1d791cd7600f5609702a895a64d9131d1cd7b8f
                                                  Found module libk5crypto.so.3 with build-id: 11238d51059ecf299699dc4d24a74e67a64aa725
                                                  Found module libkrb5.so.3 with build-id: 0582e999cc7d74e1ec2dc7b3c9f7aa4dae7342f6
                                                  Found module ld-linux-x86-64.so.2 with build-id: b43118df1fdb4c0aff150b6f8f926bccdec2a7f0
                                                  Found module libgcc_s.so.1 with build-id: 88564abce789aa42536da1247a57ff6062d61dcb
                                                  Found module libm.so.6 with build-id: cea55efc551e62cd8439d044aa9a765c445fb7bf
                                                  Found module libglib-2.0.so.0 with build-id: 3720108994016259cac8f61f174ea32513518152
                                                  Found module libpcre2-16.so.0 with build-id: 6fdd2850c96a1d770fb277838d7ecb955d2c7407
                                                  Found module libicuuc.so.69 with build-id: 45119735453983eea1a3fb59b0ed34a6e61d8c5a
                                                  Found module libicui18n.so.69 with build-id: 96cea623123108e425250a0c59fa6221e96cadb2
                                                  Found module libsystemd.so.0 with build-id: b61753e8440ecf39624b3e37f855941c18a69e9b
                                                  Found module libcrypto.so.1.1 with build-id: 3ead607210606611d5f3398ee7e65198bd519de9
                                                  Found module libssl.so.1.1 with build-id: b3b8eaa0fc316f1bb70ca237310c5b09048d3648
                                                  #1  0x00007fd3401b96a6 raise (libc.so.6 + 0x426a6)
                                                  #2  0x00007fd3401a37d3 abort (libc.so.6 + 0x2c7d3)
                                                  #1  0x00007fd3401b96a6 raise (libc.so.6 + 0x426a6)
                                                  #2  0x00007fd3401a37d3 abort (libc.so.6 + 0x2c7d3)
                                                  #3  0x00007fd34065144b _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0xb144b)
                                                  #4  0x000055a40d7ef950 main (kwin_wayland_wrapper + 0x4950)
                                                  #5  0x00007fd3401a4560 __libc_start_call_main (libc.so.6 + 0x2d560)
                                                  #6  0x00007fd3401a460c __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d60c)
                                                  #7  0x000055a40d7f0625 _start (kwin_wayland_wrapper + 0x5625)
Jan 25 08:32:45 fedora-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-1597-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostna>
Jan 25 08:32:45 fedora-pc systemd[1]: Started Process Core Dump (PID 1597/UID 0).
Jan 25 08:32:45 fedora-pc audit: BPF prog-id=49 op=LOAD
Jan 25 08:32:45 fedora-pc audit: BPF prog-id=48 op=LOAD
Jan 25 08:32:45 fedora-pc audit: BPF prog-id=47 op=LOAD
Jan 25 08:32:45 fedora-pc systemd[1]: Created slice Slice /system/systemd-coredump.
Jan 25 08:32:45 fedora-pc audit[1596]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1596 comm="kwin_wayland_wr" exe="/usr/bin/kwin_wayland_wrapper" sig>
Jan 25 08:32:45 fedora-pc uresourced[1459]: Setting resources on user@1000.service (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
Jan 25 08:32:45 fedora-pc uresourced[1459]: Setting resources on user-1000.slice (MemoryMin: 262144000, MemoryLow: 0, CPUWeight: 500, IOWeight: 500)
Jan 25 08:32:45 fedora-pc uresourced[1459]: Setting resources on user@978.service (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
Jan 25 08:32:45 fedora-pc uresourced[1459]: Setting resources on user-978.slice (MemoryMin: 0, MemoryLow: 0, CPUWeight: 100, IOWeight: 100)
Jan 25 08:32:45 fedora-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=>
Jan 25 08:32:45 fedora-pc systemd[1]: Started Locale Service.
Jan 25 08:32:45 fedora-pc systemd[1]: Starting Locale Service...

I am able to log into an X11 session, but all my audio devices are gone/not recognized. Unsure if this is related.

Strangely this issue is happening on other KDE distros at present also. Are you running an Nvidia card in your system?

Thanks for the reply. No, I have an AMD GPU, using mesa drivers.

Thats a good start, okay. Can you login with x11 session

open the terminal and punch in this command

journalctl -ab > journal.log

Then goto the home directory in the files app and copy and paste the output from the file called

journal.log

it will be read only but you should be able to copy the text from it

I’ve copied the log here:

1 Like

Okay I will check that out.

Do you know what GPU driver and kernel version your running on the system?

can you run

lspci -k

Also can you please check this file called

plasmawayland.desktop

on your filesystem

You should find it at this path

/usr/share/wayland-sessions/

I am interested in the line called Exec=

and what it says,

It may not be in that path let me know if you cannot find it.

I’ll dig into this journal log you sent now to check some things

I am running kernel 5.15.16-200.fc35.x86_64. Here is the output from lspci -k:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
        Kernel driver in use: pcieport
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
        Kernel driver in use: pcieport
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
        Kernel driver in use: pcieport
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
        Kernel driver in use: pcieport
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
        Kernel driver in use: pcieport
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
        Kernel driver in use: piix4_smbus
        Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
        Kernel driver in use: k10temp
        Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)
        Subsystem: Phison Electronics Corporation E16 PCIe4 NVMe Controller
        Kernel driver in use: nvme
        Kernel modules: nvme
20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
        Kernel driver in use: pcieport
21:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
        Kernel driver in use: pcieport
21:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
        Kernel driver in use: pcieport
21:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
        Kernel driver in use: pcieport
21:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
        Kernel driver in use: pcieport
21:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
        Kernel driver in use: pcieport
21:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
        Kernel driver in use: pcieport
21:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
        Kernel driver in use: pcieport
22:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
        Subsystem: Samsung Electronics Co Ltd SSD 970 EVO Plus 1TB
        Kernel driver in use: nvme
        Kernel modules: nvme
23:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01)
        Subsystem: Phison Electronics Corporation E12 NVMe Controller
        Kernel driver in use: nvme
        Kernel modules: nvme
25:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01)
26:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01)
        Subsystem: Device 3412:7856
        Kernel driver in use: firewire_ohci
        Kernel modules: firewire_ohci
27:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
        Kernel driver in use: r8169
        Kernel modules: r8169
2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
2a:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
        Kernel driver in use: xhci_hcd
2a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
        Subsystem: Advanced Micro Devices, Inc. [AMD] Device 148c
        Kernel driver in use: xhci_hcd
2b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
        Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode]
        Kernel driver in use: ahci
2c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
        Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode]
        Kernel driver in use: ahci
2d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c0)
        Kernel driver in use: pcieport
2e:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
        Kernel driver in use: pcieport
2f:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] (rev c0)
        Subsystem: XFX Limited Device 6901
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
2f:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
2f:00.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 73a6
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 73a6
        Kernel driver in use: xhci_hcd
2f:00.3 Serial bus controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 USB
        Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 0408
        Kernel driver in use: i2c-designware-pci
30:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
31:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
31:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7c35
        Kernel driver in use: xhci_hcd
31:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device cc35
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel

Here is the Exec line from my plasmawayland.desktop:

Exec=/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

Thanks

Can you please edit that line for

Exec=/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland

And change it to

Exec=/usr/bin/dbus-run-session /usr/bin/startplasma-wayland

I don’t think I can do that; /usr is part of the immutable filesystem I believe.

You can do a sudo edit with VIM.

However looking closer at your journal log your filesystem is setup a bit different to what I thought earlier.

I believe that the GDM should run plasma desktop for your system.

You should be able to switch easily to GDM (gnome display manager) but they may mean your QT apps will have issues.

Keep in mind Wayland is not yet ironed out all the creases for some desktop environments. Some of your apps won’t work perfectly yet especially conference calls and screen sharing.

Any important reason why you need to run Wayland?

I run X as you cannot do remote assist and many other things yet with Wayland.

Wayland is more suited to Gnome at the moment as there are some patches like these being worked on…

Right, I’m running Kinoite, which is the KDE flavor of Silverblue. Which means the system directories including /usr are immutable by design.

I don’t need to run Wayland, but I haven’t had any issues that I couldn’t work around until this.

@bennyisaiah Kinoite and Silverblue strongly differ from the “normal” Fedora Workstation and its spins. Be careful about transferring from one to the other, this can create damage.

The role of the display manager is a bit different, its impact on apps in the desktop environment is low, in general it has “just” to comply to X11 and/or Wayland. Both SDDM and GDM do this. Apps are an issue for the desktop environment, and the available/installed libraries.

So I would not automatically relate a wayland issue to sddm.

I experienced the close issue. Sometimes the panel broke and reappear again or screen becomes white and come again but no fail or no logout or something. Firefox working great these days with Wayland also no crashes but this is because of KDE desktop environment. It is not related to Wayland, kernel or mesa my thought because in Silverblue I didn’t encounter these kind of issues. If you face problems just skip into X11 than you are fine :blush:

1 Like

Thanks for confirming. Yes I realised this after I looked into the paths comparing to the workstation (desktop) I am using, so I didnt recommend any further changes. Yes I agree, the issue here seems to me to be Wayland on KDE and not a Fedora or driver issue.

I’ve compared the logs for a successful login (using the old deployment) to a failed one (new deployment).

In the new deployment, I am getting these errors:

Jan 26 07:24:46 fedora-pc systemd-user-runtime-dir[1430]: Failed to mount per-user tmpfs directory /run/user/978: No such file or directory
fedora-pc sddm-helper[1428]: pam_systemd(sddm-greeter:session): Failed to stat() runtime directory ‘/run/user/978’: No such file or directory

Whereas in a successful login, these don’t appear.

Using a different TTY upon getting to the login screen, I can check and indeed when booted in the new deployment , /run/user/ is empty. When booted in the old (working) deployment I see 2 entries in /run/user/ - one for sddm, and one for my username.

I don’t know enough about the boot process, but what is the process that is supposed to create these directories in /run/user/? Whatever that is seems to have broken.

1 Like

Upon further research, I learned that logind and PAM are responsible for creating these directories upon login. In the logs for the failed login, I found:

Jan 26 07:24:47 fedora-pc systemd-logind[1155]: New session 1 of user yosuke.
Jan 26 07:24:47 fedora-pc audit[1513]: AVC avc: denied { create } for pid=1513 comm=“systemd-user-ru” name=“1000” scontext=system_u:system_r:systemd_logind_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=dir permissive=0

So this may be an issue with SELINUX?

1 Like

Well that was the key! Found the relevant info and solution over on the Discussion Forum:

Thank you, @jakfrost

1 Like