Bug 2402675 - WebUI: org.fedoraproject.Anaconda.KeyboardConfigurationError: The live system has layout 'typing-booster' which can't be used for installation.
Summary: WebUI: org.fedoraproject.Anaconda.KeyboardConfigurationError: The live system...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda-webui
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Katerina Koukiou
QA Contact:
URL:
Whiteboard: RejectedBlocker https://discussion.fe...
: 2404396 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-09 07:36 UTC by Manish Tiwari
Modified: 2025-10-29 16:50 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Manish Tiwari 2025-10-09 07:36:42 UTC
Installer WebUI Critical Error:
org.fedoraproject.Anaconda.KeyboardConfigurationError: The live system has layout 'typing-booster' which can't be used for installation.

Please attach the log file /tmp/journal.log to the issue.

---[ System & Environment Information ]---
OS: Fedora Linux 43 (Workstation Edition Prerelease)
Anaconda version: 43.41
Anaconda UI version: 52



Reproducible: Always

Steps to Reproduce:
1.Select an IME for example ibus-typing-booster from input sources before initiating anaconda installer
2.
3.

Comment 1 Adam Williamson 2025-10-09 19:50:23 UTC
Can confirm this. It also happens if you run the installer, click "Change system keyboard layout", then add an input method.

Proposing as a Final blocker as a conditional violation of "The installer must be able to complete an installation to a single disk using automatic partitioning" in the case you're using the Workstation live installer and you configure an input method before launching the installer, or from the link on the installer's Welcome page.

For context, installs with non-US keyboard layout have always been tricky on live installs, but I don't think we've ever released in a state where configuring an input method via the desktop caused the installer to *refuse to proceed* before.

Comment 2 Lukas Ruzicka 2025-10-13 10:51:23 UTC
I am not sure I understand the problem correctly. 

1. In my Workstation Live, I cannot see a "typing-booster", but I think this has something to do with some non-latin Asian alphabets, so when I select "Chinese (smart pynyin)" I cannot proceed with installation with the described error. However, I am not sure if the system could be installed with just this one way to enter characters. Everything would be affected, passwerds, login names.

2. With latin input sources, I cannot install with two input selected, I always must choose one. Is this a blocking feature?

3. When I select one latin input source in the system and then start WebUI, everything works as expected.

I assume that what is a problem here is that I cannot select more than one inputs?

Comment 3 Kashyap Chamarthy 2025-10-13 16:12:48 UTC
(In reply to Manish Tiwari from comment #0)
> Installer WebUI Critical Error:
> org.fedoraproject.Anaconda.KeyboardConfigurationError: The live system has
> layout 'typing-booster' which can't be used for installation.
> 
> Please attach the log file /tmp/journal.log to the issue.

Also, I don't see any attachment here.  Can you please add it?

[...]

Comment 4 Lukas Ruzicka 2025-10-13 18:24:42 UTC
AGREED RejectedFinalBlocker

Discussed at the 2025-10-13 (blocker / freeze exception) review meeting:

The typing booster doesn't seem necessary to complete an installation, users can pick a different keyboard layout. If this is not the case, please propose again.

https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2025-10-13/f43-blocker-review.2025-10-13-16.00.txt

Comment 5 Adam Williamson 2025-10-15 01:56:27 UTC
Lukas: yes, more or less. This is a similar case to the 'switched layout' case where Russian, Ukrainian etc. users need two xkb layouts configured, one for native characters, one for ASCII characters. CJK users generally configure a keyboard layout for inputting ASCII, and an input method for inputting native characters. A contributing issue here is that, on Workstation live, anaconda literally tells you to 'configure the system layout' or something like that, which link launches the GNOME control center. If you put a link like that in front of someone who uses a switched layout or an input method, they will quite likely set things up the way they expect things to be set up - two layouts, or a layout and an input method - and then we reject it.

Unfortunately I'm not sure this is really fixable for F43, as it requires a chunk of work on webui :/ The patch to allow switched layouts is already probably far too big to take into F43 - https://github.com/rhinstaller/anaconda-webui/pull/1044 .

So I think our best option is to take the more limited fixes we have that provide somewhat better implementation of the not-very-good current design (where we require exactly one, ASCII-capable layout to be configured), document it, and come up with better designs for F44.

Comment 6 Adam Williamson 2025-10-20 15:15:32 UTC
*** Bug 2404396 has been marked as a duplicate of this bug. ***

Comment 7 Adam Williamson 2025-10-20 15:20:34 UTC
I actually think we should reconsider this one. Yes, you *can* just pick another input configuration, but the current experience is very weird and confusing for folks who use switched layouts or input methods. I think we need to do one of the following:

1. Fix up and merge the pending rewrites
2. Update the error messages to give a clearer explanation that acknowledges we are asking switched layout and input method users to do something sub-optimal

Proposing as a violation of any "must complete an install" criterion in the case that you use the provided 'configure system layout' (or whatever the text is) link in Workstation live to configure more than one keyboard layout, or a keyboard layout plus an input method. With the note that *this is entirely normal* for quite a lot of people, and the thing they will naturally do if you give them a link that says that.

Comment 8 Lukas Ruzicka 2025-10-20 18:45:47 UTC
Discussed at the blocker review meeting on 20th Oct. 2025

AGREED: RejectedFinalBlocker 

After extensive analysis we agreed that, while the current state is pretty unfortunate, Workstation is no worse than F42 and KDE is manageably awkward. We accept it as an FE so we could potentially land improved error messages and possibly well-tested improvements if there's a one week slip.

https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-10-20/f43-blocker-review.2025-10-20-16.02.html

Comment 9 Lukas Ruzicka 2025-10-20 18:47:53 UTC
Discussed at the blocker review meeting on 20th Oct. 2025

AGREED: RejectedFinalBlocker AcceptedFinalFreezeException

After extensive analysis we agreed that, while the current state is pretty unfortunate, Workstation is no worse than F42 and KDE is manageably awkward. We accept it as an FE so we could potentially land improved error messages and possibly well-tested improvements if there's a one week slip.

https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-10-20/f43-blocker-review.2025-10-20-16.02.html

Comment 10 Adam Williamson 2025-10-27 16:38:06 UTC
F43 is done, dropping metadata.


Note You need to log in before you can comment on or make changes to this bug.