Bug 2086885
| Summary: | Dead keys stopped working in Plasma (Wayland) after upgrade to F36 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Göran Uddeborg <goeran> | ||||
| Component: | kf5-plasma | Assignee: | KDE SIG <kde-sig> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 36 | CC: | fedora, jgrulich, kde-sig, me, oliver, rdieter, than | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-05-25 16:58:37 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Göran Uddeborg
2022-05-16 18:17:55 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. 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). 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. (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. (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. (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. 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).
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. 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. 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. 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. This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |