#4686

fcitx5 occasionally gets stuck until a full system restart

OpenAdalynBlackopened 17d ago

Rarely, after long sessions of leaving the desktop running, fcitx5 suddenly breaks entirely, acting as though keys are stuck down. Logging out and back in does not fix the issue, and neither does restarting fcitx5. A full system restart consistently fixes the issue. To be specific, fcitx5 stops handling new inputs. On some windows, it detects as constantly holding a single key/keybind (often Ctrl+T on the browser, or Enter in a terminal), and on others it doesn't detect any inputs at all. Stopping fcitx5 using the tray icon fixes the stuck keys, but the system has to be restarted to resolve the issue. I have never had this behaviour with other window managers, and it's only been an issue on Niri more recently

Configs [niri_configs.zip](https://github.com/user-attachments/files/33409250/niri_configs.zip)

System Information

  • niri version: niri 26.04
  • Distro: Fedora 44
  • GPU: Nvidia RTX 3070
  • CPU: Intel I7 11700F

Checklist

  • I searched existing issues and discussions and this issue was not already reported.
  • I did not use an LLM to write this issue.

Activity

15
YaLTeR16d ago

Could you please try to see if it happens on niri-git? https://copr.fedorainfracloud.org/coprs/yalter/niri-git/

YaLTeR16d ago

Also when it happens, attach niri logs from journalctl --user-unit=niri -b

AdalynBlack16d ago

I'll give niri-git a try

scanning through the logs for the current session, I'm not seeing any errors or warning that seem obviously related to the issue, and re-running fcitx5 shows nothing, despite the fact the the issue occurs immediately upon starting (for the current session at least, once I restart, I expect the issue to resolve itself for a few days)

YaLTeR16d ago

If it survives a fcitx restart, then also record WAYLAND_DEBUG=1 fcitx5 2>fcitx.log and try to trigger it a few times (after you reproduce on niri-git ideally)

AdalynBlack16d ago

niri-git is not launching The first time, it gave me a solid black screen, and the second time it just kicked me straight back to the login screen

AdalynBlack16d ago

Might be an unrelated issue actually, gnome is doing the same thing...

AdalynBlack16d ago

OK no, gnome does launch, I just hadn't restarted sddm properly. Niri-git just gives an infinite black screen

YaLTeR16d ago

Use Super+Shift+E Enter to exit it normally (it's just the display output that's not working), then log into GNOME and do journalctl --user-unit=niri -b and upload here

AdalynBlack16d ago

Ah, it didn't even install niri-git, since niri-settings conflicted. Even now with niri-git properly installed, it's still giving a black screen

AdalynBlack16d ago

Seems to be an nvidia driver issue I'll get back to you once I figure that out

AdalynBlack16d ago

Nvidia issue resolved, I had akmod-nvidia and akmod-nivida-open installed at the same time. The nvidia-open module got updated, but the main nvidia module did not, which caused nothing to be able to connect to the module properly. Uninstalling akmod-nvidia and its generated kmod-nivida packages, followed by a restart fixed that particular issue. Entirely my bad, not anything Niri-related, honestly surprised Gnome was even launching

I am now properly on niri-git

$ niri -V
niri 26.04 (0.0.git.2965.4263c9a1)

I'll grab some logs for you once the issue happens again

Sempyos10d ago

@AdalynBlack anything yet..?

AdalynBlack10d ago

nothing yet it's quite a rare issue, it could easily take a week or two before it pops up again

Sempyos10d ago

Thanks

Pulsar335503366d ago

I ran into this problem too, but I forgot to capture the logs 😭