Re: nm-connection-editor not working

[Dan Williams <dcbw redhat com>]

On Wed, 2014-01-08 at 11:00 -0500, Neal Becker wrote:
> Interesting.
>
> I was using x2go remote desktop.

Ok, that would make a difference.  Check:

systemd-loginctl

and grab the session number for the x2go session.  Then:

systemd-loginctl show-session X

and lets see what "Active" says.

If there is no session for the x2go, then that's the problem.  However,
it's a problem that we're aware of, and that we intend to fix.  It also
prevents random SSH sessions from correctly using nmcli.

The core problem here is (I think) the "at_console" section of
NetworkManager's D-Bus permissions.  We're going to phase out at_console
stuff and instead rely on systmed/consolekit and PolicyKit for
authentication in the near future.

Dan

> I rebooted but no difference.
>
> Then I hooked up monitor and kb, and logged in locally.  With local
> connection, nm seems to work normally.
> While logged in locally, I tried x2go and nm worked remotely.
> Then logged off local, logged off remote.
> Then start x2go again.  Once again, nm doesn't work through remote
> connection.
>
>
> On Wed, Jan 8, 2014 at 10:36 AM, Dan Williams <dcbw redhat com> wrote:
>
> > On Wed, 2014-01-08 at 09:43 -0500, Neal Becker wrote:
> > > Error org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3
> > > matched rules; type="method_call", sender=":1.5090" (uid=1000 pid=11577
> > > comm="dbus-send --system --print-reply --dest=org.freede")
> > > interface="org.freedesktop.DBus.Properties" member="GetAll" error
> > > name="(unset)" requested_reply="0"
> > > destination="org.freedesktop.NetworkManager" (uid=0 pid=602
> > > comm="/usr/sbin/NetworkManager --no-daemon ")
> >
> > Ok, that shows that it's a D-Bus issue, not an NM specific one AFAICT.
> > Have you recently updated either NetworkManager or D-Bus?
> >
> > First thing to try is "sudo killall -HUP dbus-daemon" to get it to
> > reload permissions.
> >
> > Next thing to try is a reboot; there may still be one or two cases where
> > D-Bus doesn't correctly reload permissions after clients (like
> > NetworkManager) are updated; I just saw a bug fix for something like
> > that this week.
> >
> > Last idea may be SELinux?  Try "setenforce 0" if you're running in
> > Enforcing mode, but I don't think SELinux is a likely culprit here.
> >
> > Dan
> >
> > > On Wed, Jan 8, 2014 at 9:44 AM, Dan Williams <dcbw redhat com> wrote:
> > >
> > > > On Wed, 2014-01-08 at 09:39 -0500, Neal Becker wrote:
> > > > > Any idea why this isn't working?
> > > > >
> > > > > nm-connection-editor
> > > > >
> > > > > ** (nm-connection-editor:11070): WARNING **: Could not initialize
> > > > NMClient
> > > > > /org/freedesktop/NetworkManager: Rejected send message, 3 matched
> > rules;
> > > > > type="method_call", sender=":1.5085" (uid=1000 pid=11070
> > > > comm="nm-connection-
> > > > > editor ") interface="org.freedesktop.DBus.Properties" member="GetAll"
> > > > error
> > > > > name="(unset)" requested_reply="0"
> > > > destination="org.freedesktop.NetworkManager"
> > > > > (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ")
> > > > >
> > > > > Now if I try to add a wired enet, there are no interfaces shown.
> > > >
> > > > What does this command result in?  It's the same thing the editor is
> > > > doing:
> > > >
> > > > dbus-send --system --print-reply
> > > > --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
> > > > org.freedesktop.DBus.Properties.GetAll
> > > > string:"org.freedesktop.NetworkManager"
> > > >
> > > > (all on one line of course)
> > > >
> > > > Dan