same issue in feisty herd 4. must we punish the masses whilst we work out the wacom stuff? not only is it cluttering up local log files, but it's also cluttering up other bug reports, forums and google searches with lines such as
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
since Xorg -configure finds no wacom devices this appears to be a fault in the installation scripts that generate the initial xorg.conf.
is this just a k/ubuntu deal or does it need to go upstream?
attached is more info and a workaround for those without wacom devices
same issue in feisty herd 4. must we punish the masses whilst we work out the wacom stuff? not only is it cluttering up local log files, but it's also cluttering up other bug reports, forums and google searches with lines such as
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
since Xorg -configure finds no wacom devices this appears to be a fault in the installation scripts that generate the initial xorg.conf.
is this just a k/ubuntu deal or does it need to go upstream?
attached is more info and a workaround for those without wacom devices