Mouse and Keyboard not workong in KDM

After booting my usb-keyboard and mouse are not working. During boot they work! to make them work in KDM I have to remove and plug them in again. It also happens when I log out from KDE and have to use KDM to login again. This problem occurs since I have updated my opensuse Tumbleweed (sudo zypper dup) some days ago.

This seems to be the part where I remove and plug mouse and keyboard in again:

/var/log/messages/


Oct  1 11:07:37 Spiollinux-SUSE kernel:    47.371023] usb 2-1: USB disconnect, device number 2
Oct  1 11:07:39 Spiollinux-SUSE kernel:    48.848077] usb 2-1: new full speed USB device number 4 using ohci_hcd
Oct  1 11:07:39 Spiollinux-SUSE kernel:    48.996064] usb 2-1: New USB device found, idVendor=e0ff, idProduct=0002
Oct  1 11:07:39 Spiollinux-SUSE kernel:    48.996073] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct  1 11:07:39 Spiollinux-SUSE kernel:    48.996079] usb 2-1: Product: SPEEDLINK Gaming Mouse
Oct  1 11:07:39 Spiollinux-SUSE kernel:    48.996084] usb 2-1: Manufacturer: A.....
Oct  1 11:07:39 Spiollinux-SUSE mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:13.0/usb2/2-1"
Oct  1 11:07:39 Spiollinux-SUSE kernel:    49.002938] input: A..... SPEEDLINK Gaming Mouse as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.0/input/input9
Oct  1 11:07:39 Spiollinux-SUSE kernel:    49.003563] generic-usb 0003:E0FF:0002.0005: input,hidraw0: USB HID v1.00 Mouse [A..... SPEEDLINK Gaming Mouse] on usb-0000:00:13.0-1/input0
Oct  1 11:07:39 Spiollinux-SUSE kernel:    49.010360] input: A..... SPEEDLINK Gaming Mouse as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.1/input/input10
Oct  1 11:07:39 Spiollinux-SUSE kernel:    49.012116] generic-usb 0003:E0FF:0002.0006: input,hiddev0,hidraw1: USB HID v1.00 Keyboard [A..... SPEEDLINK Gaming Mouse] on usb-0000:00:13.0-1/input1
Oct  1 11:07:39 Spiollinux-SUSE mtp-probe: bus: 2, device: 4 was not an MTP device
Oct  1 11:07:40 Spiollinux-SUSE kernel:    50.668779] usb 2-2: USB disconnect, device number 3
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.352030] usb 2-2: new low speed USB device number 5 using ohci_hcd
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.519060] usb 2-2: New USB device found, idVendor=04d9, idProduct=1603
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.519065] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.519068] usb 2-2: Product: USB Keyboard
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.519070] usb 2-2: Manufacturer:  
Oct  1 11:07:42 Spiollinux-SUSE mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:13.0/usb2/2-2"
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.533434] input:   USB Keyboard as /devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.0/input/input11
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.533552] generic-usb 0003:04D9:1603.0007: input,hidraw2: USB HID v1.10 Keyboard   USB Keyboard] on usb-0000:00:13.0-2/input0
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.556180] input:   USB Keyboard as /devices/pci0000:00/0000:00:13.0/usb2/2-2/2-2:1.1/input/input12
Oct  1 11:07:42 Spiollinux-SUSE kernel:    52.556310] generic-usb 0003:04D9:1603.0008: input,hidraw3: USB HID v1.10 Device   USB Keyboard] on usb-0000:00:13.0-2/input1
Oct  1 11:07:43 Spiollinux-SUSE mtp-probe: bus: 2, device: 5 was not an MTP device

I wasn’t able to find the kernel recognizing them the first time (THEY WORKED DURING BOOT!), maybe it’s the wrong logfile?

Sure you can imagine how annoying this is… Would be great if someone is able to help me :slight_smile:

As you did allrady conclude it has somethinmg to do with Tumbleweed, why didn’t you ask in the Tumbleweed subforum? Much more chance you find fellow Tumbleweed users who can help you!

Sorry… I didn’t know there’s a subforum for Tumbleweed
sometimes I’m like blind :shame:

I will mov it there for you. Will take about 20 mins.

To all, this thread will be closed now and hen moved. NTTP users please take care.

Moved to Tumbleweed and open for posting again.

Appears to be solved with an update lol!

CLOSED