Version: KDE 4.3.80 release 197 (using Devel) OS: Linux Installed from: Compiled sources When I select other user's(e.g. root's) process in ksysguard and choose "kill process" in the right-click menu, an error appears: "You do not have the permission to kill the process and there was a problem trying to run as root. Error 4". When choosing any other signal(STOP, TERM, ...) the same error appears. So i have to go to the console, run "su" and "killall <processname>", and this is quite inconveniently. But in KDE <= 4.3.4 when I tried to kill other's process, there appeared a window asking for a root password, so I was able to kill other's process right in ksysguard. KDE 4.3.80 "release 197"
I think that this is just because you are compiling from sources. I switched over to using KAuth (policykit) instead of kdesu, but this needs to be installed into certain directories. You have probably set a prefix directory, so these files don't get installed. When you upgrade your system next, your distro should install the needed files. There's not much I can do to fix this in the meantime sorry.
(In reply to comment #1) > I think that this is just because you are compiling from sources. Maybe I did a mistake in bug wizard - I'm using binary rpm packets from opensuse repository( http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.2 ) > I switched over to using KAuth (policykit) instead of kdesu, but this needs to > be installed into certain directories. You have probably set a prefix > directory, so these files don't get installed. can I fix that issue by adding some permissions to my user in /etc/PolicyKit/PolicyKit.conf ?
Ah sorry. I was a bit too hasty :) I'll ping Dario to see if he has any ideas.
I think your distro has installed it to /opt or something? If so, I think you need to copy from /opt/usr/Polkit/* to /usr/Polkit or something
(In reply to comment #4) > I think your distro has installed it to /opt or something? > whereis PolicyKit PolicyKit: /etc/PolicyKit /usr/lib/PolicyKit /usr/share/PolicyKit /usr/share/man/man8/PolicyKit.8.gz > ls /usr/share/PolicyKit/ config.dtd policy > ls /usr/share/PolicyKit/policy/ org.freedesktop.hal.dockstation.policy org.freedesktop.policykit.policy org.freedesktop.hal.killswitch.policy org.kde.fontinst.policy org.freedesktop.hal.leds.policy org.kde.kcontrol.kcmclock.policy org.freedesktop.hal.policy org.kde.kcontrol.kcmremotewidgets.policy org.freedesktop.hal.power-management.policy org.kde.ksysguard.processlisthelper.policy org.freedesktop.hal.storage.policy org.opensuse.yast.modules.yapi.language.policy org.freedesktop.hal.wol.policy org.opensuse.yast.modules.yapi.time.policy org.freedesktop.network-manager-settings.system.policy in /opt/ there are only kde3 files. > If so, I think you need to copy from /opt/usr/Polkit/* to /usr/Polkit or > something erm, I dont think that's good idea...
Your system configuration is correct - the error you're getting means that you're not authorized to perform the action. To check if that is true, you might want to check in the policykit control module if you see the action correctly. If you do, the causes could be that consolekit is not running on your system (in that case the authorization would be forbidden by default), or you're simply not authorized to perform the action. If not the former (which you can verify by changing the policies in the policykit control module), posting your PolicyKit.conf might help finding out the reason.
(In reply to comment #6) > Your system configuration is correct - the error you're getting means that > you're not authorized to perform the action. To check if that is true, you > might want to check in the policykit control module if you see the action > correctly. Yes, I've changed policies in policykit control module -> org.kde -> ksysguard -> KSysGuard -> "Kill or stop etc a process"(org.kde.ksysguard.processlisthelper.sendsignal) to "authenticate as root", and now everything works flawless. I think these policies should be set up by default. Thanks for your help!
Those policies are off for security reasons - you probably might want to file a bug against opensuse to provide correct consolekit support (or if they don't want to, they can patch the policy files out before installing them)
Dario, so.. what exactly does opensuse need to do? What about their consolekit support is wrong?