Seems like it's the expected behavior since focal, this is reversed in GNOME 44 (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2821) and in noble (GNOME Shell 46.0) I can no longer reproduce it.
@ccshen(Sam Shen), can we mark this issue as a known bug that is going to be fixed in noble? It does not seem like a critical issue (restarting gdm is annoying though). More information on why other model of hw work: - on rpi there is a "writeback" connector that's always active, so gnome-shell always detects an active monitor and starts - on Xilinx Kria we somehow have an always active Display Port, again gnome-shell does not fail because of this -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/2044664 Title: HDMI plugin after boot, but display can't work Status in webbrowser-app package in Ubuntu: Confirmed Bug description: [Summary] HDMI plugin but display can't work after boot under HDMI only display [Reproduce] 1. Set display configuration as single HDMI only 2. Boot into the system without plugging HDMI cable 3. Ensure system is booted (check it by debug console), then plug HDMI cable 4. Check the image on HDMI monitor [Expected result] Ubuntu desktop should be shown on HDMI monitor [Actual result] Ubuntu desktop was not shown on HDMI monitor [Fail Rate] 100% [Additional information] Platform: Mediatek Genio1200 EVK Ubuntu Version: 22.04.2 LTS Image: baoshan-classic-desktop-2204-x01-20231005-133.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/2044664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
