Bug 2278864 - Please support org.freedesktop.locale1 keyboard configuration for Anaconda on Live environment
Summary: Please support org.freedesktop.locale1 keyboard configuration for Anaconda on...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: miracle-wm
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Matthew Kosarek
QA Contact:
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F43BetaFreezeException
TreeView+ depends on / blocked
 
Reported: 2024-05-03 11:54 UTC by Jiri Konecny
Modified: 2025-09-10 03:07 UTC (History)
3 users (show)

Fixed In Version: miracle-wm-0.7.0-1.fc43
Clone Of:
Environment:
Last Closed: 2025-09-10 03:07:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jiri Konecny 2024-05-03 11:54:02 UTC
This is a message for the Miracle spin:

Hello, I’m contacting you on behalf of the Anaconda team to raise awareness that Anaconda has to change the backend which is used to control keyboard configuration of the Live environment. That means that we will depend on the org.freedesktop.locale1 D-Bus API and we are contacting you with a request to support this API. Currently, Anaconda depends on libXklavier library, however, we are forced to migrated from this solution to Wayland compatible solution for various reasons:

* The libXklavier library is deprecated (https://bugzilla.redhat.com/show_bug.cgi?id=1955025 )
* Anaconda have to migrate to Wayland native solution which makes libXklavier to crash
* The libXklavier doesn’t work great in some situations on Wayland environment
  * Anaconda was forced to not be able to configure keyboards which makes user experience worse https://bugzilla.redhat.com/show_bug.cgi?id=2072941 

Also, the Anaconda team got a lot smaller, so we are not in position to maintain both solutions based on the system. That would get us into more bugs in the future which we don’t have capacity to resolve. For that reason we are requesting all the SIGs owning spins on Fedora to implement support which will reflect this DBus API to the Live environment. More precisely, this API will be used by Anaconda to read and change the currently set keyboard layout configuration on Live media. Your Live environment should reflect on these changes and apply them to the running Live environment. I’ll create a system wide change soon to connect all the parties in one place but we wanted to reach all of you beforehand.

What you need to do:
* Verify if you are already reflecting the systemd-localed keyboard configuration on your spin Live installation environment.
* If the above is not correct, please implement this missing communication. For inspiration (can’t be used in this version) feel free to take a look at the Sway solution (https://github.com/alebastr/sway-systemd/blob/main/src/locale1-xkb-config ).

For more information please see this https://www.freedesktop.org/software/systemd/man/latest/org.freedesktop.locale1.html 

We would like to get these changes together with Wayland to switch to Fedora 41 if possible. In case you won’t be able to add support for the DBus service, we will solve this situation with the same approach as described in bug above which means that Anaconda won’t be controlling your system keyboard configuration in the Live environment and users will be requested to set this in the Anaconda for the installed system only.

We are sorry for the inconvenience and we will try to help you with this migration process.

Reproducible: Always

Comment 1 Aoife Moloney 2025-02-26 13:01:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 2 Jiri Konecny 2025-03-28 14:53:53 UTC
Hi, after this was implemented in some environments, we have started to face issues about getting information from the compositor to Localed. Often, we hit a problem that it is not easy to decide the current layout for the Anaconda window, also we found that required APIs are pretty often not present or broken. Based on these issues, we have decided to disable keyboard shortcuts for switching keyboard layouts in Anaconda which is the only requirement using information from the compositor.

Outcome:
Compositor does not need to reflect its configuration to Localed anymore. Compositor is still required to listen on Localed and reflect localed configuration to the compositor.

You can read more details here: https://discussion.fedoraproject.org/t/f41-change-proposal-anaconda-as-native-wayland-application-system-wide/118550/30

Comment 3 Neal Gompa 2025-09-05 03:23:25 UTC
Moving to F43.

Comment 4 Fedora Update System 2025-09-05 03:23:53 UTC
FEDORA-2025-f6dfac5433 (mir-2.22.0-1.fc43, miracle-wm-0.7.0-1.fc43, and 1 more) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f6dfac5433

Comment 5 Fedora Blocker Bugs Application 2025-09-05 03:24:54 UTC
Proposed as a Freeze Exception for 43-beta by Fedora user ngompa using the blocker tracking app because:

 This update to the Mir stack makes it so MiracleWM supports listening to locale1 for locale changes, needed for Anaconda keyboard layout stuff to work properly.

Comment 6 Adam Williamson 2025-09-05 20:58:18 UTC
+4 in https://pagure.io/fedora-qa/blocker-review/issue/1906 , marking accepted.

Comment 7 Fedora Update System 2025-09-06 01:32:10 UTC
FEDORA-2025-f6dfac5433 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f6dfac5433`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f6dfac5433

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2025-09-10 03:07:26 UTC
FEDORA-2025-f6dfac5433 (mir-2.22.0-1.fc43, miracle-wm-0.7.0-1.fc43, and 1 more) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


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