Hello,
When I bought my new laptop (MSI Thin GF63 12UCX) I installed Fedora 41 KDE with encryption enabled. Everything is working great, but there’s this issue that has always been bothering me.
Basically, whenever I turn on the PC, Plymouth asks for my passphrase and when I start typing it, the keyboard will become unresponsive for a moment, just enough to make me skip a character or two.
The issue doesn’t seem to present itself if I wait long enough before typing in the passphrase, so usually I would turn on the laptop while preparing the desk and wait for a bit (usually 5s after the prompt appears are enough).
I don’t know what might be causing this issue, and I wouldn’t even know what to try for diagnosing the problem.
Did anyone else experience this? What could I try to see what’s wrong or how to resolve this?
Since installing Fedora 42 (KDE and GNOME editions), I have been experiencing intermittent keyboard issues:
Keys are activated randomly, such as F7 (external display configuration), Tab, Shift etc.
Character sequences such as $ty; ty; tty... appear spontaneously in text fields.
*Once the phrase “georgia nursery” appeared without any action on my part!!!
These behaviors sometimes manifest themselves from the LUKS unlock screen.
A quick reboot doesn’t fix the problem, but a long, complete shutdown followed by a reboot seems to temporarily clear it up.
Additional Information
Hardware: Lenovo G14 V4 AMN laptop
Keyboard: I only use the built-in keyboard, in normal AZERTY.
Fedora version: Fedora 42 KDE / GNOME
Updates: done.
I tested the keyboard on another system, and it works fine, which seems to rule out a hardware issue, with the phrase “Georgia nursery”…
Have you ever encountered this type of problem or do you have any suggestions for solving it?
I feel like I’ve caught a virus, even though I checked the ISO, checksum, PGP…
And I have reinstalled fedora 3 times since the first time:
Installing Fedora: the problem occurs shortly after (Fedora GNOME) > Reinstalling Fedora GNOME > Installing Fedora KDE (fed up with GNOME), the problem occurs 2 days later...