KSysGuard problem (doesn't run)

[Derek]

I can't run KSysGuard anymore, but get it's 'dancing' icon for a few
seconds instead, and that's it. I ran Konsole and gave the "$
killall ksysguard" command, but the problem remains.
Can't run KSysGuard from the console either.

What would possibly be the cause and what could be the remedy?

[penguin.ch]

Re: KSysGuard problem (doesn't run)

sudo apt-get --reinstall install ksysguardd ksysguard

[Derek]

Re: KSysGuard problem (doesn't run)

Thanks. I did what you recommended, but the problem is still there. Can't run KSysGuard.

[Derek]

Re: KSysGuard problem (doesn't run)

I ran sudo ksysguard

and got:

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
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :0.0
DCOP aborting call from 'anonymous-6103' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.

But after all that stuff KSysGuard fires up and runs. It does not run from the KDE menu though (not even when I 'am' root.

[Derek]

Re: KSysGuard problem (doesn't run)

Correction. KSysGuard does run from the menu when I 'am' root.

[askrieger]

Re: KSysGuard problem (doesn't run)

First of all, those "X Error: BadDevice ..." lines are irrelevant. They reflect the fact that you haven't commented out the "wacom" stuff in your xorg.conf file. Search on "wacom". This topic has been beaten to death long ago.

Second, whenever you find that a program runs when you're root (using sudo, or kdesu) and doesn't run when you're a normal user, it almost always means that normal users do not have permission to execute the program. It shouldn't make any difference whether you start it from the command line in a konsole or from the GUI. The easiest way to fix that problem is from the console. Run the following command:

chmod 755 /usr/bin/ksysguard

(remember spelling counts). That SHOULD solve your problem, if I have guessed correctly, but ksysguard already has 755 perms on my box, so I may be wrong.

[Derek]

Re: KSysGuard problem (doesn't run)

Thanks. I had looked into the Wacom lines already. I have no Wacom hardware installed, but when I comment out the Wacom lines in xorg.conf KDE does not run, very weird.

Somehow the permisson for KSysGuard was changed suddenly to Root, I don't understand why. Not necessarily a bad thing though.

[askrieger]

Re: KSysGuard problem (doesn't run)

When you commented out the "wacom" stanzas, did you remember to also comment out the "stylus", "cursor", and "eraser" lines in the "ServerLayout" stanza?

"ls -l /usr/bin/ksysguard/" should give:

-rwxr-xr-x 1 root root 573224 2007-04-11 /usr/bin/ksysguard

where root root refers to the owner and group and the "rwxr-xr-x" are the three octal digits 755, referring to the permissions of the owner, her group, and all other users. That way only root can change the file, but everyone can execute it.

[Derek]

Re: KSysGuard problem (doesn't run)

No, I had not done that. Thanks. Things are even better now.