This error is not harmful. You can ignore it without any trouble to use eman.
But to compile EMAN on Ubuntu (>7.04), you need set ENABLE_UBUNTU in ccmake, type 't' for advanced setting.
If you think this is annoying and want to get rid of it, please do as following:
Seems a lot of users are getting the below errors when running applications from the console:
Code:
X Error: BadDevice, invalid or uninitialized input device 168
Major opcode: 148
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
Major opcode: 148
Minor opcode: 3
Resource id: 0x0
Failed to open device
To fix this, look for the lines posted below, or similar to, and comment them out of your /etc/X11/xorg.conf file:
Code:
# Section "InputDevice"
# Driver "wacom"
# Identifier "stylus"
# Option "Device" "/dev/wacom" # Change to
# # /dev/input/event
# # for USB
# Option "Type" "stylus"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
#EndSection
#Section "InputDevice"
# Driver "wacom"
# Identifier "eraser"
# Option "Device" "/dev/wacom" # Change to
# # /dev/input/event
# # for USB
# Option "Type" "eraser"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
#EndSection
#Section "InputDevice"
# Driver "wacom"
# Identifier "cursor"
# Option "Device" "/dev/wacom" # Change to
# # /dev/input/event
# # for USB
# Option "Type" "cursor"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
#EndSection
Then also a bit further down in the file you need to look for the below lines, or ones similar to these:
Code:
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
EndSection
**WARNING** If you fail to comment the lines below that are commented out, then X will *NOT* start when you go to restart the X server.
Once you comment those things out then a restart of X is needed. Once X is back up and running again you shouldn't see those errors anymore.the solution is come from Ubuntu forum, I copy it here in case that link is not approachable.