What a surprise: After updating to Kernel Linux 6.5.12-300.fc39.x86_64 I can login under Gnome/Wayland again.
Had this been a kernel issue?
Can anybody else confirm this?
Edit:
Sorry this post had been a little too fast. It is not relyable and stable. Login is now successful in about 1/3rd of the login attempts. Befote it was 0%…
There seems to be a change, but not a real solution.
BTW my permissions are set correctly.
Hi everyone, I have encountered same issue.
I can not properly/get stable login on Fedora 39 KDE wayland.
Yes I do have Nvidia card 
and yes I am booting from external SSD and yes it is ASUS TUF A15.
I can get on and boot for the third or fifth time from boot menu options.
Previously I could run on wayland and installed all the needed drivers/system updates.
But I did it only once and then could only boot in x11.
As for now I found a workaround for myself to boot into Fedora 39 KDE Wayland session:
And it works, did that a few times - login again after logout and login after laptop reboot.
PS: sorry if some terminology/texting might sound wrong but that worked for me.
Everyone have a nice day and stay safe 
I am having the same problem. I have only been able to run X11 since upgrading to F39. None of these fixes worked for me. I tried backing up dconf and deleting it to force defaults but that did not work either. I am out of ideas and just waiting for an update to fix this.
So, think I have some workaround, I don’t know if that’s true or not. I read somewhere that early KMS might help with some of the errors that I was encountering on my journalctl. So I created the file /etc/dracut.conf.d/nvidia.conf and force the modules to load?? as suggested here.
I ran dracut --force and rebooted and got a wayland session without it kicking me out to the gdm screen.
Also I updated the grub, and remove the nvidia stuff from there but kept the blacklisting nouveau and I now see the wayland option and I’m able to log in no problem.
The reason I had to remove it from grub is because it’s added when you install akmod-nvidia
Can also confirm this is happening on AMD, specifically Renoir Graphics. Launches on X11 just fine, but the only way I’ve been able to fix this is just by resetting the entire dconf file for GNOME.
dconf reset -f /org/gnome/
Of course, all your gnome configs will be reset, but I was more than willing to do that.
I would be very interested in knowing, whether this solution is persistent for you?
For me it did not work for more than 24 hours…
After tweaking Gnome settings back to my preference, I could not start a Wayland session any longer.
It could be helpful to know what “tweaks” you made. Other threads have reported issues with Gnome extensions. Some extensions are provided by users and it appears not be compatible with the current Fedora 39 versions.
Please see above:
In the meantime I believe, that the system is just running unstable and the root cause is hiding quite well.
Please let me know, if I should do some tests on my system, if you have fresh ideas. Some of the “solutions” mentioned here have worked somehow temporarily, but not persistent.
My tweaks were typically just styling changes such as using adw-gtk3 for gradience and a few changes using GNOME tweaks.
Not much can hide from journalctl, but finding the one line that points to the cause of an issue can be a challenge. There are useful commnd-line options to selec the entries displayed by priority or grep strings.
Are you seeing:
Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
You can use busctl to gather information about org.freedesktop.systemd1 in a terminal.
busctl listNAME PID PROCESS USER CONNECTION UNIT SESSION DESCRIPTION
:1.0 813 systemd-resolve systemd-resolve :1.0 systemd-resolved.service - -
:1.1 809 systemd-oomd systemd-oom :1.1 systemd-oomd.service - -
:1.10 907 udisksd root :1.10 udisks2.service - -
:1.11 900 rtkit-daemon root :1.11 rtkit-daemon.service - -
:1.12 902 switcheroo-cont root :1.12 switcheroo-control.service - -
:1.13 890 avahi-daemon avahi :1.13 avahi-daemon.service - -
:1.14 904 systemd-logind root :1.14 systemd-logind.service - -
:1.15 908 upowerd root :1.15 upower.service - -
:1.1517 46962 fwupd root :1.1517 fwupd.service - -
:1.16 910 abrtd root :1.16 abrtd.service - -
:1.1612 50387 busctl gnw3 :1.1612 session-8.scope 8 -
:1.17 901 accounts-daemon root :1.17 accounts-daemon.service - -
:1.18 898 polkitd polkitd :1.18 polkit.service - -
:1.2 1 systemd root :1.2 init.scope - -
:1.20 997 ModemManager root :1.20 ModemManager.service - -
:1.21 998 firewalld root :1.21 firewalld.service - -
:1.22 1007 NetworkManager root :1.22 NetworkManager.service - -
:1.25 1080 wpa_supplicant root :1.25 wpa_supplicant.service - -
:1.26 1087 cupsd root :1.26 cups.service - -
:1.28 1161 gdm root :1.28 gdm.service - -
:1.3 888 dbus-broker-lau root :1.3 dbus-broker.service - -
:1.31 1204 uresourced root :1.31 uresourced.service - -
:1.38 1312 colord colord :1.38 colord.service - -
:1.4 891 bluetoothd root :1.4 bluetooth.service - -
:1.5 903 systemd-homed root :1.5 systemd-homed.service - -
:1.6 905 systemd-machine root :1.6 systemd-machined.service - -
:1.632 14484 gdm-session-wor root :1.632 session-5.scope 5 -
:1.637 14510 systemd gnw3 :1.637 user@1000.service - -
:1.638 14548 gnome-keyring-d gnw3 :1.638 session-5.scope 5 -
:1.639 14572 gdm-wayland-ses gnw3 :1.639 session-5.scope 5 -
:1.642 14590 gnome-session-b gnw3 :1.642 session-5.scope 5 -
:1.644 14694 gnome-session-b gnw3 :1.644 user@1000.service - -
:1.645 14722 pipewire gnw3 :1.645 user@1000.service - -
:1.646 14724 wireplumber gnw3 :1.646 user@1000.service - -
:1.647 14724 wireplumber gnw3 :1.647 user@1000.service - -
lines 1-36
busctl status org.freedesktop.systemd1PID=1
PPID=n/a
TTY=n/a
UID=0
EUID=0
SUID=0
FSUID=0
GID=0
EGID=0
SGID=0
FSGID=0
SupplementaryGIDs=
Comm=systemd
CommandLine=/usr/lib/systemd/systemd --switched-root --system --deserialize=36 rhgb
Label=system_u:system_r:init_t:s0
CGroup=/init.scope
Unit=init.scope
Slice=-.slice
UserUnit=n/a
UserSlice=n/a
Session=n/a
AuditLoginUID=n/a
AuditSessionID=n/a
UniqueName=:1.2
EffectiveCapabilities=cap_chown cap_dac_override cap_dac_read_search
cap_fowner cap_fsetid cap_kill cap_setgid
cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service
cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock
cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot
cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot
cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config
cap_mknod cap_lease cap_audit_write cap_audit_control
cap_setfcap cap_mac_override cap_mac_admin cap_syslog
cap_wake_alarm cap_block_suspend cap_audit_read cap_perfmon
cap_bpf cap_checkpoint_restore
PermittedCapabilities=cap_chown cap_dac_override cap_dac_read_search
lines 1-36
It is possible that disabling extensions leaves some side-effects (library or misconfiguration).
Moving the user file out of the way (by renaming) fixed it for me!! Thanks! Removing the experimental feature that I had (allowing fractional scaling) did not seem to work for me.
it diesn’t work for me (dconf reset)
In my case : either it boots with Wayland (default boot) and everything is fine.
Either wayland doesn’t launch (I don’t know why) and it boots with w11 instead but I then have a choppy display (latency of about 2 seconds)
Sometimes wayland launches correctly 5 times in a row. Sometimes I have to raise 5 times to get wayland.
This is probably a different problem [quote=“news news, post:54, topic:95501, username:newsnews”]
it boots with w11 instead
[/quote]
Is w11 Xorg or Windows 11? Booting Fedora with broken Wayland support should fallback to Xorg.
Using a terminal, journalctl -b <N> -s wayland output should differ between boots that provide Wayland and boots that fallback to Xorg.
Thank you George,
when I grep ‘org.freedesktop.systemd’ on journalctl, I get the following:
[eth@wlg3060 ~]$ journalctl | grep org.freedesktop.systemd | tail
Nov 30 12:20:13 wlg3060 gsd-sharing[35150]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Nov 30 12:20:13 wlg3060 gsd-sharing[35150]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Nov 30 12:20:29 wlg3060 /usr/libexec/gdm-wayland-session[36081]: dbus-daemon[36081]: [session uid=42 pid=36081] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=42 pid=36082 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Nov 30 12:20:29 wlg3060 /usr/libexec/gdm-wayland-session[36081]: dbus-daemon[36081]: [session uid=42 pid=36081] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Nov 30 12:20:29 wlg3060 gnome-session[36082]: gnome-session-binary[36082]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Fehler beim Aufruf von StartServiceByName für org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Nov 30 12:20:29 wlg3060 gnome-session-binary[36082]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Fehler beim Aufruf von StartServiceByName für org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Nov 30 12:20:30 wlg3060 /usr/libexec/gdm-wayland-session[36081]: dbus-daemon[36081]: [session uid=42 pid=36081] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=42 pid=36181 comm="/usr/libexec/gsd-sharing" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Nov 30 12:20:30 wlg3060 /usr/libexec/gdm-wayland-session[36081]: dbus-daemon[36081]: [session uid=42 pid=36081] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Nov 30 12:20:30 wlg3060 gsd-sharing[36181]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Nov 30 12:20:30 wlg3060 gsd-sharing[36181]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Is there anything to deal with?
Best regards
Thomas
It looks like there are at least two different issues in this thread – one that is “solved” by using a new user login or deleting ~/.config/dconf/user file (may be caused by an extensions that hasn’t been updated for the F39), and one where the wayland session fails to start with “Wayland `service org.freedesktop.systemd1’ failed at login”.
Since this thread is marked as “solved”, we need a new thread for “`service org.freedesktop.systemd1’ failed at login”.
Using tail may have omitted the precipitating event. There is an art to extracting the relevant details from journalctl.
If you don’t have “Problem Reporting” turned on in Gnome Setting Notifications it may help to turn that on in the hope a useful problem report will be generated.
I might also suggest turning on GDM debugging in /etc/gdm/custom.conf.
Good luck, everyone!
Since this thread is marked as “solved”, we need a new thread for “`service org.freedesktop.systemd1’ failed at login”.
new topic : Problems with wayland after updating to fedora 39 - PART 2 - org.freedesktop.systemd1’ failed at login”
Okey! Just installed Fedora 39 with the nvidia rpmfusion driver on plasma and i can confirm that this is the only way to login into Wayland on Plasma, other than that i only get a freeze rear login.
Linux 6.6.7-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Dec 13 21:43:37 UTC 2023 x86_64 GNU/Linux