Bugzilla – Bug 790222
dbus: something is wrong with at_console, user cannot communicate with NetworkManager anymore.
Last modified: 2012-11-23 13:34:07 UTC
After todays update to Factory, the nm-applet does no longer appear on the desktop, but is still running. nm-tool gives: seife@susi:~> nm-tool ** (process:2980): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.86" (uid=10329 pid=2980 comm="nm-tool ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=988 comm="/usr/sbin/NetworkManager --no-daemon ") NetworkManager Tool State: unknown ** (process:2980): WARNING **: error: could not connect to NetworkManager this should be allowed by the at_console thing in /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf, the same problem happens to bluetooth devices. I "fixed" it for now with this patch: diff -upwr /tmp/system.d/bluetooth.conf /etc/dbus-1/system.d/bluetooth.conf --- /tmp/system.d/bluetooth.conf 2012-11-15 19:24:51.000000000 +0100 +++ /etc/dbus-1/system.d/bluetooth.conf 2012-11-19 10:38:12.089714698 +0100 @@ -29,7 +29,8 @@ </policy> <policy context="default"> - <deny send_destination="org.bluez"/> + <allow send_destination="org.bluez"/> +<!-- <deny send_destination="org.bluez"/> --> </policy> </busconfig> .conf --- /tmp/system.d/org.freedesktop.NetworkManager.conf 2012-11-12 13:27:50.000000000 +0100 +++ /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf 2012-11-19 10:40:15.310174230 +0100 @@ -24,7 +24,7 @@ <allow send_destination="org.freedesktop.NetworkManager.pptp"/> <allow send_destination="org.freedesktop.NetworkManager.vpnc"/> </policy> - <policy at_console="true"> + <policy context="default"> <allow send_destination="org.freedesktop.NetworkManager"/> <allow send_destination="org.freedesktop.NetworkManager" @@ -85,6 +85,7 @@ send_interface="org.freedesktop.NetworkManager" send_member="wake"/> </policy> +<!-- <policy context="default"> <deny own="org.freedesktop.NetworkManager"/> @@ -112,5 +113,6 @@ send_interface="org.freedesktop.NetworkManager" send_member="wake"/> </policy> +--> </busconfig> but this is surely not "production ready" :-)
Which version of polkit did you get on your system? Latest .changes entries of polkit?
(info: this is likely due to all the checkins happening at the moment to switch from CK to systemd-login... all packages need to be 'the' same to be reliable)
seife@susi:~> rpm -q polkit polkit-0.108-1.1.x86_64 seife@susi:~> rpm -q --changelog polkit|head -16 * Do Nov 15 2012 dimstar@opensuse.org - Update to version 0.108: + PolkitAgent: Avoid crashing if initializing the server object fails + Fall back to authenticating as uid 0 if the list of admin identities is empty + Dynamically load libmozjs185.so and cope with it not being available + docs: mention the audience for authorization rules + build: Fix .gir generation for parallel make - Only conditionally Require ConsoleKit when with_systemd is 0: systemd support obsoletes ConsoleKit. - Add polkit-link-gmodule.patch: Link against gmodule-2.0. - Change libpolkit0 to require polkit >= %version instead of the exact version. This will ease upgrade problems should there ever be a soname bump of libpolkit0.
that should be the right one for now.. which DM are you using (kdm,xdm,gdm,[...]dm)? And which DE (kde,gnome.lxde,xfce,[...])? I somewhat suspect that your DM relies on CK while the rest of the system moved forward... having the info about the DM/DE might allow us to assign it to the right team.
DM is gdm, DE is xfce4 seife@susi:~> ps xauwww|grep gdm root 1012 0.0 0.0 192400 3252 ? Sl 10:10 0:00 /usr/sbin/gdm root 1036 0.0 0.0 282700 4232 ? Sl 10:10 0:00 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_0 root 1049 1.6 0.7 237036 45088 tty7 Ss+ 10:10 6:02 /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-pXCKpW/database -seat seat0 -nolisten tcp vt7 root 1646 0.0 0.0 234896 4436 ? Sl 10:10 0:00 gdm-session-worker [pam/gdm-password] seife@susi:~> ps xau|grep dbus message+ 970 0.0 0.0 20756 2652 ? Ss 10:10 0:01 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation seife 1654 0.0 0.0 12820 716 ? Ss 10:10 0:00 /usr/bin/ck-launch-session /usr/bin/dbus-launch --sh-syntax --exit-with-session /home/seife/.xinitrc seife 1711 0.0 0.0 13824 544 ? S 10:10 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session /home/seife/.xinitrc seife 1712 0.0 0.0 21440 2184 ? Ss 10:10 0:01 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
which package of dbus-1 are you running ? you might not have the one with systemd integration enabled.
susi:~ # rpm -q dbus-1 dbus-1-1.5.12-13.1.x86_64 susi:~ # rpm -q --changelog dbus-1|head * Fri Nov 16 2012 fcrozat@suse.com - Move default home from /var/run/dbus to /run/dbus - Fix useradd invocation: -o is useless without -u and newer versions of pwdutils/shadowutils fail on this now. * Thu Nov 08 2012 tittiatcoke@gmail.com - Link /usr/bin/dbus-send to /bin/dbus-send. Upower uses dbus-send to receive signals from systemd regarding resuming, however looks for the moment in the wrong directory.
you need the next release of the package, containing : Fri Nov 16 12:56:04 UTC 2012 - dimstar@opensuse.org - Enable systemd integration (with_systemd 1): follow the rest of the distribution enabling systemd support. As agreed, systemd is the main supported way for 12.3.
yes, works again after todays update of dus-1