Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ctrl-key is stuck after some hotkeys (Bug?)

  • 1 réponse
  • 1 a ce problème
  • 186 vues
  • Dernière réponse par teascade

options supplémentaires

When I press a hotkey that involves Ctrl (ie. opening a new Tab via Ctrl+T or closing one via Ctrl+W) Ctrl sometimes remains stuck until I press it again. This will cause issues ie. when I open a new tab and try to type a new address (or search term), and Ctrl causes new hotkeys to be executed.

I've even tried launching firefox with a new profile, and on safe mode (firefox --safe-mode -p <something-else-than-usual>), so no bookmarks, cookies or extensions should be causing this, and it will still happen sometimes. The annoying part is that this seems to be an issue with performance. It happens less-often with the empty profile and safe mode, but it still happens, especially if I had just opened a new page some tab, causing the most minute thing for firefox to process.

The problem is probably not the computer specs either (below my specs). Indeed, from what I can tell, firefox does not even seem to function particularily slow in any case. Just this ctrl being stuck seems to happen.

I have also tried disabling hardware-acceleration (and explicitly enabling it), no effect.

Other interesting facts I've discovered: - This for sure does not happen in other programs and - This does not happen with the Ctrl for all the keybinds within firefox. For example, Ctrl+A (for select all) does not trigger this

From neofetch my setup is OS: Arch Linux x86_64 Host: MS-7C56 1.0 Kernel: 6.12.8-arch1-1 Uptime: 2 hours, 10 mins Packages: 2370 (pacman), 7 (flatpak) Shell: zsh 5.9 Resolution: 3840x2160 DE: labwc:wlroots WM: sway Terminal: alacritty CPU: AMD Ryzen 9 5900X (24) @ 4.951GHz GPU: AMD ATI Radeon RX 7900 XT/7900 XTX/7900 GRE/7900M Memory: 5531MiB / 32015MiB

(I have no idea why it's reporting that I'm using Sway, I'm most certainly only using labwc, maybe labwc just reports sway for some programs for compatibility) I've installed firefox from pacman, and my current version is firefox 134.0.1-1

And finally firefox --full-version Mozilla Firefox 134.0.1 20250113214611 20250113214611

I'm not sure what else I could share at this point

When I press a hotkey that involves Ctrl (ie. opening a new Tab via Ctrl+T or closing one via Ctrl+W) Ctrl sometimes remains stuck until I press it again. This will cause issues ie. when I open a new tab and try to type a new address (or search term), and Ctrl causes new hotkeys to be executed. I've even tried launching firefox with a new profile, and on safe mode (firefox --safe-mode -p <something-else-than-usual>), so no bookmarks, cookies or extensions should be causing this, and it will still happen sometimes. The annoying part is that this seems to be an issue with performance. It happens less-often with the empty profile and safe mode, but it still happens, especially if I had just opened a new page some tab, causing the most minute thing for firefox to process. The problem is probably not the computer specs either (below my specs). Indeed, from what I can tell, firefox does not even seem to function particularily slow in any case. Just this ctrl being stuck seems to happen. I have also tried disabling hardware-acceleration (and explicitly enabling it), no effect. Other interesting facts I've discovered: - This for sure does not happen in other programs and - This does not happen with the Ctrl for all the keybinds within firefox. For example, Ctrl+A (for select all) does not trigger this From neofetch my setup is OS: Arch Linux x86_64 Host: MS-7C56 1.0 Kernel: 6.12.8-arch1-1 Uptime: 2 hours, 10 mins Packages: 2370 (pacman), 7 (flatpak) Shell: zsh 5.9 Resolution: 3840x2160 DE: labwc:wlroots WM: sway Terminal: alacritty CPU: AMD Ryzen 9 5900X (24) @ 4.951GHz GPU: AMD ATI Radeon RX 7900 XT/7900 XTX/7900 GRE/7900M Memory: 5531MiB / 32015MiB (I have no idea why it's reporting that I'm using Sway, I'm most certainly only using labwc, maybe labwc just reports sway for some programs for compatibility) I've installed firefox from pacman, and my current version is firefox 134.0.1-1 And finally firefox --full-version Mozilla Firefox 134.0.1 20250113214611 20250113214611 I'm not sure what else I could share at this point

Solution choisie

This has been identified as a bug in labwc+fcitx5, so this is resolved.

https://github.com/labwc/labwc/pull/2498

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

options supplémentaires

Solution choisie

This has been identified as a bug in labwc+fcitx5, so this is resolved.

https://github.com/labwc/labwc/pull/2498