Re: Keyboard stopped working in KDE

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/12/14 06:18, Patrick O'Callaghan wrote:
> On Wed, 2014-03-12 at 05:07 +0800, Ed Greshko wrote:
>> On 03/12/14 01:04, Patrick O'Callaghan wrote:
>>> F20 fully updated to KDE 4.12.3-1, x86_64, NVidia GT630 graphics with
>>> the proprietary driver.
>>>
>>> This morning everything was working. This afternoon, after updating
>>> KDE, I no longer have a keyboard.
>>>
>>> The KB does work in a non-desktop console, and also under Gnome (where
>>> I'm typing this), but in no part of KDE.
>>>
>>> KB hardware is a Microsoft Wireless Keyboard 800 connected via a USB
>>> dongle. The mouse connects through the same dongle and is working
>>> fine. That particular model is not listed as an option in the KDE
>>> Settings widget, so I've been selecting "Microsoft Wireless Multimedia
>>> Keyboard 1.0A".
>>>
>>> This could be something silly related to evdev, but I've no idea what,
>>> so ideas are welcome.
>> Similar configuration....  GTX 660, nvidia drivers, logitech USB Mouse/Keyboard.  Updated last night.  But I have no problems.
>>
>> Anything in the Xorg.0.log pop out at you? 
>>
>> [egreshko@meimei log]$ grep -i keyb Xorg.0.log
>> [ 50660.975] Initializing built-in extension XKEYBOARD
>> [ 50661.883] (**) Power Button: Applying InputClass "evdev keyboard catchall"
>> [ 50661.883] (**) Power Button: Applying InputClass "anaconda-keyboard"
>> [ 50661.883] (II) evdev: Power Button: Configuring as keyboard
>> [ 50661.883] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
>> [ 50661.910] (**) Power Button: Applying InputClass "evdev keyboard catchall"
>> [ 50661.910] (**) Power Button: Applying InputClass "anaconda-keyboard"
>> [ 50661.910] (II) evdev: Power Button: Configuring as keyboard
>> [ 50661.910] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
>> [ 50661.921] (**) Logitech Unifying Device. Wireless PID:2011: Applying InputClass "evdev keyboard catchall"
>> [ 50661.921] (**) Logitech Unifying Device. Wireless PID:2011: Applying InputClass "anaconda-keyboard"
>> [ 50661.921] (II) evdev: Logitech Unifying Device. Wireless PID:2011: Configuring as keyboard
>>
>> for me...
> Here's mine:
>
> $ grep -i keyb /var/log/Xorg.0.log
> [  1102.578] Initializing built-in extension XKEYBOARD
> [  1102.933] (**) Power Button: Applying InputClass "evdev keyboard catchall"
> [  1102.933] (**) Power Button: Applying InputClass "system-keyboard"
> [  1102.934] (II) evdev: Power Button: Configuring as keyboard
> [  1102.934] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
> [  1102.945] (**) Power Button: Applying InputClass "evdev keyboard catchall"
> [  1102.945] (**) Power Button: Applying InputClass "system-keyboard"
> [  1102.945] (II) evdev: Power Button: Configuring as keyboard
> [  1102.945] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
> [  1102.946] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
> [  1102.946] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
> [  1102.947] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as keyboard
> [  1102.947] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 8)
> [  1102.947] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
> [  1102.947] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
> [  1102.947] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as keyboard
> [  1102.947] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 9)
> [  1102.948] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
> [  1102.948] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "evdev keyboard catchall"
> [  1102.948] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
> [  1102.948] (II) evdev: Microsoft Microsoft® 2.4GHz Transceiver v8.0: Configuring as keyboard
> [  1102.948] (II) XINPUT: Adding extended input device "Microsoft Microsoft® 2.4GHz Transceiver v8.0" (type: KEYBOARD, id 10)
> [  1102.948] (**) Microsoft Microsoft® 2.4GHz Transceiver v8.0: Applying InputClass "system-keyboard"
>
> Apart from MS vs Logitech, mine is longer for some reason. Several lines are repeated with different id numbers. Also, yours talks about anaconda-keyboard and mine about system-keyboard. Are you using KDE?
>
> poc
>

Odd, that you're getting different ID's....   Yes, I'm using KDE.  I've got "Generic | Generic 101-key PC" in the "System Settings" which I never changed from what it defaulted to.


-- 
Getting tired of non-Fedora discussions and self-serving posts
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org





[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux