Created attachment 145923 [details] Journalctl error: kwin_wayland_wrapper SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Boot 2. Select Wayland on login screen 3. Enter password and hit Enter OBSERVED RESULT One of two outcomes: 1) Screen momentarily goes black, then the login screen re-appears. 2) Screen permanently goes black, the signal to the monitor is lost. EXPECTED RESULT Log in to Wayland session SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.23.4 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I am using and AMD GPU, using the amdgpu drivers. This occurred sometime after January 12, 2022. I am running Fedora Kinoite. Using a previous deployment from Jan 12, I do not have this issue. The working deployment from Jan 12 is running the same KDE Plasma and Frameworks versions as the current (broken) deployment. Only notable differences are: Kernel 5.15.13-200.fc35 -> 5.15.16-200.fc35 mesa 21.3.3-1.fc35 -> 21.3.4-3.fc35 Attached is a journalctl entry from a time when the login screen turned black and returned to the login screen. There seems to have been a crash with the kwin_wayland_wrapper
Can you attach ~/.local/share/sddm/wayland-session.log to the bug report please?
(In reply to Vlad Zahorodnii from comment #1) > Can you attach ~/.local/share/sddm/wayland-session.log to the bug report > please? I don't seem to have that directory and log. yosuke@fedora-pc ~/.local/share ls -l drwx------@ - yosuke 21 Sep 2021 applications drwxr-xr-x@ - yosuke 25 Sep 2021 aurorae drwxr-xr-x@ - yosuke 25 Jan 09:57 baloo drwxr-xr-x@ - yosuke 26 Oct 2021 color-schemes drwx------@ - yosuke 31 Aug 2021 containers drwx------@ - yosuke 31 Aug 2021 desktop-directories drwxr-xr-x@ - yosuke 7 Oct 2021 discover drwxr-xr-x@ - yosuke 17 Sep 2021 dolphin drwx------@ - yosuke 31 Aug 2021 evolution drwx------@ - yosuke 25 Jan 08:28 flatpak drwxr-xr-x@ - yosuke 16 Sep 2021 fonts drwxr-xr-x@ - yosuke 31 Aug 2021 gnome-settings-daemon drwx------@ - yosuke 17 Sep 2021 gnome-shell drwx------@ - yosuke 17 Sep 2021 gvfs-metadata drwxr-xr-x@ - yosuke 31 Aug 2021 ibus-typing-booster drwxr-xr-x@ - yosuke 31 Aug 2021 icc drwx------@ - yosuke 3 Dec 2021 icons drwxr-xr-x@ - yosuke 17 Sep 2021 kactivitymanagerd drwxr-xr-x@ - yosuke 25 Jan 10:00 kcookiejar drwxr-xr-x@ - yosuke 17 Sep 2021 kded5 drwxr-xr-x@ - yosuke 25 Jan 10:01 keyrings drwxr-xr-x@ - yosuke 17 Sep 2021 khelpcenter drwxr-xr-x@ - yosuke 25 Jan 10:07 klipper drwxr-xr-x@ - yosuke 18 Oct 2021 knewstuff3 drwxr-xr-x@ - yosuke 18 Oct 2021 konsole .rw-------@ 5.6k yosuke 25 Jan 10:01 krunnerstaterc drwxr-xr-x@ - yosuke 28 Sep 2021 kscreen drwxr-xr-x@ - yosuke 26 Oct 2021 kwalletd drwxr-xr-x@ - yosuke 6 Oct 2021 kwrite drwxr-xr-x@ - yosuke 13 Oct 2021 kxmlgui5 drwxr-xr-x@ - yosuke 12 Oct 2021 lutris drwx------@ - yosuke 14 Oct 2021 mc drwxr-xr-x@ - yosuke 31 Aug 2021 nautilus drwxr-xr-x@ - yosuke 20 Oct 2021 okular drwxr-----@ - yosuke 31 Aug 2021 pki drwxr-xr-x@ - yosuke 25 Sep 2021 plasma drwxr-xr-x@ - yosuke 21 Oct 2021 plasma-systemmonitor drwxr-xr-x@ - yosuke 12 Oct 2021 plasma-vault drwxr-xr-x@ - yosuke 17 Sep 2021 plasma_icons drwxr-xr-x@ - yosuke 7 Oct 2021 plasmashell drwxr-xr-x@ - yosuke 25 Jan 09:46 RecentDocuments .rw-------@ 27k yosuke 3 Nov 2021 recently-used.xbel drwxr-xr-x@ - yosuke 17 Sep 2021 remoteview drwx------@ - yosuke 31 Aug 2021 sounds drwx------@ - yosuke 23 Nov 2021 Trash .rw-r--r--@ 11k yosuke 14 Oct 2021 user-places.xbel .rw-r--r--@ 11k yosuke 14 Oct 2021 user-places.xbel.bak .rw-r--r--@ 0 yosuke 14 Oct 2021 user-places.xbel.tbcache drwxr-xr-x@ - yosuke 16 Sep 2021 virtualenv drwxr-xr-x@ - yosuke 12 Oct 2021 webkitgtk
Do you use SDDM? If not, make sure that environment variables such as XDG_RUNTIME_DIR are set
(In reply to Vlad Zahorodnii from comment #3) > Do you use SDDM? If not, make sure that environment variables such as > XDG_RUNTIME_DIR are set I use SDDM. yosuke@fedora-pc ~ systemctl status sddm ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-01-26 06:38:08 CST; 1min 26s ago Docs: man:sddm(1) man:sddm.conf(5) Main PID: 1395 (sddm) Tasks: 33 (limit: 38323) Memory: 199.5M CPU: 248ms CGroup: /system.slice/sddm.service ├─1395 /usr/bin/sddm └─1406 /usr/libexec/Xorg -dpi 0 -auth /var/run/sddm/{fb1fdb8a-fcaf-4ef0-9522-dffa4f269a7f} -background none -noreset -displayfd 16 -seat> Jan 26 06:38:14 fedora-pc sddm-helper[1532]: gkr-pam: unable to locate daemon control file Jan 26 06:38:14 fedora-pc sddm-helper[1532]: gkr-pam: stashed password to try later in open session Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_unix(sddm:session): session opened for user yosuke(uid=1000) by (uid=0) Jan 26 06:38:14 fedora-pc sddm-helper[1532]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring Jan 26 06:38:14 fedora-pc sddm-helper[1532]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Created attachment 145954 [details] Full boot log Attached is a full log of a failed login. I’ve compared the logs for a successful login (using the old deployment) to a failed one (new deployment, attached). In the new deployment, I am seeing these errors: 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 `ls -l /run/user` 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.
Upon further investigation, I believe this is an SELinux issue. Closing.