How do I get this to run after installing it?

[ardchoille]

I am using Kubuntu Feisty. I installed gkrellm with "sudo apt-get install gkrellm", but when I launch it from a term, all I get is this:

[~ @ 15:26:36] gkrellm
X Error: BadDevice, invalid or uninitialized input device 169
 Major opcode: 147
 Minor opcode: 3
 Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
 Major opcode: 147
 Minor opcode: 3
 Resource id: 0x0
Failed to open device

That stuff is output for almost every app I run from konsole. But, gkrellm never shows up on the desktop and there is no other error output either. How do I get gkrellm running?

[Bapelsin]

Re: How do I get this to run after installing it?

Try checking in KSysGuard if the process is running. Maybe the program icon is in the system tray?

[ardchoille]

Re: How do I get this to run after installing it?

Try checking in KSysGuard if the process is running. Maybe the program icon is in the system tray?

[~ @ 15:35:00] ps aux | grep gkrellm
ianmac  9570 0.0 0.0  2884  752 pts/6  R+  15:46  0:00 grep gkrellm

gkrellm isn't running and there's no icon in the tray. gkrellm usually pops up on the desktop upon launch and I have never known gkrellm to have a tray icon. It simply isn't showing on the desktop.

[dibl]

Re: How do I get this to run after installing it?

I think that output is the famous "worthless wacom xorg crap" error. It is harmless, albeit annoying, and totally irrelevant to your gkrellm issue.

Somewhere there is instructional material on how to comment the wacom stuff out of xorg.conf. Basically, you need to put a "#" in front of every part of /etc/X11/xorg.conf that relates to the wacom driver, like this (AFTER you back up your present xorg.conf!):

# Identifier "stylus"
# Driver "wacom"
# Option "Device" "/dev/wacom" # Change to
# Option "Type" "stylus"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
# EndSection
# Section "InputDevice"
# /dev/input/event
# for USB
# Identifier "eraser"
# Driver "wacom"
# Option "Device" "/dev/wacom" # Change to
# Option "Type" "eraser"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
# EndSection
# Section "InputDevice"
# /dev/input/event
# for USB
# Identifier "cursor"
# Driver "wacom"
# Option "Device" "/dev/wacom" # Change to
# Option "Type" "cursor"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
# EndSection

Section "ServerLayout"

# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"

The gkrellm issue is something different -- hopefully help will come for that too ...

[Guest]

Re: How do I get this to run after installing it?

You don't need to edit out all that stuff, just these three lines:

# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"

That's what I've been doing since Dapper to get rid of the messages anyway.

[ardchoille]

Re: How do I get this to run after installing it?

Thank you, I commented out all the wacom stuff since I don't have wacom devices and will probably never have them.

Anyone know how to fix the gkrellm problem?

[ardchoille]

Re: How do I get this to run after installing it?

Now, this is very interesting. I can launch gkrellm and it runs, but doesn't popup on the desktop like it should. Then, exactly three minutes later, it pops up on the dekstop.

Anyone know how to fix this?

[ardchoille]

Re: How do I get this to run after installing it?

Ok, new information about the "gkrellm running invisible for 3 to 4 minutes" problem - which I was experiencing. I decided to tail /var/log/messages, run gkrellm and then tail /var/log/messages again and I got some info from /var/log/messages that hinted toward the firewall being misconfigured. So, I uninstalled the firewall and uninstalled KMyFirewall. Then I rebooted, ran gkrellm and it immediately popped up on the desktop.

Seems the "gkrellm running invisible for 3 to 4 minutes" problem on my machine was caused by a misconfigured firewall. Others who are experiencing the gkrellm problem may want to look into their firewall config.