Xorg Logs show misdetection of my DVB USB tuner device as a Keyboard - How to Resolve ?
Fedora 20 / Gnome Destop / 64 bit / Kworld 395U DVB-T Tuner
While searching the Xorg logs for a problem to do with Fedora front screen not responding to keyboard after PC being unattended for an hour - mouse moved OK but keyboard (ESC) will not respond to take me to password entrry screen …… and whiule browsing logs to debug it I found a more concerning 2nd problem - so one problem at a time …….
Background : I have been having erratic behaviour with my USB - DVB-T device - it would sometimes become unrecognised by the system after a period of say couple hours ie failed to initialize errors in dmesg | grep DVB and so on
While browsing the Xorg Logs i found this below - Should I be concerned with the fact that the DVB tuner it reports as a keyboard in the logs - I reckon i should be ?? see below
$ cat Xorg.0.log | grep 395
[ 33.464] (II) config/udev: Adding input device KWorld USB DVB-T TV Stick II (VS-DVB-T 395U) (/dev/input/event5)
[ 33.464] (**) KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Applying InputClass "evdev keyboard catchall"
[ 33.464] (**) KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Applying InputClass "system-keyboard"
[ 33.464] (II) Using input driver 'evdev' for 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)'
[ 33.464] (**) KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): always reports core events
[ 33.464] (**) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Device: "/dev/input/event5"
[ 33.464] (--) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Vendor 0x1b80 Product 0xe39b
[ 33.464] (--) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Found keys
[ 33.464] (II) evdev: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U): Configuring as keyboard
[ 33.464] (II) XINPUT: Adding extended input device "KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)" **(type: KEYBOARD, id 10)**
by the way tuner still works mostly - but it can uninstall detach itself from the system occasionally (not physically ) but from an OS / driver point of view
What can i do to fix this mis detection of my device ? thank you all Don