HDMI external monitor and audio devices stop working on Fedora 41

Ask Fedora
, , ,
1

Hey, folks! :wave:

So, my problem is a bit hard to explain since it’s actually a few things that started happening all at the same time since I ran dnf upgrade last week (around Feb 10, 2025), so please bear with me.

I’ve been experiencing 4 issues:

  • If I switch inputs in my external video monitor (I also use it in another PC), when I switch back to my laptop with Fedora 41 in it, the video monitor just says “No Signal” and the display on the native laptop screen flickers every ~10 seconds (happens every time I switch inputs in my external HDMI video monitor)
  • Right after I log in, GNOME doesn’t recognize any audio devices, either from my laptop or external video monitor (which has a built-in speaker) (happens 50% of the times I reboot)
  • Right after I log in, GNOME seems to hang for ~5 minutes and I can’t move my mouse and there is no background image, only a solid gray color (after those ~5 minutes the background image loads) (happens on every reboot)
  • Fedora 41 started to take a long to time to power off and reboot. Sometimes it doesn’t reboots at all and I need to physically power it off and power it on again (happens on every power off and reboot)

All these issues never happened before. The only way to solve them is to reboot multiple times until it just works.

I’d really appreciate some help because I need to reboot everyday because of this. I can provide any logs, just ask me.

I tried systemctl --user restart pipewire.service and systemctl --user restart wireplumber.service but to no avail, nothing changed, that’s why I think the issue might be with Wayland or GNOME.

2

FWIW, I’d probably try installing another DE and, ideally, create a new user account to use with it.

For example:

sudo dnf install @budgie-desktop
sudo useradd --create-home edsantos-2
sudo passwd edsantos-2

Then sign out, select the new user, click the gear icon to change the DE to Budgie, and sign back in with the new account.

Edit:

That sounds like something going wrong at a lower level than the DE to me. If it didn’t happen before, I’d suspect a recent kernel/driver update.