The shutdown and the boot screens have the same design in UEFI: the OEM logo, with a loading circle and Fedora logo. However, when logging out from the session, the same design appears, which can be weird for newcomers for example.
I'm getting Fatal Error (500) when posting the images, but not when commenting, so it goes:
<img alt="logging-out.png" src="/fedora-workstation/issue/raw/files/324fa242de323fd5238567265a44e11aad59c5b9923b8e25a121db56e000e72b-logging-out.png" /><img alt="shutting-down.png" src="/fedora-workstation/issue/raw/files/cd00434c9dce13eb0169a68866e18bc3c9631e1f3b59205af1a1e68e3a73a988-shutting-down.png" />
Thanks for the suggestion, @limao-doce . We don't tend to track every detail of the workstation user experience in this project, and i think that a change like this would be better reported directly against the relevant project.
Perhaps @jwrdegoede can suggest a good place to report this. I'd be happy to comment from a design perspective.
Metadata Update from @aday: - Issue close_status updated to: Deferred to upstream - Issue status updated to: Closed (was: Open)
The logout screen is not under our control, whenever the GNOME user session stops, be it on logout or on shutdown/restart it releases the framebuffer without doing any sort of handover.
This leads to a brief time when the framebuffer is not owned by any userspace process at which points the kernel shows what I call the "fallback" framebuffer, which is the framebuffer which it inherited from the bootloader/fw at boot. Which is just a black screen with the OEM logo.
Until we fix the lack of handover from the GNOME user-session back to gdm, or to plymouth on shutdown, we can thus not avoid the OEM logo showing for a brief time.
This also means that we cannot really change the shutdown splash design, if we drop the OEM logo there it will still show briefly, which will make things look ugly.
With all that said, trying to fix these handover is something which has be on my radar for a while now and it would be good to have some upstream bug to track this.
It is probably best to track this in plymouth upstream for now.
Please file a new issue for this here: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues
The logout screen is not under our control, whenever the GNOME user session stops, be it on logout or on shutdown/restart it releases the framebuffer without doing any sort of handover. This leads to a brief time when the framebuffer is not owned by any userspace process at which points the kernel shows what I call the "fallback" framebuffer, which is the framebuffer which it inherited from the bootloader/fw at boot. Which is just a black screen with the OEM logo. Until we fix the lack of handover from the GNOME user-session back to gdm, or to plymouth on shutdown, we can thus not avoid the OEM logo showing for a brief time. This also means that we cannot really change the shutdown splash design, if we drop the OEM logo there it will still show briefly, which will make things look ugly. With all that said, trying to fix these handover is something which has be on my radar for a while now and it would be good to have some upstream bug to track this. It is probably best to track this in plymouth upstream for now. Please file a new issue for this here: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues
Thanks for the response. However, I'm a bit confused how to write the bug report in there. Should I mention the framebuffer thing or just suggest to implement a logging out/restarting/shutdown screen?
BTW, I saw that there was some tentative designs for these screens and they look really cool: https://wiki.gnome.org/Design/OS/BootProgress
Login to comment on this ticket.