Update: Issue disappeared without doing anything. After just letting my computer sit turned off for a few hours I started it back up to troubleshoot. Now it works again. Something happened to break it and then to unfuck it again without any input from me. Something is unstable and I’m gonna try to figure it out.

Started my PC up today, logged in like normal, but my keyboard wont work after logging in. Except for the calculator button. None of the keys will actually do anything. But logging in works normally.

Worked fine last night, no updates have run or anything. Where to start diagnosing this? In a way where I won’t need a keyboard?

Fedora 42 KDE

Edit: Keyboard works fine in a live environment on the USB I used to install yesterday. Tried a different keyboard on my main install, and that didn’t work either. So it’s not the keyboard itself at least

  • Parptarf@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 day ago

    Already checked the i put and that looks to be right. No slow keys enabled in settings and no response holding down keys for up to 15 seconds.

    My keyboard can both use a dongle and BT. But I can’t find it on BT. Other keyboard is the same model, which isn’t ideal but it was worth testing out.

    Also, mouse still works. And I’m logged into here on my browser so I can copy commands and stuff.

    • just_another_person@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      1 day ago

      Checked your accessibility menu and see if anything there may be turned on?

      Also, can you drop to a straight terminal (ALT+F2) and the key card works fine?

      • tal@lemmy.today
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        Also, can you drop to a straight terminal (ALT+F2) and the key card works fine?

        Alt-Fn works to switch among terminals once you’re in a terminal.

        If you’re in Xorg or Wayland already, then you need Control-Alt-Fn to get out to a terminal, and I believe that some distros disable this.

      • Parptarf@lemm.eeOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 day ago

        Tried turning stuff on, then off, then reset to default. Nothing.

        Nothing, except function keys for volume etc. and the calculator keys work when I’m logged in. I can log out and write my password normally.

        I can get to a console from the login screen, which tells me to login. But I get incorrect credentials even though they are correct.

          • Parptarf@lemm.eeOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 day ago

            Logi MX Keys S.

            I had an update available today(after this issue). Ran it but it didn’t fix the issue sadly.

            • just_another_person@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              1
              ·
              1 day ago

              Okay, so let’s try connectit via BT as a test at least. You said it wasn’t showing up in your BT menu, check this out.

              The other thing here is that this is a wireless-only key card, so you’ve got a potential HID configuration problem because of that receiver. The fact that you can actually login first, THEN it stops working tells me it’s something like this. The fact it works fine on LiveUSB screams settings/config issue. You may need that LiveUSB again to go in and chroot some stuff away.

              • Parptarf@lemm.eeOP
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 day ago

                It just works again after the computer being shut off for a few hours. I did quite a few restarts earlier today that didn’t help so something isn’t right. I’m thinking there’s something broken with the HID config myself.

                If I was on Windows I’d reinstall the driver, check chipset driver etc. maybe check if there’s something wrong with Logitech’s software. I’ll do some digging now that I have a keyboard again to see how if I find anything.