You’re going to see some typing errors in this post, and thaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaat is intentioooooooooooooooooooooooooooooooooooooooooooooooooooooooooonal. It’s going to make the post unpleeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeasant to read, but I assure you it’s more unpleasant to type.

The issue: Every 5-10 seconds or so, my laptop has recently started pausing, with one symptom being repetition of any key I happen to be typing at that moment, whether a letter, deletion, or something else. I haven’t changed anything, and something very similar seems to be happening on mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmy Fedora-based desktop.

I have tried thhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhe usual troubleshooting steps, such as watchinggggggggggggggggggggggggggggggggggggggggggggggggggggggggggg my processes, disabling gnome extensions, and I cannot pin down the cause.

(1) Annnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnyone seen anything like this?

(2) Any suggestions for troubleshooting?

The laptop is more than powerrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrful enough, a Gen 8 X1 Carbon. OS and apps are up to date. I assume an OS, gnome, or applicationnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn update has broken something, but I cannot for the life of me pinnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn down where the issue is occurring.

EDIT:

Adding system specs –

Intel® Core™ i7-10610U 16GB Intel® UHD Graphics Gnome/Wayland NixOS 23.11 kernel 6.1.57

EDIT 2:

Well, it appears to be gnome. Switched to KDE and everything is perfectly fine. I don’t like KDE (but I fully respect others’ preferences, just … to avoid unpleasantness). I’m going to do some digging around to see if gnome is conflicting with something in NixOS land.

  • noride@lemm.ee
    link
    fedilink
    arrow-up
    20
    ·
    edit-2
    9 months ago

    I hope I don’t get flayed for saying this, but I actually had this problem on Windows once, and it turned out to be thermal throttling of the CPU. I was going from 4+ghz to around 200mhz and then it would shoot back to normal. Just needed a thorough cleaning of the fans and ducting.

    Thought it was worth mentioning on the off chance it might help someone.

  • stepanzak@iusearchlinux.fyi
    link
    fedilink
    arrow-up
    13
    ·
    9 months ago

    I have no idea how to fix something like this, but what would I do is try to isolate the problem. Boot live iso with another Linux and see if that happens again. If it does, I would try live windows iso to see if it can be because of Linux kernel or drivers. I it happens even on windows, it’s probably a hardware thing.

    • rockSlayer@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      9 months ago

      This is your best bet op. You can’t figure out the issue if you don’t know where the problem is coming from

    • 1024_Kibibytes@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      I would try in the terminal (Ctrl+Alt+F3 or F1 or F2 depending on the distro), and then a live iso, then a live version of Windows or the Windows installer.

    • pukeko@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      LOL.

      Or, rather, LOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOL

  • dingdongitsabear@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    9 months ago

    the least you can do is provide the basics - AMD/Intel, GPU, wayland/x11, os and kernel version, I’m not looking up what an 8th gen x1 runs on.

    as to your question, seen similar with ryzens freezing for seconds intermittently on older kernels.

    • pukeko@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      You’re right, but it’s pretty horrendous typing in this environment so it slipped my mind.

      Intel® Core™ i7-10610U 16GB Intel® UHD Graphics Gnome/Wayland NixOS 23.11 kernel 6.1.57

    • pukeko@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      I have been entertaining myself by reading this post out loud. It sounds like I’m having a stroke over and over.

  • BitSound@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    Can you boot into an old generation and see if that fixes the issue? If it doesn’t maybe check if you’ve updated firmware recently

    • pukeko@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      The repeating is a symptom, and the system pause/stutter/whatever is still happening regardless. I thought about it just as a sanity play, but I’d rather fix the underlying issue.

  • SteveTech@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I actually might be having a similar issue on one of my servers, every 5 to 10 seconds the hypervisor will just freeze for less than a second, and it doesn’t repeat characters but it still makes typing in SSH super annoying. I did find using irqstat that during that time, interrupts from the ahci kernel module would spike into the 50,000s, so I have a feeling it’s to do with that, but I haven’t really figured it out yet, since it somehow doesn’t actually seem to affect my VMs.

    Although it probably isn’t related considering switching to KDE fixed it for you, and I haven’t got display stuff installed.

  • Silveste@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    Is your keyboard connected using USB or Bluetooth? I had similar problem in the past and it turned out that was an issue with my Bluetooth dongle

    • pukeko@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      Integrated laptop keyboard (so I assume USB under the hood?)

  • Yote.zip@pawb.social
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    9 months ago

    My only guess is that maybe your input device is disconnecting, then reconnecting.