Hi, I think that I've been bitten by this. My /var/log/NetworkManager shows something similar to this : May 17 22:35:52 laptop NetworkManager: <WARN> get_secrets_cb(): Couldn't get connection secrets: Rejected send message, 13 matched rules; type="method_call", sender=":1.12" (uid=0 pid=2096 comm="/usr/sbin/NetworkManager) interface="org.freedesktop.NetworkManagerSettings.Connection.Secrets" member="GetSecrets" error name="(unset)" requested_reply=0 destination="org.freedesktop.NetworkManagerUserSettings" (uid=1000 pid=3533 comm="/usr/bin/knetworkmanager)). I've tried copying the suggested config into both /etc/dbus-1/system.d/Network-frontend.conf and also into /etc/dbus-1/session.d/Network-frontend.conf. I've restarted dbus, networkmanager, rebooted several times. It still does not work. I've also now changed some of the other files in /etc/dbus-1 to reduce the amount of security (yeah, yeah, I know it's a bad idea, however I'm on a laptop and am the only user). I'm currently using cnetworkmanager as root to get around this issue, but I'd prefer to get back to a correctly working system. Any help would be appreciated. Thanks, CPH On Wed 28 Apr 2010 22:16:46 Tejas Guruswamy wrote:

Hi guys,

As I started my machine after the latest zypper up, I found the following recent commit has broken NetworkManager for KDE:KDE4:Factory 11.2 users for obvious reasons (we got the updated NetworkManager-kde4 from KKFD, but not NetworkManager, so no dbus conf)

+Fri Apr 23 10:20:23 UTC 2010 - bili@novell.com + +- Add a general frontend dbus configuration in NetworkManager + so delete the conf in knetworkmanager, bili@novell.com(bnc#476502).

Since a lot of people use 11.2 + KKFD I thought it would be best to publicise the workaround as soon as I experienced this. Put the new dbus conf from factory NetworkManager [ http://pastebin.com/5X7x9JHY ] in /etc/dbus-1/system.d as NetworkManager-frontend.conf also available on build.oo from the Factory NetworkManager package

I know that backwards compatibility shouldn't hold back development, but it would be nice if this change was made in a way that didn't kill 11.2 users. Solutions might be an ugly specfile hack or to somehow provide new NetworkManager to 11.2 users. I know its in GNOME:Factory, but I'd rather not add that massive repo if I didn't have to. Is it sensible to have KKFD aggregating factory NetworkManager as a sort of backport for 11.2 users?

Anyway there will probably be quite a few surprised users, knetworkmanager pops up a really scary dialog on reboot after this change, saying sth like "Knetworkmanager cannot provide user settings ... Knetworkmanager will not start on startup ever again", so here's your heads up.

Regards, Tejas -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org