Cannot connect second-display (HDMI) from Laptop [Fedora Silverblue 38]

Hey there, I have been using Fedora Silverblue for a while now, I have most apps installed using Flatpak and some Overlayed packages (Mostly virtualization software and encryption software).

When I upgraded my base Tree (using rpm-ostree upgrade) and rebooted (using systemctl reboot) everything worked fine except being able to connect my second-monitor. I tried to troubleshoot but not sure what I should be looking for.

What happens when I connect an HDMI Cable
The screen starts flashing, in Gnome Settings I can see it detecting the 2nd display and losing it repeatedly)

Hardware Information

  • Graphics: AMD Radeon R5 Graphics

Can anyone help me? What should I be looking for?

Would you consider sharing your HW info ?

P.S.: can you try different HDMI cable(s) as a first quick test ?

I have tried 3 different HDMI Cables

HW as in Hardware Information?

Yes. Issues like this are often HW-specific.

Added some Hardware Information to the main post (Graphics and Model, anything else that would make sense?)

Cannot find anything specific to the laptop, GPU or distro. A workaround would be boot into previous state of Fedora Silverblue, remove/rollback last update and use that older version until there is new kernel/driver update is release. Then try upgrading, expecting that issues that you having are resolved.

I had been doing that for like a month and a half, I needed to upgrade and didn’t know what was the package that was creating problems, when I connect the HDMI Cable there is a new entry in the Gnome Logs app (these messages are sent by gnome-shell):

  • Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).

  • meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed

That’s an old post, but similar to yours - boot - What's the likely cause of a get monitor geometry assertion? - Ask Ubuntu. I know, that you tried 3 different cables, so either you have to try a 4th one :wink: , or wait for a fix, if the problem is caused by a bug, introduced by recent update.

I experience something similar a few months ago.

It turns out the HDMI port of my monitor is problematic.

If you have extra equipment, please try to cross test with different Laptop, Monitor .

I was troubleshooting the components and I did some tests:

TEST 1 - Laptop to another monitor

I tried, using the same Laptop and Cable connect to a television, it worked, this made me think that the problem was the Secondary Display. I then remembered that I had once (when I started having this problem) rolled back and the monitor worked, just not with the latest updates

Test 2 - Another device connecting to the Secondary Display

Since I cannot Rollback anymore (due to upgrading twice since the last time the monitor was connecting to my laptop), I tried to connect the monitor to a TV Box, it connected flawlessly

With these two test I conclude that there is no problem either on the cable or the secondary monitor, so I will do what @arturasb recomended and just wait for an update to a driver that works :confused:

1 Like

Not necessarily true.
Above it was noted that a monitor was the issue, and since the hdmi standards are evolving it is possible that the hdmi port on the monitor has a different standard for connection than your laptop. The system upgrade may have simply exposed the incompatibility that was previously masked.

Testing the monitor on a different system does not mean it is good, but merely shows those two devices are compatible.

Testing a different monitor or a tv on your laptop would be a more definitive test since that verifies the port on the laptop as well. You seem to have done that with test 1 so this exposed the incompatibility between the devices as the cause.

In general, such device issues cannot be fixed unless one reports the bug

  1. with specific details about the devices – both laptop and monitor
  2. with specific details about the software versions that worked and did not work
  3. When the developers have access to exactly the same circumstances (hardware and software) to identify the specific cause and design a fix.

It may be a software regression or it may be an actual hardware issue. This cannot be resolved (except maybe by chance) without the developers being aware of it.