Results 1 to 7 of 7

Thread: USB Mouse & Keyboard Problems

  1. #1

    Default USB Mouse & Keyboard Problems

    Hi!
    I was happily using tumbleweed until an update around February, 23th (I recall a new kernel). From that day on my mouse and keyboard (both USB) don't work well.
    First symptom: The user login screen switches both devices off. I have to pull the cables off and reinsert them to be able to select a user and / or enter a password
    Second symptom: Both devices loose events. To write this text I nearly have to press every key two or three time to have them recognized. Same for the mouse. I have to repeat clicks.

    I did a look at /var/log bud didn't find any hint.

    How to search for the bug? Any ideas?

  2. #2
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,212

    Default Re: USB Mouse & Keyboard Problems

    Quote Originally Posted by riccardoescher View Post
    I was happily using tumbleweed until an update around February, 23th (I recall a new kernel). From that day on my mouse and keyboard (both USB) don't work well.
    It does seem to be a problem with the kernel. There are comments about the problem on the factory mailing list:

    https://lists.opensuse.org/opensuse-.../msg00055.html
    Regards, Paul

    Tumbleweed (Snapshot: 20190909) KDE Plasma 5
    Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected
    2x Leap 15.1 KDE Plasma 5

  3. #3
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,763
    Blog Entries
    14

    Default Re: USB Mouse & Keyboard Problems

    Quote Originally Posted by riccardoescher View Post
    Hi!
    I was happily using tumbleweed until an update around February, 23th (I recall a new kernel). From that day on my mouse and keyboard (both USB) don't work well.
    First symptom: The user login screen switches both devices off. I have to pull the cables off and reinsert them to be able to select a user and / or enter a password
    Second symptom: Both devices loose events. To write this text I nearly have to press every key two or three time to have them recognized. Same for the mouse. I have to repeat clicks.

    I did a look at /var/log bud didn't find any hint.

    How to search for the bug? Any ideas?
    Install the xf86-input-libinput package and reboot. If you already messed around with the touchpad settings in Systemsettings - Input Devices, restore those to defaults.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  4. #4
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,212

    Default Re: USB Mouse & Keyboard Problems

    These also:
    https://lists.opensuse.org/opensuse-.../msg00570.html
    https://lists.opensuse.org/opensuse-.../msg00577.html

    Don't seem able to find any actual bug reports though...

    Perhaps you should file a bug report at:
    https://bugzilla.opensuse.org/

    Or, as the kernel seems implicated:
    https://bugzilla.kernel.org

    Edit: Just seen Knurpht's reply... hopefully that will solve your problem.
    Regards, Paul

    Tumbleweed (Snapshot: 20190909) KDE Plasma 5
    Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected
    2x Leap 15.1 KDE Plasma 5

  5. #5

    Default Re: USB Mouse & Keyboard Problems

    Thank you Paul for the two answeres, it gives me the impression not to be alone with my problem (symptom 1). I have disovered today where the message are hidden (journalctl). Difficult to interpret.
    The only error message I can find is:

    ar 14 21:25:00 linux-3hsx sddm-greeter[2970]: QObject: Cannot create children for a parent that is in a different thread.
    (Parent is SDDM::GreeterApp(0x7ffd76179840), parent's thread is QThread(0xbc0790), current thread is QThread(0xc1c050)
    Mar 14 21:25:00 linux-3hsx sddm-greeter[2970]: QObject: Cannot create children for a parent that is in a different thread.
    (Parent is SDDM::GreeterApp(0x7ffd76179840), parent's thread is QThread(0xbc0790), current thread is QThread(0xc1c050)
    Mar 14 21:25:00 linux-3hsx sddm-greeter[2970]: QObject: Cannot create children for a parent that is in a different thread.
    (Parent is SDDM::GreeterApp(0x7ffd76179840), parent's thread is QThread(0xbc0790), current thread is QThread(0xc1c050)
    Mar 14 21:25:00 linux-3hsx sddm-greeter[2970]: QObject: Cannot create children for a parent that is in a different thread.
    (Parent is SDDM::GreeterApp(0x7ffd76179840), parent's thread is QThread(0xbc0790), current thread is QThread(0xc1c050)
    Mar 14 21:25:00 linux-3hsx sddm-greeter[2970]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.

    Next days I will try to compare the messages of the past with now...

  6. #6

    Default Re: USB Mouse & Keyboard Problems

    Quote Originally Posted by Knurpht View Post
    Install the xf86-input-libinput package and reboot. If you already messed around with the touchpad settings in Systemsettings - Input Devices, restore those to defaults.
    Thank you Knupht. Iooking at yast I see that this package is already installed (never touched the touchpad settings). Actual version is 0.17git-20160229T143443-5e7ee73-2.1-x86_64 from scalpel4k
    But I see other versions too, for example 0.17.0-33.2-x86_64 from GNOME. I see a radio button, I will try this ...

  7. #7

    Default Re: USB Mouse & Keyboard Problems

    Quote Originally Posted by riccardoescher View Post
    But I see other versions too, for example 0.17.0-33.2-x86_64 from GNOME. I see a radio button, I will try this ...
    Wow! I have selected the other version in yast, an installation started. I did reboot. The first symptom is still there (mouse & keyboard dead at the greeter), but the second symptom is gone away (loosing events), I can type this as fast as I am used to. Happy again (the greeter problem is not so heavy).
    Looking in yast at the entry again (Tab Change protocol) I notice a newer change protocol, the last entry being Fr 26 Feb 2016 from zaitor. The version I had before was much older.
    In yast tab "Versions" the entry I had before (017git...) is at fourth position, seeming to me being older.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •