That was…different LOL. The upgrade was done on a new Laptop Framework 16 with the Ai9 HX 370 CPU.
So 1.8Gig of updates and all went fairly well on reboot. I monitored the system once up and logged into the Desktop and waited until all the major processes (cleanup ?) were done. Then I shut it down and booted up again. Well…I was greeted with a Black Screen. No boot up process no login screen..just Black. Jumped over to a TTY terminal and ran the “reboot” command. System again showed no boot process but my keyboard backlight turned off, came back on again, giving me some notion that things were happening. Finally after about 10 seconds I was greeted with the login GUI and rest worked flawless. At this stage I am a bit hesitant to fully shut it down again as the system is running backup update to the NAS. Maybe it was the cause at the time.
Has anyone else done the update yet and how was your experience ?
Just finished the dnf update (literally, 30 seconds ago) but not rebooted yet. I’ll give it a whirl now.
Well, nothing exploded.
It did take longer to boot though - much more time spent in userspace. I’ll have a look at the journal in a bit and the plot to see what it was doing.
┌─🎩 lurcher ~
├─
└─➜ uname -a 11:54 Fri 20-Feb
Linux lurcher 6.18.12-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 16 18:58:26 UTC 2026 x86_64 GNU/Linux
┌─🎩 lurcher ~
├─
└─➜ systemd-analyze 11:54 Fri 20-Feb
Startup finished in 23.355s (firmware) + 7.125s (loader) + 1.093s (kernel) + 5.480s (initrd) + 51.610s (userspace) = 1min 28.665s
graphical.target reached after 51.504s in userspace.
Turns out it was akmods doing its thing for 48 seconds. No crashes or weirdness though.
One weird crash for me, on the second boot after updating.
Logged in as normal, started opening my normal apps, then after a couple of minutes the system kicked me back into SDDM. Trying to log in again, the system froze and needed a forcible reboot.
The logs show several apps coredumping, but nothing that really tells me what the cause was. It hasn’t recurred but I’ll keep an eye.
1 Like
Laptop coming out of sleep, no problem. Shut down and boot..same issue.
Back into TTY and reboot…works again.
Here are some of the captured error messages. Ouch, these did not exist before the update LOL:
journalctl -b -0 -p err
Feb 21 10:31:07 fedora kernel: ucsi_acpi USBC000:00: unknown error 256
Feb 20 23:31:12 fedora bluetoothd[1167]: Failed to set default system config for hci0
Feb 20 23:31:12 fedora bluetoothd[1167]: Failed to set mode: Failed (0x03)
Feb 20 23:31:16 fedora firewalld[1274]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error(s) opening ddc devices
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-3
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-4
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-5
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-6
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-7
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-8
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-9
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-10
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-11
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-12
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-13
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-14
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-15
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-16
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-17
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-18
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-19
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-20
Feb 20 23:31:35 fedora wpa_supplicant[1374]: bgscan simple: Failed to enable signal strength monitoring
Feb 20 23:31:35 fedora bluetoothd[1167]: Failed to set mode: Failed (0x03)
Feb 20 23:31:39 fedora wpa_supplicant[1374]: bgscan simple: Failed to enable signal strength monitoring
Feb 20 23:32:31 fedora kwin_wayland[2377]: Libinput: event4 - PIXA3854:00 093A:0274 Touchpad: kernel bug: Touch jump detected>
See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.ht>
...skipping...
Feb 21 10:31:07 fedora kernel: ucsi_acpi USBC000:00: unknown error 256
Feb 20 23:31:12 fedora bluetoothd[1167]: Failed to set default system config for hci0
Feb 20 23:31:12 fedora bluetoothd[1167]: Failed to set mode: Failed (0x03)
Feb 20 23:31:16 fedora firewalld[1274]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error(s) opening ddc devices
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-3
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-4
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-5
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-6
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-7
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-8
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-9
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-10
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-11
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-12
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-13
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-14
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-15
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-16
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-17
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-18
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-19
Feb 20 23:31:34 fedora org_kde_powerdevil[2760]: [ 2760] Error EACCES(-13): Permission denied opening /dev/i2c-20
Feb 20 23:31:35 fedora wpa_supplicant[1374]: bgscan simple: Failed to enable signal strength monitoring
Feb 20 23:31:35 fedora bluetoothd[1167]: Failed to set mode: Failed (0x03)
Feb 20 23:31:39 fedora wpa_supplicant[1374]: bgscan simple: Failed to enable signal strength monitoring
Feb 20 23:32:31 fedora kwin_wayland[2377]: Libinput: event4 - PIXA3854:00 093A:0274 Touchpad: kernel bug: Touch jump detected>
See https://wayland.freedesktop.org/libinput/doc/1.30.1/touchpad-jumping-cursors.ht>
~
Could be a race condition. Here, for 3 systems by age, oldest first, no akmods, upgraded remotely using ssh sessions:
% systemd-analyze
Startup finished in 728ms (kernel) + 3.068s (initrd) + 15.592s (userspace) = 19.388s
graphical.target reached after 15.592s in userspace.
% systemd-analyze
Startup finished in 6.181s (firmware) + 6.537s (loader) + 862ms (kernel) + 3.567s (initrd) + 11.587s (userspace) = 28.737s
graphical.target reached after 11.582s in userspace.
% systemd-analyze
Startup finished in 5.194s (firmware) + 10.466s (loader) + 1.079s (kernel) + 2.721s (initrd) + 15.410s (userspace) = 34.872s
graphical.target reached after 15.410s in userspace.
(The oldest system is a 2012 iMac with Nvidia graphics using nouveau).
1 Like
Maybe funky permisisons? Here’s mine for reference, although this is a desktop:
┌─🎩 lurcher /dev🔒
├─
└─➜ ls -al i2* 12:49 Fri 20-Feb
Permissions Size User Date Modified Name
crw-------@ 89,0 root 20 Feb 11:53 i2c-0
crw-------@ 89,1 root 20 Feb 11:53 i2c-1
crw-------@ 89,2 root 20 Feb 11:53 i2c-2
crw-------@ 89,3 root 20 Feb 11:53 i2c-3
crw-rw----@ 89,4 root 20 Feb 11:54 i2c-4
crw-rw----@ 89,5 root 20 Feb 11:54 i2c-5
crw-rw----@ 89,6 root 20 Feb 11:54 i2c-6
crw-rw----@ 89,7 root 20 Feb 11:54 i2c-7
crw-rw----@ 89,8 root 20 Feb 11:54 i2c-8
crw-rw----@ 89,9 root 20 Feb 11:54 i2c-9
crw-rw----@ 89,10 root 20 Feb 11:54 i2c-10
┌─🎩 lurcher /dev🔒
├─
└─➜ cat i2c-0 12:49 Fri 20-Feb
[bat error]: 'i2c-0': Permission denied (os error 13)
┌─🎩 lurcher /dev🔒
├─
└─➜ cat i2c-4 12:49 Fri 20-Feb
File: i2c-4 <EMPTY>
1 Like
Mine looks ..off?
/dev$ ls -al i2*
crw-------. 1 root root 89, 0 Feb 20 23:31 i2c-0
crw-------. 1 root root 89, 1 Feb 20 23:31 i2c-1
crw-------. 1 root root 89, 10 Feb 20 23:31 i2c-10
crw-------. 1 root root 89, 11 Feb 20 23:31 i2c-11
crw-------. 1 root root 89, 12 Feb 20 23:31 i2c-12
crw-------. 1 root root 89, 13 Feb 20 23:31 i2c-13
crw-------. 1 root root 89, 14 Feb 20 23:31 i2c-14
crw-------. 1 root root 89, 15 Feb 20 23:31 i2c-15
crw-------. 1 root root 89, 16 Feb 20 23:31 i2c-16
crw-------. 1 root root 89, 17 Feb 20 23:31 i2c-17
crw-------. 1 root root 89, 18 Feb 20 23:31 i2c-18
crw-------. 1 root root 89, 19 Feb 20 23:31 i2c-19
crw-------. 1 root root 89, 2 Feb 20 23:31 i2c-2
crw-------. 1 root root 89, 20 Feb 20 23:31 i2c-20
crw-------. 1 root root 89, 21 Feb 20 23:31 i2c-21
crw-------. 1 root root 89, 22 Feb 20 23:31 i2c-22
crw-------. 1 root root 89, 23 Feb 20 23:31 i2c-23
crw-------. 1 root root 89, 3 Feb 20 23:31 i2c-3
crw-------. 1 root root 89, 4 Feb 20 23:31 i2c-4
crw-------. 1 root root 89, 5 Feb 20 23:31 i2c-5
crw-------. 1 root root 89, 6 Feb 20 23:31 i2c-6
crw-------. 1 root root 89, 7 Feb 20 23:31 i2c-7
crw-------. 1 root root 89, 8 Feb 20 23:31 i2c-8
crw-------. 1 root root 89, 9 Feb 20 23:31 i2c-9
Maybe - maybe mine is off. Can’t say I’ve ever looked at the i2c stuff as I’ve never had a problem with it, that I was aware of. Maybe mine is FUBAR’d.
Apparently some of them have these privs deliberately so that one cannot do oneself a mischief…
┌─🎩 lurcher ~
├─
└─➜ sudo i2cdetect -l 12:54 Fri 20-Feb
i2c-0 i2c NVIDIA GPU I2C adapter I2C adapter
i2c-1 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter
i2c-2 smbus SMBus PIIX4 adapter port 2 at 0b00 SMBus adapter
i2c-3 smbus SMBus PIIX4 adapter port 1 at 0b20 SMBus adapter
i2c-4 i2c NVIDIA i2c adapter 1 at e:00.0 I2C adapter
i2c-5 i2c NVIDIA i2c adapter 2 at e:00.0 I2C adapter
i2c-6 i2c NVIDIA i2c adapter 3 at e:00.0 I2C adapter
i2c-7 i2c NVIDIA i2c adapter 5 at e:00.0 I2C adapter
i2c-8 i2c NVIDIA i2c adapter 6 at e:00.0 I2C adapter
i2c-9 i2c NVIDIA i2c adapter 7 at e:00.0 I2C adapter
i2c-10 i2c NVIDIA i2c adapter 8 at e:00.0 I2C adapter
1 Like
I am going to sit back a bit. Just came back to Linux after over 10 years of absence and I consider myself a Dabbler …just enough to be dangerous.
Anyway..smarter guys then me will sort it out.
Here is my output:
sudo i2cdetect -l
i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-2 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-3 i2c AMDGPU DM i2c hw bus 0 I2C adapter
i2c-4 i2c AMDGPU DM i2c hw bus 1 I2C adapter
i2c-5 i2c AMDGPU DM i2c hw bus 2 I2C adapter
i2c-6 i2c AMDGPU DM i2c hw bus 3 I2C adapter
i2c-7 i2c AMDGPU DM i2c hw bus 4 I2C adapter
i2c-8 i2c AMDGPU DM i2c hw bus 5 I2C adapter
i2c-9 i2c AMDGPU DM i2c hw bus 6 I2C adapter
i2c-10 i2c AMDGPU DM i2c hw bus 7 I2C adapter
i2c-11 i2c AMDGPU DM i2c hw bus 8 I2C adapter
i2c-12 i2c AMDGPU DM aux hw bus 0 I2C adapter
i2c-13 i2c AMDGPU DM aux hw bus 1 I2C adapter
i2c-14 i2c AMDGPU DM aux hw bus 2 I2C adapter
i2c-15 i2c AMDGPU DM aux hw bus 3 I2C adapter
i2c-16 i2c AMDGPU DM aux hw bus 4 I2C adapter
i2c-17 i2c AMDGPU DM aux hw bus 5 I2C adapter
i2c-18 i2c AMDGPU DM aux hw bus 6 I2C adapter
i2c-19 i2c AMDGPU DM aux hw bus 7 I2C adapter
i2c-20 i2c AMDGPU DM aux hw bus 8 I2C adapter
i2c-21 smbus SMBus PIIX4 adapter port 0 at 0b00 SMBus adapter
i2c-22 smbus SMBus PIIX4 adapter port 2 at 0b00 SMBus adapter
i2c-23 smbus SMBus PIIX4 adapter port 1 at 0b20 SMBus adapter
I’d not sweat it - on your machine those errors in the journal are because your i2c bus is locked down, presumably because of your installed hardware and configuration.
One can, if one dicks about with prodding the i2c bus with stuff one shouldn’t prod, trigger failures, bricking, EEPROM changes and so on. Bad stuff can happen - you can simply speed your fan up, or stop it…
1 Like
A bit more amateur investigation and it appears that SDDM is at fault for my problem. I had customized the Login screen with a different background and my customized one might be causing the problem. I did a cold shut down in a slightly different way and on cold boot start it threw me into the old default Fedora Log In screen. I might have a Font problem for the Login Screen ???
Here is what I get:
systemctl status sddm
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Sat 2026-02-21 11:18:20 AEDT; 13min ago
Invocation: 076df079df3f463fa4cc6b5707fccb7d
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 1500 (sddm)
Tasks: 2 (limit: 76191)
Memory: 29.5M (peak: 50.2M)
CPU: 227ms
CGroup: /system.slice/sddm.service
└─1500 /usr/bin/sddm
Feb 21 11:18:20 fedora systemd[1]: Started sddm.service - Simple Desktop Display Manager.
Feb 21 11:18:20 fedora sddm-helper[1516]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Feb 21 11:18:20 fedora sddm-helper[1516]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=983) by (uid=0)
Feb 21 11:19:00 fedora sddm-helper[2016]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
If you’re referring to the locale messages, that refers to the local that the system is running in. It defined the language, how to format currency and numbers, format of telephone numbers and so on.
I’m in the UK, so I have mine set as follows:
┌─🎩 lurcher ~
├─
└─➜ locale ⏱️ 11m31s 12:01 Sat 21-Feb
LANG=en_GB.UTF-8
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
Saying all of that, those messages are not harmful at all and should not impact the operation of sddm; in fact that systemctl output looks ok to me.
1 Like
I think this message is a false alarm - I see it on every startup, including those which are completely problem-free.
1 Like
dmesg sometimes has clues in it when this happens.
Mine has given me a black screen again and now did it consistant. Didn’t matter if it was cold boot or reboot.
This time I jumped to the next TTY up and then back again, which then gave me the TTY console where before it had just a black screen.
Logging in and then using startplasma-wayland then brought the GUI up.
Logs showed that SDDM was looking at a file that it wasn’t happy with and then shut down SDDM.
Booting in the previous Kernel, the system worked just fine. Tested multiple times, coldboot/reboot..no problem.
Do the same on the newest Kernel and it consistently ended up with a Black screen.
Not being an expert I might just have to wait for them to sort out any Kernel bugs. I am just baffled that a Kernel would cause issues with SDDM.
What file? Show us the logs showing the error.
There is more than just the kernel involved - the display should come on before linux is loaded, so vendor firmware may have a conflict.
These logs are rather large. I will try to get at least the last 2/3rd pasted here:
This is a failed log with latest Kernel 6.18.12-200
journalctl -b -2 | grep "sddm"
Feb 22 22:53:06 fedora systemd[1]: Started sddm.service - Simple Desktop Display Manager.
Feb 22 22:53:06 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 22 22:53:06 fedora sddm-helper[1514]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Feb 22 22:53:06 fedora audit[1514]: AUDIT1100 pid=1514 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 22:53:06 fedora audit[1514]: AUDIT1101 pid=1514 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 22:53:06 fedora audit[1514]: AUDIT1103 pid=1514 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 22:53:06 fedora sddm-helper[1514]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=983) by (uid=0)
Feb 22 22:53:06 fedora systemd-logind[1208]: New session 'c1' of user 'sddm' with class 'greeter' and type 'wayland'.
Feb 22 22:53:06 fedora audit[1571]: AUDIT1101 pid=1571 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-executor" hostname=? addr=? terminal=? res=success'
Feb 22 22:53:06 fedora audit[1571]: AUDIT1103 pid=1571 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-executor" hostname=? addr=? terminal=? res=failed'
Feb 22 22:53:06 fedora systemd-logind[1208]: New session '1' of user 'sddm' with class 'manager-early' and type 'unspecified'.
Feb 22 22:53:06 fedora (systemd)[1571]: pam_unix(systemd-user:session): session opened for user sddm(uid=983) by sddm(uid=0)
Feb 22 22:53:06 fedora audit[1571]: AUDIT1105 pid=1571 uid=0 auid=983 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-executor" hostname=? addr=? terminal=? res=success'
Feb 22 22:53:06 fedora systemd[1571]: drkonqi-coredump-cleanup.timer - Cleanup lingering KCrash metadata skipped, unmet condition check ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini
Feb 22 22:53:06 fedora systemd[1571]: drkonqi-sentry-postman.timer - Submitting pending crash events skipped, unmet condition check ConditionPathExistsGlob=/var/lib/sddm/.cache/drkonqi/sentry-envelopes/*
Feb 22 22:53:06 fedora systemd[1571]: drkonqi-coredump-cleanup.service - Cleanup lingering KCrash metadata skipped, unmet condition check ConditionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini
Feb 22 22:53:06 fedora systemd[1]: Started session-c1.scope - Session c1 of User sddm.
Feb 22 22:53:06 fedora audit[1514]: AUDIT1105 pid=1514 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=fedora addr=? terminal=/dev/tty1 res=success'
Feb 22 22:53:07 fedora sddm-helper-start-wayland[1647]: "No backend specified, automatically choosing drm\n"
Feb 22 22:53:07 fedora sddm-helper-start-wayland[1647]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
Feb 22 22:53:07 fedora sddm-helper-start-wayland[1647]: "kwin_core: Failed to open drm node: \"/dev/dri/card1\"\n"
Feb 22 22:53:07 fedora sddm-helper-start-wayland[1647]: "kwin_wayland_drm: No suitable DRM devices have been found\n"
Feb 22 22:53:07 fedora sddm-helper-start-wayland[1647]: "QThreadStorage: entry 6 destroyed before end of thread 0x563b7a06f0a0\nQThreadStorage: entry 1 destroyed before end of thread 0x563b7a06f0a0\nQThreadStorage: entry 0 destroyed before end of thread 0x563b7a06f0a0\n"
Feb 22 22:53:07 fedora sddm-helper-start-wayland[1647]: Stopping... "/usr/bin/sddm-greeter-qt6"
Feb 22 22:53:07 fedora sddm-helper[1514]: pam_unix(sddm-greeter:session): session closed for user sddm
Feb 22 22:53:07 fedora audit[1514]: AUDIT1106 pid=1514 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty1 res=success'
Feb 22 22:53:07 fedora audit[1514]: AUDIT1104 pid=1514 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty1 res=success'
Feb 22 22:54:38 fedora systemd[1]: Stopping sddm.service - Simple Desktop Display Manager...
Feb 22 22:54:38 fedora sddm[1496]: Signal received: SIGTERM
Feb 22 22:54:38 fedora systemd[1]: sddm.service: Deactivated successfully.
Feb 22 22:54:38 fedora systemd[1]: Stopped sddm.service - Simple Desktop Display Manager.
Feb 22 22:54:38 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
And this is a successful boot into the Login Manager with the older Kernel: 6.18.10-200
journalctl -b -0 | grep "sddm"
Feb 22 23:09:43 fedora systemd[1]: Started sddm.service - Simple Desktop Display Manager.
Feb 22 23:09:43 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sddm comm
="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 22 23:09:43 fedora sddm-helper[1519]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Feb 22 23:09:43 fedora audit[1519]: AUDIT1100 pid=1519 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 23:09:43 fedora audit[1519]: AUDIT1101 pid=1519 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 23:09:43 fedora audit[1519]: AUDIT1103 pid=1519 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 23:09:43 fedora sddm-helper[1519]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=983) by (uid=0)
Feb 22 23:09:43 fedora systemd-logind[1213]: New session 'c1' of user 'sddm' with class 'greeter' and type 'wayland'.
Feb 22 23:09:43 fedora audit[1574]: AUDIT1101 pid=1574 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:accou
nting grantors=pam_unix acct="sddm" exe="/usr/lib/systemd/systemd-executor" hostname=? addr=? terminal=? res=success'
Feb 22 23:09:43 fedora audit[1574]: AUDIT1103 pid=1574 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcr
ed grantors=? acct="sddm" exe="/usr/lib/systemd/systemd-executor" hostname=? addr=? terminal=? res=failed'
Feb 22 23:09:43 fedora systemd-logind[1213]: New session '1' of user 'sddm' with class 'manager-early' and type 'unspecified'.
Feb 22 23:09:43 fedora (systemd)[1574]: pam_unix(systemd-user:session): session opened for user sddm(uid=983) by sddm(uid=0)
Feb 22 23:09:43 fedora audit[1574]: AUDIT1105 pid=1574 uid=0 auid=983 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="s
ddm" exe="/usr/lib/systemd/systemd-executor" hostname=? addr=? terminal=? res=success'
Feb 22 23:09:43 fedora systemd[1574]: drkonqi-coredump-cleanup.timer - Cleanup lingering KCrash metadata skipped, unmet condition check Condit
ionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini
Feb 22 23:09:43 fedora systemd[1574]: drkonqi-sentry-postman.timer - Submitting pending crash events skipped, unmet condition check ConditionP
athExistsGlob=/var/lib/sddm/.cache/drkonqi/sentry-envelopes/*
Feb 22 23:09:43 fedora systemd[1574]: drkonqi-coredump-cleanup.service - Cleanup lingering KCrash metadata skipped, unmet condition check Cond
itionPathExistsGlob=/var/lib/sddm/.cache/kcrash-metadata/*.ini
Feb 22 23:09:43 fedora systemd[1]: Started session-c1.scope - Session c1 of User sddm.
Feb 22 23:09:43 fedora audit[1519]: AUDIT1105 pid=1519 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:session_open grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty1 res=succ
ess'
Feb 22 23:09:44 fedora sddm-helper-start-wayland[1654]: "No backend specified, automatically choosing drm\n"
Feb 22 23:09:44 fedora sddm-helper-start-wayland[1654]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
Feb 22 23:09:44 fedora sddm-helper-start-wayland[1654]: "kwin_xkbcommon: XKB: Multiple definitions of group 0 name in map 'basic'; Using 'Engl
ish (Australia)', ignoring 'English (US)'\n"
Feb 22 23:09:45 fedora sddm-helper-start-wayland[1654]: "qt.qpa.wayland: qtvirtualkeyboard currently is not supported at client-side, use QT_I
M_MODULES=qtvirtualkeyboard at compositor-side.\n"
Feb 22 23:09:45 fedora sddm-greeter-qt6[1715]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Feb 22 23:09:45 fedora sddm-greeter-qt6[1715]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Feb 22 23:09:45 fedora sddm-greeter-qt6[1715]: QQuickView(0x557a99242080) already has a shell integration. Call QWindow::close() first and sho
w it again.
Feb 22 23:10:06 fedora sddm-greeter-qt6[1715]: file:///usr/share/sddm/themes/breeze/Main.qml:241:17 Parameter "username" is not declared. Inje
ction of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.
Feb 22 23:10:06 fedora sddm-helper[1984]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Feb 22 23:10:06 fedora sddm-helper[1984]: pam_kwallet5(sddm:auth): pam_kwallet5: pam_sm_authenticate
Feb 22 23:10:06 fedora audit[1984]: AUDIT1100 pid=1984 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:authentication grantors=pam_unix acct="alfstandard" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 23:10:06 fedora audit[1984]: AUDIT1101 pid=1984 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:accounting grantors=pam_unix acct="alfstandard" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 23:10:06 fedora sddm-helper[1984]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Feb 22 23:10:06 fedora audit[1984]: AUDIT1103 pid=1984 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:setcred grantors=pam_unix acct="alfstandard" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Feb 22 23:10:06 fedora audit[1984]: AUDIT2300 pid=1984 uid=0 auid=1001 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=pam_selinux d
efault-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 ex
e="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty2 res=success'
Feb 22 23:10:06 fedora sddm-helper-start-wayland[1654]: Stopping... "kwin_wayland"
Feb 22 23:10:06 fedora sddm-helper-start-wayland[1654]: "kwin_scene_opengl: Could not delete render time query because no context is current\n
"
Feb 22 23:10:06 fedora sddm-helper[1519]: pam_unix(sddm-greeter:session): session closed for user sddm
Feb 22 23:10:06 fedora audit[1519]: AUDIT1106 pid=1519 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:session_close grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty1 res=suc
cess'
Feb 22 23:10:06 fedora audit[1519]: AUDIT1104 pid=1519 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='o
p=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty1 res=success'
Feb 22 23:10:06 fedora sddm-helper[1984]: pam_unix(sddm:session): session opened for user alfstandard(uid=1001) by alfstandard(uid=0)
Feb 22 23:10:06 fedora sddm-helper[1984]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Feb 22 23:10:06 fedora sddm-helper[2094]: pam_kwallet5: final socket path: /run/user/1001/kwallet5.socket
Feb 22 23:10:06 fedora audit[1984]: AUDIT1105 pid=1984 uid=0 auid=1001 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_o
pen grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_kwallet5,pam_umask
,pam_lastlog2 acct="alfstandard" exe="/usr/libexec/sddm-helper" hostname=fedora addr=? terminal=/dev/tty2 res=success'
Feb 22 23:10:06 fedora sddm-helper[1984]: Starting Wayland user session: "/etc/sddm/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-
needed /usr/bin/startplasma-wayland"
@alinausssieland comparing your ls with @anothermindbomb 's it shows that yours just has rw on User right, while his also has some on Group rights. Could this not be the reason why you get this access denied above, in the log?
P.S.
In my Gnome I do also have a mixture of user/group rw. Just to see that something is not as usual.