First of all, I think that this question is not an easy one. I don't expect a quick solution, but rather some ways of investigation.
Background: I have 3 FreeBSD installations with almost the same configuration: 14.0-RELEASE-p3 and Lxde/slim as DE.
I upgraded two of them from 13.2-RELEASE to 14-RELEASE without any trouble. The last one, however, has a problem and not a little one.
As the title says, polkitd doesn't work. It exits with a message like this:
Digging with
The files /usr/local/share/dbus-1/system.conf and /usr/local/share/dbus-1/session.conf are the same than the two others systems that work well.
And, of course, dbus is actually running.
Any suggestion? I'm really lost there.
Background: I have 3 FreeBSD installations with almost the same configuration: 14.0-RELEASE-p3 and Lxde/slim as DE.
I upgraded two of them from 13.2-RELEASE to 14-RELEASE without any trouble. The last one, however, has a problem and not a little one.
As the title says, polkitd doesn't work. It exits with a message like this:
Code:
Successfully changed to user polkitd
11:30:20.696: Loading rules from directory /usr/local/etc/polkit-1/rules.d
11:30:20.696: Loading rules from directory /usr/local/share/polkit-1/rules.d
11:30:20.696: Finished loading, compiling and executing 1 rules
Entering main event loop
Connected to the system bus
11:30:20.697: Lost the name org.freedesktop.PolicyKit1 - exiting
Shutting down
Exiting with code 1
Digging with
dbus-monitor --system
, I saw that:
Code:
method call time=1706439359.110346 sender=:1.87 -> destination=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RequestName
string "org.freedesktop.PolicyKit1"
uint32 1
error time=1706439359.110360 sender=org.freedesktop.DBus -> destination=:1.87 error_name=org.freedesktop.DBus.Error.AccessDenied reply_serial=3
string "Connection ":1.87" is not allowed to own the service "org.freedesktop.PolicyKit1" due to security policies in the configuration file"
The files /usr/local/share/dbus-1/system.conf and /usr/local/share/dbus-1/session.conf are the same than the two others systems that work well.
And, of course, dbus is actually running.
Any suggestion? I'm really lost there.