Is it Normal to Experience Strange Input Issues on Linux Compared to Windows?

0
31
Asked By TechyExplorer92 On

I've been using Fedora with the KDE desktop environment, and I've noticed two annoying issues that seem to occur on every Linux distro I've tried, like Mint, Pop!_OS, and Fedora, but I never experience these on Windows. Firstly, when I'm moving tabs in my browser, sometimes the mouse seems overly sensitive, making it feel like it 'sticks' to the tab and drags it into a new window even when I just did a quick click. Secondly, when I type quickly while using Caps Lock, I occasionally end up with double uppercase letters, such as getting 'AA' instead of 'Aa'. This doesn't happen on Windows, no matter how fast I type. I don't think it's a hardware issue since I've seen this behavior on multiple Linux systems. Is there a known reason for this with libinput, KDE, or Wayland? Or is there a solid fix without having to switch to X11?

4 Answers

Answered By InputGuru45 On

It sounds like the first issue could be due to 'tap-and-drag lock' if you're using a touchpad, which you can adjust in the KDE settings. As for the Caps Lock issue, believe it or not, many people have discussed this one. Default Linux settings might be releasing Caps Lock when the key is let go, not when it's pressed, which causes these kinds of typing errors.

Answered By RandomCommenter21 On

I'm not absolutely sure about the first part since your description is a bit unclear, but for the Caps Lock issue, this behavior is quite common among Linux users. There are fixes that involve changing your xkb layouts, so if you look it up, you might find a solution that suits you.

Answered By JustAnotherUser88 On

I’ve encountered similar behaviors across various desktop environments like KDE, GNOME, and others. It often seems to be how input is handled in Linux itself, rather than an issue tied to a specific system.

Answered By CuriousUser123 On

For the tab dragging issue, if it's easily reproducible, you might want to test it on Fedora with the GNOME environment to check if it's a KDE-specific bug. I've found that similar quirks can indeed be tied to the desktop environment. If it doesn’t happen in GNOME, it’s likely a KDE problem, which can occur sometimes since I love KDE but it's not perfect.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.