[Touch-packages] [Bug 2044664] Re: HDMI plugin after boot, but display can't work

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? I

[Touch-packages] [Bug 2044664] Re: HDMI plugin after boot, but display can't work

I cannot reproduce it on 2 other devices that I have - rpi 3b - Xilinx Kria KV-240 After debugging it seems that we return in this line: https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-42/src/backends/native/meta- monitor-manager-native.c#L890 if (manager_native->needs_outputs && !can_have_out

[Touch-packages] [Bug 2044664] Re: HDMI plugin after boot, but display can't work

Alongside the #5 I can see the following: 1. If the HDMI is connected during boot, gnome-shell starts normally, I can see the login screen on the HDMI monitor. 1a. If the HDMI is disconnected during boot, gnome-shell fails with Sep 13 08:05:22 mtk-genio org.gnome.Shell.desktop[1452]: Failed to s

[Touch-packages] [Bug 2044664] Re: HDMI plugin after boot, but display can't work

** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- 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 dis

[Touch-packages] [Bug 2044664] Re: HDMI plugin after boot, but display can't work

** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Asa Mirzaieva (asaly12) -- 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: H