abrt 1.0.4 detected a crash. architecture: x86_64 cmdline: /usr/bin/python /usr/share/system-config-firewall/system-config-firewall-mechanism.py component: system-config-firewall executable: /usr/share/system-config-firewall/system-config-firewall-mechanism.py kernel: 2.6.31.12-174.2.3.fc12.x86_64 package: system-config-firewall-1.2.21-1.fc12 release: Fedora release 12 (Constantine) backtrace ----- Summary: TB08997608 connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.75" is not allowed to own the service "org.fedoraproject.Config.Firewall" due to security policies in the configuration file Traceback (most recent call last): File "/usr/share/system-config-firewall/system-config-firewall-mechanism.py", line 27, in <module> fw_dbus.run_service() File "/usr/share/system-config-firewall/fw_dbus.py", line 123, in run_service name = dbus.service.BusName(DBUS_DOMAIN, bus) File "/usr/lib/python2.6/site-packages/dbus/service.py", line 129, in __new__ retval = bus.request_name(name, name_flags) File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 306, in request_name 'su', (name, flags)) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.75" is not allowed to own the service "org.fedoraproject.Config.Firewall" due to security policies in the configuration file Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SystemBus (system) at 0x247c8f0> args: ('org.fedoraproject.Config.Firewall', 0) utf8_strings: False bus_name: 'org.freedesktop.DBus' get_args_opts: {'byte_arrays': False, 'utf8_strings': False} object_path: '/org/freedesktop/DBus' timeout: -1.0 signature: 'su' dbus_interface: 'org.freedesktop.DBus' message: <dbus.lowlevel.MethodCallMessage object at 0x7fa2bdc5d450> method: 'RequestName'
Created attachment 389864 [details] File: backtrace
Was there a SELinux error message also?
The dbus mechanism has been modified to report an error to syslog in the case of dbus problems. The cause of the dbus problem is unknown. It could be a mislabeled file. Closing due to user inactivity.
I know this is closed. But, I stumbled across this bug report searching for a solution. So to add to the story... I noticed that firewald was not running on one of my f20 cloud servers. All attempts to restart resulted in: firewalld: 2015-01-08 16:12:40 ERROR: Exception DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.3699" is not allowed to own the service "org.fedoraproject.FirewallD1" due to security policies in the configuration file So I inspected the "security policies in the configuration file" @ /etc/dbus-1/system.d/FirewallD.conf Looked good. With a wild guess, I restarted the dbus.service dbus-daemon: dbus[362]: [system] Reloaded configuration dbus[362]: [system] Reloaded configuration And then restarted firewalld. systemd: Starting firewalld - dynamic firewall daemon... systemd: Started firewalld - dynamic firewall daemon. All is good. Hope this helps someone else. JB