Currently there are a number of issues with the way that the Anaconda web UI appears in the live session:
It would be great if we could figure out how to resolve these.
@stransky @fmuellner @rstrode @jkonecny
Metadata Update from @aday: - Issue set to the milestone: Fedora 39 - Issue tagged with: installation
Thanks for the heads up. We are aware of these and trying to find a solution.
Currently there are a number of issues with the way that the Anaconda web UI appears in the live session: the window has a close button - https://bugzilla.redhat.com/show_bug.cgi?id=2230053
Why not to use kiosk/fullscreen mode? Or disable the system titlebar (you can force disable it). Or I can create a Fedora specific fix (perhaps under pref?) to remove the close button completely.
the window title says "Mozilla Firefox" - https://bugzilla.redhat.com/show_bug.cgi?id=2230058
Enabled system titlebar, it's generated by system. Can be changed by .desktop file.
if you go to the overview, the window has the Firefox icon - https://bugzilla.redhat.com/show_bug.cgi?id=2230072
App icon can be also set by .desktop file. You may create a .desktop file for installer (anaconda.desktop ?) and set app name/icon as you wish there.
It would be great if we could figure out how to resolve these. @stransky @fmuellner @rstrode @jkonecny
bugzilla. redhat.com works better for me as I'm getting updates from it and it's more comfortable. Please file #BZ for the issues (titlebar + icon/app name).
Thanks for the responses, @stransky !
Why not to use kiosk/fullscreen mode?
Various reasons, including:
To be clear: These are not bugs in Firefox directly; these are problems with using Firefox the way we're using Firefox, as a web app viewer.
Ideally, we'd be able to have an embeddable web view in an app and use that. We could do that with WebKitGTK, but we had to switch to Firefox due to supportability decisions (outside of our team) regarding WebKitGTK.
Firefox's PWA support would've been great and would've addressed these issues. But Firefox dropped support for PWA a few releases ago.
Kiosk mode is unsuitable for the reasons Allan mentioned, and for a few others too (such as needing a second window in some cases: for bug reporting, for using an app for partition editing, etc.)
Therefore, we've been trying to make Firefox suitable as much as possible — but we're running into the issues mentioned at the top and need help fixing these.
While a wrapper script and custom desktop might be able to be made, it hasn't been done yet. And we need help with that. And the title thing? I'm not sure how to fix that in current Firefox — does it need recompiling Firefox (I hope not!) — but we don't know, and need help.
This issue is to asking for help with the problems we're encountering above. Again: These are not Firefox bugs, but these are issues we're running into with using Firefox as a web viewer. (We've already worked around a lot of other Firefox-as-a-webviewer issues we encountered, but we haven't been able to figure these out yet and would like some assistance on these.)
Thanks!
Yes. But Bugzilla is just a tool and we can use it for such task too to better track changes/fixes.
@stransky thanks to your suggestions we should be able to resolve most of the issues by creating a custom script to run FF with our custom desktop file.
However, it seems that we are not able to change the window title. For that I created a BZ for you: https://bugzilla.redhat.com/show_bug.cgi?id=2230336 . Could you please take a look on this?
Adding another one to the list: https://bugzilla.redhat.com/show_bug.cgi?id=2231085
The issue is that gsettings get org.gnome.desktop.input-sources mru-sources returns empty value which is used by our new code to find what layout should be used for virtual console keymap.
gsettings get org.gnome.desktop.input-sources mru-sources
Today I tried a nightly ISO from yesterday. Now that the various components have been plumbed together, I can see the following issues:
In general, it doesn't feel like the experience hangs together. This is primarily caused by:
Some more warts:
The Workstation WG discussed these issues today and agreed that while the new installation workflow has a lot of warts to be addressed, none of these issues are blockers. We should work together to address as many as possible. Most seem straightforward; however, we're concerned by the long 10-second delay before starting gnome-initial-setup and anaconda, as we don't know what's causing that.
We want the quick settings menu in gnome-shell to not be displayed at all, which would eliminate Allan's sublist of issues associated with that. Only the accessibility menu (which is currently missing) should be displayed. It's OK for the accessibility menu to be English only in order to avoid another session switch.
We also noticed a couple more serious issues. I selected English (Dvorak) keyboard layout in gnome-initial-setup and entered my LUKS passphrase in that keyboard layout. But anaconda used English (US) for the installed system, so it's not possible for me to unlock the installed system because I don't know how to type my passphrase in this keyboard layout. The scheme for detecting the current keyboard layout that i proposed here was not implemented. I will propose this bug to block the Fedora 39 beta release as the installed system is effectively unusable.
Additionally, it seems the installer is not localized into Spanish, the first language I tested. It seems like there is very little time remaining to land localizations. Could you please report on the status of localization for the languages with the most users, Spanish and Chinese? The Working Group didn't discuss this yet, but I expect this will be a major concern and likely blocker, since English should not be a requirement to install Fedora.
Today I tried a nightly ISO from yesterday. Now that the various components have been plumbed together, I can see the following issues: After the desktop is shown, there's a delay before the initial setup window appears
I believe this is from an selinux issue regarding geolocation that's already filed but I need to confirm that. Will investigate.
The first screen just says "Welcome", which feels a bit ambiguous. Existing Fedora users might be unsure what they are looking at. Changing the window title to "Fedora Setup" might help.
We could probably change that.
The quick settings menu is visible with all the usual content.
This sounds weird, like the gnome-initial-setup shell session isn't getting run in gnome-initial-setup mode.
The text doesn't follow the selected display language.
Are you talking about the installer or the whole desktop? If the installer, they have a bug for it with a fix. Otherwise, I'll try the iso and see if i can reproduce.
The lock button doesn't have any effect. The installer doesn't respect the dark mode setting. If I select log out, the dialog reads "Log Out gnome-initial-setup". I can activate power saver mode. Is that really desirable for installation?
None of these should be there. it's for some reason not getting started in the right mode. will investigate.
There's no accessibility menu.
sounds like we may need always-show-universal-access-status in the dconf config.
always-show-universal-access-status
"Install or try" page: It doesn't say what will we be installed - there's no reference to the product name or version.
Can you provide a mockup of what you'd like it to look like?
There's no back button.
okay will investigate
If I click "Install...", the window disappears and there is a long delay before the installer window is shown (I counted 13 seconds). There's no feedback during this time.
I believe there's an open bug about this.
The installer window pops up in a different area of the screen from initial setup and looks really different. Various issues with the installer window: Window title is "Anaconda Web UI - Mozilla Firefox".
This is fixed upstream
There's a close button.
This might be hard to fix.
After installation has completed, the "Quit" button restarts the system, which is surprising (the button label should indicate what the button does).
I believe this is a known issue that the anaconda team is fixing.
When you restart to the newly installed system, initial setup is shown with the same language and keyboard selection pages that you completed previously. This is repetitious and feels a bit broken.
The fixes for this is almost ready to land upstream in anaconda. The gnome-initial-setup side is already fixed downstream.
So the localizations should work soon? That's good.
Allan is specifically talking about the quick settings menu, so let's just not show it.
Bug report for broken keyboard layout at LUKS passphrase prompt., proposed as a beta blocker.
I just realized the gnome-initial-setup menu weirdness isn't because it's getting run in the wrong mode, it's because it's getting run with the wrong dconf settings. that's fixed here:
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/212
But it's not in fedora yet. will fix.
"Install or try" page: It doesn't say what will we be installed - there's no reference to the product name or version. Can you provide a mockup of what you'd like it to look like?
The simplest fix would be to change the page title like so:
<img alt="Screenshot_from_2023-08-30_15-49-13.png" src="/fedora-workstation/issue/raw/files/a7d74608a3c3ba64a4642420cb3a80b57a1775196b78bdfdbb32e0d003a0a774-Screenshot_from_2023-08-30_15-49-13.png" />
I've changed the other text in that mockup - I think that that this is a bit better.
The long delay I'm seeing when Anaconda is launched seems like the most severe issue. I've proposed it as a final blocker: https://bugzilla.redhat.com/show_bug.cgi?id=2236438
@stransky Is there any hope to get SSB/PWA support added to Firefox in the near future? PWA adoption seems have taken off after support was deleted from desktop Firefox three years ago...
I hear first time about it. And I don't think they'll add it back. But we can use modified kiosk mode for it - it has all the features you want (website displayed without any control/menus etc.).
We only need to change window size from fullscreeen to normal which isn't any big deal. We can do any Firefox update/tweaks we want, just tell me what you need to do.
Looks like PWA is available as extension - https://github.com/filips123/PWAsForFirefox
We will follow your recommendation @stransky about what is recommended to use.
About the extension, I don't see it packaged into Fedora not sure if that is a problem for us.
As the solution will be used in RHEL 10 as well, then I would prefer to use what's built in rather than rely on 3rd party extensions (which we really don't want to support).
Login to comment on this ticket.