This update has the same problem as the Fedora 45 gnome-kiosk update: it changes gnome-kiosk's default behavior to disallow VT switches, which breaks both openQA tests and human expectations when running a Fedora install from a dedicated installer image. Those images use gnome-kiosk and it is certainly expected that you are able to switch to a VT to debug installation issues or check log files.
The update needs to contain an anaconda build that passes the argument to gnome-kiosk that enables VT switching.
ignore previous comment:
seems to work fine after manually updating gnome-shell* + mutter to latest rc1. Those were not yet available in updates-testing.
gdm-1:50~rc-1.fc44.x86_64 breaks the login screen for me:
--- 8< ---
Mar 05 18:29:41 gibbon systemd[1]: Starting gdm.service - GNOME Display Manager...
Mar 05 18:29:41 gibbon systemd[1]: Started gdm.service - GNOME Display Manager.
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14051 was already dead.
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14051 was already dead.
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14632 was already dead.
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14632 was already dead.
Mar 05 18:29:43 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:43 gibbon gdm[13650]: Gdm: Child process -14799 was already dead.
Mar 05 18:29:43 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:43 gibbon gdm[13650]: Gdm: Child process -14799 was already dead.
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -14996 was already dead.
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -14996 was already dead.
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -15171 was already dead.
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -15171 was already dead.
Mar 05 18:29:45 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing
Mar 05 18:29:45 gibbon gdm[13650]: Gdm: GdmLocalDisplayFactory: maximum number of display failures reached. Giving up.
Mar 05 18:29:45 gibbon gdm[13650]: Gdm: Child process -15329 was already dead.
--- >8 ---
Downgrading to gdm-1:50~beta-1.fc44.x86_64 fixed it.
Hi @nphilipp, this seems to be weird, because going through GDM git log between beta and rc, there doesn't seem to be a change that could potentially break this. I will ask the gdm maintainer about it.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
jgrulich edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
jgrulich edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
jgrulich edited this update.
New build(s):
Karma has been reset.
jgrulich edited this update.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
jgrulich edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
This update's test gating status has been changed to 'failed'.
jgrulich edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
jgrulich edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
This update's test gating status has been changed to 'waiting'.
jgrulich edited this update.
New build(s):
Karma has been reset.
This update's test gating status has been changed to 'failed'.
This update has the same problem as the Fedora 45 gnome-kiosk update: it changes gnome-kiosk's default behavior to disallow VT switches, which breaks both openQA tests and human expectations when running a Fedora install from a dedicated installer image. Those images use gnome-kiosk and it is certainly expected that you are able to switch to a VT to debug installation issues or check log files.
The update needs to contain an anaconda build that passes the argument to gnome-kiosk that enables VT switching.
KVM: gnome-session-50~rc-1.fc44 removes restart /power options from the control panel
downgrading to gnome-session-0:50~beta-1.fc44.x86_64 restored
ignore previous comment: seems to work fine after manually updating gnome-shell* + mutter to latest rc1. Those were not yet available in updates-testing.
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Generally seems to work well on an older Intel laptop and a VM (did not check/test for the gnome-kiosk regression).
gdm-1:50~rc-1.fc44.x86_64 breaks the login screen for me:
--- 8< --- Mar 05 18:29:41 gibbon systemd[1]: Starting gdm.service - GNOME Display Manager... Mar 05 18:29:41 gibbon systemd[1]: Started gdm.service - GNOME Display Manager. Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14051 was already dead. Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14051 was already dead. Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14632 was already dead. Mar 05 18:29:42 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:42 gibbon gdm[13650]: Gdm: Child process -14632 was already dead. Mar 05 18:29:43 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:43 gibbon gdm[13650]: Gdm: Child process -14799 was already dead. Mar 05 18:29:43 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:43 gibbon gdm[13650]: Gdm: Child process -14799 was already dead. Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -14996 was already dead. Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -14996 was already dead. Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -15171 was already dead. Mar 05 18:29:44 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:44 gibbon gdm[13650]: Gdm: Child process -15171 was already dead. Mar 05 18:29:45 gibbon gdm[13650]: Gdm: GdmDisplay: Session never registered, failing Mar 05 18:29:45 gibbon gdm[13650]: Gdm: GdmLocalDisplayFactory: maximum number of display failures reached. Giving up. Mar 05 18:29:45 gibbon gdm[13650]: Gdm: Child process -15329 was already dead. --- >8 ---
Downgrading to gdm-1:50~beta-1.fc44.x86_64 fixed it.
Hi @nphilipp, this seems to be weird, because going through GDM git log between beta and rc, there doesn't seem to be a change that could potentially break this. I will ask the gdm maintainer about it.
@nphilipp did you downgrade only gdm or the whole update? Can you try again and possibly open a bug report for this issue?
jgrulich edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
This update's test gating status has been changed to 'waiting'.
jgrulich edited this update.
New build(s):
Karma has been reset.
This update's test gating status has been changed to 'failed'.
This update is also now blocked (requires) by PipeWire that is submitted as an update here: FEDORA-2026-e289bfed2e
jgrulich edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
@jgrulich I only downgraded gdm. I’ve just applied current updates, will reboot with the beta, update to the rc, reboot again and report back.
@jgrulich Hmm, now it works. Probably some interplay between new gdm and some other (meanwhile updated) component at the time.
jgrulich edited this update.
New build(s):
Karma has been reset.
This update has been submitted for testing by jgrulich.
This update has obsoleted anaconda-44.24-1.fc44, and has inherited its bugs and notes.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Working good for me.
jgrulich edited this update.
Upgraded from Fedora 43 to 44, all GNOME stuff appears to work as expected (or at least without regressions).
This update has been submitted for stable by bodhi.
salimma edited this update.
This update has been pushed to stable.