Bug 773698 - ksysguard policy kit problem
Summary: ksysguard policy kit problem
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-workspace
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 16:13 UTC by Joshua
Modified: 2012-06-20 13:32 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:26:52 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 218648 0 None None None 2012-06-20 12:43:30 UTC

Description Joshua 2012-01-12 16:13:15 UTC 
Description of problem:
when I updated to fedora 16 ksysguard started giving me an error saying

You do not have the permission to kill the process and there was a problem
trying to run as root.  Error 7 Dbus Backend error: The name org.kde.ksysguard.processlisthelper was not provided by any service files Message error: the name org.kde.ksysguard.processlisthelper was not provided
by any .service files


Version-Release number of selected component (if applicable):
my current version is 4.7.4-6

How reproducible:
always

Steps to Reproduce:
1.open the ksysguard process list
2.try to end a process that is not yours
3.watch the error pop up
Comment 1 Martin Bříza 2012-06-20 12:43:30 UTC 
Hello, 

I added external tracker for this bug, but it is resolved as fixed there. It seems there was/is a problem with PolicyKit, however, I can't reproduce this kind of behavior on my box with Fedora 16 and KDE SC 4.8.3.

Could you please provide us with information if the issue is still present or was resolved by an update? Thank you.
Comment 2 Joshua 2012-06-20 13:01:28 UTC 
It happened when I first installed fedora 16 but upstream must have fixed it. It is no longer giving me any problems.
Comment 3 Martin Bříza 2012-06-20 13:26:52 UTC 
Thanks for the response and the good news. I'm closing the bug, but feel free to reopen it in case you experience the issue again.
Comment 4 Rex Dieter 2012-06-20 13:32:25 UTC 
Thanks.
Note You need to log in before you can comment on or make changes to this bug.