Bug 2086885 - Dead keys stopped working in Plasma (Wayland) after upgrade to F36
Summary: Dead keys stopped working in Plasma (Wayland) after upgrade to F36
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kf5-plasma
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-16 18:17 UTC by Göran Uddeborg
Modified: 2022-11-07 14:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)
This specific update run broke my dead keys (21.26 KB, text/plain)
2022-10-06 08:44 UTC, Eelko Berkenpies
no flags Details

Description Göran Uddeborg 2022-05-16 18:17:55 UTC
Description of problem:
After upgrading to Fedora 36, the dead keys stopped working. Using them has no effect, typing dead_acute followed by an e shows just an e.


Version-Release number of selected component (if applicable):
Fully upgraded Fedora 36. I don't really know which component is guilty, I selected a general plasma component for this report.


Steps to Reproduce:
1. Create a new account to get a clean environment
2. Log in to the account in a Plasma session
3. Log out
4. Log in to the same account again.


Actual results:
Dead keys work in the first login, but no longer in the second or later sessions.


Additional info:
I have upgraded two laptops to Fedora 36, but only one of them shows this behaviour. Probably some difference in the installed packages cause the issue, but I have failed to figure out which one.

Removing the entire .config tree from the home directory seems to reset things so the dead keys work again for one session.

This paragraph may or may not be relevant: The behaviour with the dead keys, when they work, are slightly different. In Firefox, I see what I think is called a "preview", I see the acute accent with an underline until I type the next key. In Konsole and XTerm nothing is shown when I type the dead key, but when I type the e it comes with an accent. Thus it is not a Wayland/X11 difference, since Konsole is a Wayland application while XTerm is not.

This appears specific to KDE. If I create an account and use Gnome sessions the dead keys continue to work after having logged out and in again.

In case it matters, SDDM is the login manager for all the experiments.

Comment 1 Göran Uddeborg 2022-05-17 16:21:20 UTC
I have now "bisected" what exact files under .config cause this behaviour. It is the two files under .config/environment.d, imsettings-gtk.conf and imsettings-qt.conf. Removing them makes the dead keys work in the following session.

These files seem to get recreated on each login, so the following session is broken again. From what I can tell, it is the libraries in imsettings-systemd that keep recreating these files each time. They get overwritten if I try to put something else in them. I'm not sure if this indicates a bug in imsettings-systemd. As it seems to work in Gnome, I don't really believe that, but I haven't figured out how this input method thing really work.

It is not enough to remove only imsettings-qt.conf. Both that file and imsettings-gtk.conf need to be removed before the dead keys start working again.

Comment 2 Göran Uddeborg 2022-05-23 08:36:37 UTC
Testing by removing the imsettings-systemd package and the created config files seems to work around the problem except for the proprietary Slack program. Everything else seems to work again, and I haven't noticed any drawbacks (yet).

Comment 3 Oliver Sampson 2022-10-04 09:35:48 UTC
I have the same issue, also with two systems, one with the problem and one without.

However, my two systems are running KDE and X11.

The primary difference between them is that the one with the broken dead keys is a new F35 install upgrade to F36, and the correctly working system is much older. The first Fedora install on that computer must be F27 or so, and continuously upgraded since then.

Comment 4 Oliver Sampson 2022-10-04 09:36:49 UTC
(In reply to Göran Uddeborg from comment #1)
> I have now "bisected" what exact files under .config cause this behaviour.
> It is the two files under .config/environment.d, imsettings-gtk.conf and
> imsettings-qt.conf. Removing them makes the dead keys work in the following
> session.

I tried this on my KDE/X11 system and it didn't work for me. My dead keys are still very much dead.

Comment 5 Oliver Sampson 2022-10-04 09:45:13 UTC
(In reply to Oliver Sampson from comment #4)
> (In reply to Göran Uddeborg from comment #1)
> > I have now "bisected" what exact files under .config cause this behaviour.
> > It is the two files under .config/environment.d, imsettings-gtk.conf and
> > imsettings-qt.conf. Removing them makes the dead keys work in the following
> > session.
> 
> I tried this on my KDE/X11 system and it didn't work for me. My dead keys
> are still very much dead.

I tried removing imsettings-systemd and removing the files in .config/environment.d/ and the keys are still not working with the German default layout in KDE Keyboard settings.

Comment 6 Oliver Sampson 2022-10-05 07:13:48 UTC
(In reply to Oliver Sampson from comment #3)
> I have the same issue, also with two systems, one with the problem and one
> without.
> 
> However, my two systems are running KDE and X11.
> 
> The primary difference between them is that the one with the broken dead
> keys is a new F35 install upgrade to F36, and the correctly working system
> is much older. The first Fedora install on that computer must be F27 or so,
> and continuously upgraded since then.

The plot thickens: I have a third machine that I upgraded from F35 to F36 that is even older than the properly working machine. (I think it started with Fedora 17.) The dead keys are also not working properly on that machine.

Comment 7 Eelko Berkenpies 2022-10-06 08:44:29 UTC
Created attachment 1916385 [details]
This specific update run broke my dead keys

After a recent update my dead keys also stopped working. Not sure what broke it and also tried suggestions in this thread to fix the problem.

Tried removing .config/environment.d, imsettings-gtk.conf and imsettings-qt.conf as suggested by Göran Uddeborg. Didn't work for my primary profile (I prefer not to remove the whole .config directory at this point so I have not tried that yet). A newly created profile doesn't seem to have the problem, at least not after the first login (have not tested if it's still working after the next login).

I'm using using the "English (US)" with the "English (US, intl., with dead keys)" variant. 

System is fully up to date (F36) and not sure where to look and what to try. Things worked perfectly fine before this specific update run. Maybe someone can spot a specific package which could cause this behavior? In the mean time I switched back to a non-dead keys profile (which is working fine).

Comment 8 Oliver Sampson 2022-10-24 05:08:33 UTC
I haven't had to use any dead keys for a while, but I just did, and they are working again. I'm on kernel 5.19.12-200.fc36.x86_64.

Comment 9 Eelko Berkenpies 2022-10-31 09:01:35 UTC
Dead keys are also/still broken in F37. Also, problem occurred on my fully updated laptop (F37) too. 

Had a minor breakthrough though. I switched from KDE Plasma Desktop/X11 to KDE Plasma Desktop/Wayland on both my desktop and laptop and that seems to work fine for now.

Comment 10 Oliver Sampson 2022-10-31 09:23:31 UTC
I've just checked this again and the dead keys are still broken. I have no idea what has changed. Th only change I've made to my system this week is uninstalling nodejs and installing a newer version.

Comment 11 Oliver Sampson 2022-11-07 14:41:28 UTC
I have more information that may also explain why it sometimes works and sometimes not.

When I try dead keys in Konsole or in Kate, for example, the dead keys do not work.

When I try dead keys in Firefox, Chromiumn or in Signal for Desktop, they do.

Hopefully this will help narrow down the problem.


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