First I tried to install F37 Beta on the Steam Deck only to find out that anaconda was failing because of lcms2 related crash in gnome-kiosk. Then after managing a minimal install in text mode I tried to get gdm working only to find out that gnome-shell was crashing in what looked like the same lcms2 place. Looking around in gnome gitlab I found this https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2627 which is already merged and applying locally to mutter-43.0-3.fc37.x86_64 fixed the gdm crashing here. Apparently this problem will pop-up not only with the Steam Deck's eDP, but other monitors and LCDs as well. Since it prevents the installer from working it could probably be considered a release blocker.
Created attachment 1920953 [details] roll up of the merge that fixed the issue here
That should indeed be fixed and safe to backport.
Proposed as a Freeze Exception for 37-final by Fedora user jadahl using the blocker tracking app because: Apparently Steam Deck's eDP connected panel has garbage EDID, causing crashes in libmutter and effectively gnome-kiosk/gnome-shell, effectively meaning an inability to install. It is fixed upstream by ignoring garbage EDID blobs.
*** Bug 2138909 has been marked as a duplicate of this bug. ***
Accepted as a freeze exception in: https://pagure.io/fedora-qa/blocker-review/issue/998
FEDORA-2022-911f9d72c4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-911f9d72c4
FEDORA-2022-911f9d72c4 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-911f9d72c4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-911f9d72c4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-911f9d72c4 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.