Bug 2451402 - System frequently fails to boot to graphical target
Summary: System frequently fails to boot to graphical target
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 43
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-25 17:57 UTC by Robin
Modified: 2026-04-21 22:28 UTC (History)
20 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robin 2026-03-25 17:57:06 UTC
As of the last two weeks I have been having potentially two separate issues.

The first one was random system freezes throughout the day. This one seems to have been resolved by disabling power saving features in UEFI.

The second problem is that my system no longer consistently boots to the default graphical target.

I have a workaround: if I edit my kernel command line in grub to say "systemd.unit=multi-user.target" I can boot without issue and after that I have had good success with logging in and running: sudo systemctl isolate graphical.target

Reproducible: Sometimes

Steps to Reproduce:
1. Boot my computer
2. Sometimes it works, sometimes it doesn't
3.
Actual Results:
The boot process stalls. When I eventually get into my system I can see this logged as the last line from a failed boot:

Mar 24 09:22:45 systemd[1]: user: start operation timed out. Terminating.

On a successful boot I can see this:
sudo journalctl -b -1 -u user
Mar 24 09:21:59 systemd[1]: Starting user - User Manager for UID 60578...
Mar 24 09:22:00 (systemd)[2675]: pam_unix(systemd-user:session): session opened for user gdm-greeter(uid=60578) by gdm-greeter(uid=0)
Mar 24 09:22:45 systemd[1]: user: start operation timed out. Terminating.

Which made me think this is a GDM issue.

Expected Results:
System boots normally.

Additional Information:
Another user has reported, what seems to me, the same problem on the forums: https://discussion.fedoraproject.org/t/fedora-freezes-just-before-login-screen/183173/9

Comment 1 Robin 2026-03-27 17:18:12 UTC
My system has now booted successfully two days in a row after upgrading the kernel to: 6.19.9-200.fc43.x86_64 so this might very well have been a regression in the AMD Ryzen support.

Comment 2 Robin 2026-03-31 22:30:42 UTC
And there we go. Just had multiple system freezes today.

The first one I could still hear music playing but all input and rendering was completely frozen. I then upgraded to 6.19.10 after which I got another freeze, at this point I could switch between windows and the system would take input but refused to start any new processes. I have now downgraded to 6.17.1-300 in the hopes that this will finally solve my problem.

Comment 3 Robin 2026-04-15 16:26:15 UTC
It's now been 2 weeks without a single freeze running the 6.17.1 kernel. Something is definitely rotten with newer 6.18.x and 6.19.x kernels.

Comment 4 Adam Williamson 2026-04-16 16:19:08 UTC
It might be good to report this to https://gitlab.freedesktop.org/drm/amd/-/issues if you did not already. DRM issues are *usually* upstream, we do not patch these drivers downstream much.

Comment 5 Robin 2026-04-21 22:28:52 UTC
Reported upstream as suggested: https://gitlab.freedesktop.org/drm/amd/-/work_items/5205


Note You need to log in before you can comment on or make changes to this bug.