Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18825 - After upgrading dbus and dbus-core to version 1.2.24-1, Network Manager no longer works.

Attached to Project: Arch Linux
Opened by smradlev (smradlev) - Thursday, 25 March 2010, 00:37 GMT
Last edited by Jan de Groot (JGC) - Thursday, 25 March 2010, 15:08 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrading to dbus and dbus-core 1.2.24-1, the Network Manager (nm-applet) no longer works. I get:
[~]$ nm-applet
** (nm-applet:2622): WARNING **: <WARN> applet_dbus_manager_start_service(): Could not acquire the NetworkManagerUserSettings service.
Message: 'Connection ":1.56" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file'

I'm not sure about the number above (whether it was 2622), since I forgot to copy the whole message before reverting to dbus and dbus-core version 1.2.22-1. After doing that nm-applet works again.

Additional info:
* package version(s)
dbus and dbus-core 1.2.24-1
* config and/or log files etc.


Steps to reproduce:
Upgrade dbus and dbus-core to version 1.2.24-1 and reboot. The nm-applet is no longer there and I have no network connection.
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 25 March 2010, 15:08 GMT
Reason for closing:  Works for me
Additional comments about closing:  Works fine here, reporter also cannot reproduce it anymore.
Comment by Ionut Biru (wonder) - Thursday, 25 March 2010, 01:15 GMT
edited:

i can't replicate.
Comment by Jan de Groot (JGC) - Thursday, 25 March 2010, 09:44 GMT
I can't reproduce it either. If you used non-standard ways to configure permissions to access networkmanager, the update could have broken that.
Comment by smradlev (smradlev) - Thursday, 25 March 2010, 14:52 GMT
I haven't touched any of the NM configs.

Today I tried upgrading after I logged out from my gnome session first, and this time the upgrade didn't brake the Network Manager. I have no idea why it worked this time ...
Comment by Ionut Biru (wonder) - Thursday, 25 March 2010, 15:00 GMT
the only thing that i have in mind is that you are not authorized to consolekit.
1) use gdm
2) "exec ck-launch-session wm" in .xinitrc

Loading...