system-config-services stopped working - meaning of error message?

[geckobelly]

After an update about 12 hours ago, which I just noticed because prior to the updates it was working, services under the administration tab, stopped working. When I attempt to launch it, it on the bottom task bar it shows "starting services" for about 7 seconds, then disappears. I'm running the beta version of Fedora 13, x64 version. Here's the output from the command line when I run system-config-services:

Traceback (most recent call last):
File "/usr/sbin/system-config-services", line 1040, in <module>
GUI(use_dbus=use_dbus).run()
File "/usr/sbin/system-config-services", line 958, in __init__
if slip.dbus.polkit.AreAuthorizationsObtainable(self. polkit_actions):
File "/usr/lib/python2.6/site-packages/slip/dbus/polkit.py", line 420, in AreAuthorizationsObtainable
return __polkit.AreAuthorizationsObtainable(authorization s)
File "/usr/lib/python2.6/site-packages/slip/dbus/polkit.py", line 317, in AreAuthorizationsObtainable
if not self._polkitd_interface():
File "/usr/lib/python2.6/site-packages/slip/dbus/polkit.py", line 257, in _polkitd_interface
PolKit.__determine_polkit_version()
File "/usr/lib/python2.6/site-packages/slip/dbus/polkit.py", line 240, in __determine_polkit_version
raise VersionError("Cannot determine valid PolicyKit version.")
slip.dbus.polkit.VersionError: Cannot determine valid PolicyKit version.

Help anyone?

[Hlingler]

I'm running the beta version of Fedora 13, x64 version.

Moved to "F13" section.

V

[BugRocks1]

In Fedora 12 I have 3 services that say they are dead but are working when I look at top.

opnvpn
lvm2-monitor
privoxy

[CiaW]

Was there an SELinux policy violation message? I suspect it's an SELinux issue.

I've received an alert every time I bring up >system > admin > services but since I have SELinux in permissive mode, it comes up for me. And on this particular alert, it doesn't give me an option to report it as a bug. I just saved the output to the clipboard and pasted it to a gedit doc. I'll file a bugzilla if there isn't one already, which I hadn't done previously because I figured someone else probably would do it first and/or I just forgot because I don't bring that up often. You'll probably want to check your selinux alerts to see if it gives you this:

 SELinux is preventing /sbin/plymouthd "open" access on tty63.

[geckobelly]

hot damn, ciaw you were right, wasn't even thinking in the direction of selinux but i dialed back the enforcement settings and several nagging issues disappeared immediately, you da man!!!

[AdamW]

Can you file a bug for this? Against selinux-policy. Include the traceback from system-config-services and also look in /var/log/messages at the time of the failure, there should be some kind of log from selinux (could be listed as 'audit') showing it denied access to something at that time, include that notice too. Thanks!

[CiaW]

Originally Posted by AdamW

Can you file a bug for this? Against selinux-policy. Include the traceback from system-config-services and also look in /var/log/messages at the time of the failure, there should be some kind of log from selinux (could be listed as 'audit') showing it denied access to something at that time, include that notice too. Thanks!

Bug report filed, if more output is needed I'll need specifics of how or where to find it.