HEllo, when I run applications from console I get this X Error: BadDevice, invalid or uninitialized input device 166, how to solve it? What causes it?
-
-
Re: X error
Seconded... I'm still searching for the solution. Now that that I've rid my xorg.conf of the wacom tablet PC errors (device 168), I thought I might be able to rid myself of this one. But alas, everything else seems rather important: mouse, keyboard, screen, monitor...
Any help out there? -
Re: X error
Those errors are really just for the wacom references in xorg.conf. They also don't do anything harmful at all. So my suggestion for now is to ignore it. At least until a real fix would be made.
Besides, you can also launch apps by pressing Alt+F2, so you won't have to see those error messages
Comment
-
Re: X error
Thanks for responding.
From what I've gathered, however, wacom errors show up as device 168, and I've commented these sections from my xorg.conf file. If they're 166 as well, and they aren't in my config file, how do they show up?
Anyhow, you're right they're mostly benign- however, they have lead to a bit of annoyance for me:
When runnung amarok (and others), after the "X Error: Bad device...", this message and every subsequent command is echoed into .xsession-errors file. When scanning a collection or something this ends up leading to a lot of writing...
I found this out the first time after the file had grown to 900 Mb (and I had the settings on a small partition).
Now that I know, can deal with it. Still annoying: yes, very.
Hopefully will disable these settings by deafult in next release...Comment
Comment