Bug 475111

not only networkmanager. it broke on one of my machines system-config-services:

ERROR:dbus.proxies:Introspect error on :1.63:/org/fedoraproject/Config/Services/ServiceHerders/SysVServiceHerder: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.DBus.Introspectable" member "Introspect" error name "(unset)" destination ":1.63")
Traceback (most recent call last):
  File "/usr/bin/system-config-services", line 945, in <module>
    GUI (use_dbus = use_dbus).run ()
  File "/usr/bin/system-config-services", line 900, in __init__
    self.serviceherders.append (cls (bus = self._bus))
  File "/usr/lib/python2.5/site-packages/scservices/dbus/proxy/serviceherders.py", line 53, in __init__
    for service_name in self.list_services ():
  File "/usr/lib/python2.5/site-packages/slip/dbus/polkit.py", line 48, in enable_proxy_wrapper
    return func (*p, **k)
  File "/usr/lib/python2.5/site-packages/scservices/dbus/proxy/serviceherders.py", line 66, in list_services
    return self.dbus_object.list_services (dbus_interface = "org.fedoraproject.Config.Services.ServiceHerder")
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.fedoraproject.Config.Services.ServiceHerder" member "list_services" error name "(unset)" destination ":1.63")



and on another machine with a fresh install (using online updates during install) it even broke the gnome-settings daemon, thus i wasn't able to do any useful stuff in gnome :-)

(In reply to comment #0)
> Couldn't retrieve connection settings: A security policy in place prevents
> this sender from sending this message to this recipient, see message bus
> configuration file (rejected message had interface
> "org.freedesktop.NetworkManagerSettings.Connection" member "GetSettings"
> error name "(unset)" destination
> "org.freedesktop.NetworkManagerUserSettings").

What does your /etc/dbus-1/system.d/nm-applet.conf say?  Such message should be permitted by a "send_destination" rule.  Trying with fresh F10 install, there are no obvious issues with NM (tried with dhcp and static wired network).  If you run d-feet, open system bus, which process owns org.freedesktop.NetworkManagerUserSettings service?

(In reply to comment #1)
> :1.63:/org/fedoraproject/Config/Services/ServiceHerders/SysVServiceHerder:
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A
> security policy in place prevents this sender from sending this message to
> this recipient, see message bus configuration file (rejected message had
> interface "org.freedesktop.DBus.Introspectable" member "Introspect" error
> name "(unset)" destination ":1.63")

Maybe this should be added to system.conf:
  <allow send_interface="org.freedesktop.DBus.Introspectable"/>
below:
  <allow receive_sender="org.freedesktop.DBus"/>
to permit introspection by default.

> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A
> security policy in place prevents this sender from sending this message to
> this recipient, see message bus configuration file (rejected message had
> interface "org.fedoraproject.Config.Services.ServiceHerder" member
> "list_services" error name "(unset)" destination ":1.63")

This should be a s-c-services bug.  It seems to use a couple of interfaces, but only allows use of .Config.Services.  This should get separate bug against s-c-services.

i've added <allow send_interface="org.freedesktop.DBus.Introspectable"/> to /etc/dbus-1/system.conf. now i get this:

[sothis@rigel ~]$ system-config-services 
Traceback (most recent call last):
  File "/usr/bin/system-config-services", line 945, in <module>
    GUI (use_dbus = use_dbus).run ()
  File "/usr/bin/system-config-services", line 900, in __init__
    self.serviceherders.append (cls (bus = self._bus))
  File "/usr/lib/python2.5/site-packages/scservices/dbus/proxy/serviceherders.py", line 53, in __init__
    for service_name in self.list_services ():
  File "/usr/lib/python2.5/site-packages/slip/dbus/polkit.py", line 48, in enable_proxy_wrapper
    return func (*p, **k)
  File "/usr/lib/python2.5/site-packages/scservices/dbus/proxy/serviceherders.py", line 66, in list_services
    return self.dbus_object.list_services (dbus_interface = "org.fedoraproject.Config.Services.ServiceHerder")
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.fedoraproject.Config.Services.ServiceHerder" member "list_services" error name "(unset)" destination ":1.39")


in other words, the introspect error went away, but the rest remains the same :-(

(In reply to comment #3)
> in other words, the introspect error went away, but the rest remains the same
> :-(

Sure, as noted in the comment #2, this is not Introspect issue and deserves a separate bug against s-c-services (I've filed one - bug #475203, feel free to CC yourself).

Tomas, I don't have a /etc/dbus-1/system.d/nm-applet.conf here. Only:
nm-avahi-autoipd.conf    nm-dispatcher.conf       nm-system-settings.conf
nm-dhcp-client.conf      nm-openvpn-service.conf  nm-vpnc-service.conf
This is a system installed with F9 and updates to F10.

Do you have NetworkManager-gnome installed?  Can you run d-feet and see if anything owns org.freedesktop.NetworkManagerUserSettings on the system bus?

I'm back on dbus-1.24.xx for the moment. But if I understand right that makes no difference, since the separate policy-files are what matters, right?

No NetworkManager-gnome here, just knetworkmanager (and some other packages for that).

Haven't used d-feet before. org.freedesktop.NetworkManagerUserSettings has process "knetworkmanager". Under "Object Paths" nothing more is mentioned ...

This new release of dbus broke also PackagetKit and system-config-services.

Please raise priority.

(In reply to comment #7)
> I'm back on dbus-1.24.xx for the moment. But if I understand right that makes
> no difference, since the separate policy-files are what matters, right?

DBus 1.2.6 changes default policy, as it claimed to deny by default, even though allow was the effective default.  As this default policy was incorrect for quite a long time, some applications rely on it and need to have their policy files updated.

> No NetworkManager-gnome here, just knetworkmanager (and some other packages for
> that).

Ok, knetworkmanager bug #475468.  Feel free to check if the proposed policy file addresses your problem.

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.