Bug 2413790 - Spacebar is not cancelling dead keys on Fedora 43
Summary: Spacebar is not cancelling dead keys on Fedora 43
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 43
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: fujiwara
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-11-10 14:57 UTC by cgraeff
Modified: 2025-11-22 01:36 UTC (History)
8 users (show)

Fixed In Version: ibus-1.5.33-2.fc43
Clone Of:
Environment:
Last Closed: 2025-11-22 01:36:54 UTC
Type: ---
Embargoed:
tfujiwar: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ibus ibus issues 2825 0 None open EN compose file is not loaded by default in pt_BR.UTF-8 locale with IBus 1.5.33 2025-11-15 15:48:37 UTC

Description cgraeff 2025-11-10 14:57:21 UTC
In us international and brazillian abnt2 keyboards, characters with diacritics are written using dead keys (e.g. é). However, in some instances it is necessary to write only the diacritic, like when writting source code blocks in markdown (e.g. `cat example.txt`).

The behavior up to Fedora 42 was to hit space to insert the character, but as of Fedora 43, that is not working anymore, the entry is stuck in preview mode and must be cancelled using the esc key.

A description of the issue can be seen on a video on https://discussion.fedoraproject.org/t/spacebar-is-not-cancelling-dead-keys-on-43/171482

Reproducible: Always

Steps to Reproduce:
1. In any text entry, press diacritic dead key (e.g. `)
2. Press space

Actual Results:
Gets stuck in preview mode

Expected Results:
The insertion of only the diacritic character, (e.g. for ` and than space, the ` character should be displayed).

Additional Information:
Note that the insertion of characters with diacritics is working fine, the problem only happens when trying to insert only the diacritic by combining it with space.

Comment 1 Cesar Eduardo Barros 2025-11-11 22:55:51 UTC
Another thread linked to from that one (https://discussion.fedoraproject.org/t/new-accent-keys-typing-behavior/171288) has a workaround: using AltGr+key instead of the key followed by a space. However, it's obscure (I'd never know of it if I hadn't seen that thread), and AFAIK other operating systems also use key followed by a space.

This should have the CommonBugs keyword (it'll affect all Brazilians who are using a Brazilian keyboard), but I don't seem to be able to add keywords to this bug.

Comment 2 Cesar Eduardo Barros 2025-11-11 23:24:47 UTC
GNOME issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/4450

Comment 3 Cesar Eduardo Barros 2025-11-11 23:42:30 UTC
This issue is probably in ibus, not libinput, according to a comment in that GNOME issue.

Comment 4 Cesar Eduardo Barros 2025-11-12 02:30:52 UTC
I've opened an issue in ibus: https://github.com/ibus/ibus/issues/2825

Comment 6 cgraeff 2025-11-12 11:50:48 UTC
Sorry, reposted the links you already posted. Guess I need more coffee.

Comment 7 Gabriel Freitas 2025-11-12 12:12:33 UTC
I had the same issue, it would only happen if the system language was set to Portuguese(Brazil) on Fedora 43, Gnome 49 and US international keyboard layout.
Following this rabbit hole, I don't believe the issue is ibus per se. 

In the issues provided, even though some of the fixes there work, they revolve around configuring the compose file. Well, I never had to do that before, so I assumed Fedora or Gnome had set it up previously.
Fortunately I found the old X11 compose files at `/usr/share/X11/locale/pt_BR.UTF-8/Compose` and `/usr/share/X11/locale/en_US.UTF-8/Compose`. Then 
- I copied both to `$HOME/.config/ibus/Compose.en_US` and `$HOME/.config/ibus/Compose.pt_BR`
- Set the ownership to my user
- Fixed the include reference in the pt_BR file to point to the new path of the en_US version
- Created a symbolic link `ln -s ~/.config/ibus/Compose.pt_BR ~/.config/ibus/Compose`

With these steps the issue was fixed. My conclusion is that Wayland is not providing these default compose files (or they are incomplete), and ibus itself no longer provides them by default as well. Since X11 is no longer a thing in Fedora 43, there were no proper Compose to be found after the update.

Comment 8 Gabriel Freitas 2025-11-12 12:36:31 UTC
Well, I was wrong it was an ibus bug: https://github.com/ibus/ibus/issues/2825#issuecomment-3521678859
The maintainer also provides a simpler workaround then mine:

```
mkdir -p ~/.config/ibus
echo 'include "%L"' > ~/.config/ibus/Compose
ibus restart
```

Comment 9 Mateus Rodrigues Costa 2025-11-15 15:48:38 UTC
I added the ibus issue for easier access.
I also added the CommonIssues keyword so it becomes easier to document the current workaround.

Comment 10 Fedora Update System 2025-11-18 05:31:33 UTC
FEDORA-2025-0e64bbc873 (ibus-1.5.33-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-0e64bbc873

Comment 11 Fedora Update System 2025-11-19 01:27:37 UTC
FEDORA-2025-0e64bbc873 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-0e64bbc873`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0e64bbc873

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

Comment 12 Fedora Update System 2025-11-22 01:36:54 UTC
FEDORA-2025-0e64bbc873 (ibus-1.5.33-2.fc43) 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.