Your message dated Mon, 23 Apr 2012 23:03:58 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#657279: network-manager: Not 
authorized to control networking
has caused the Debian Bug report #657279,
regarding network manager won't reconnnect, various errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
657279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657279
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.2.0-1

Debian testing

If I lose my connection, the network manager won't reestablish the connection.

There's many of these errors, some for State, Default, Default6, etc..:

Window manager warning: Log level 16: _nm_object_get_property: Error
getting 'State' for
/org/freedesktop/NetworkManager/ActiveConnection/4: (19) Method "Get"
with signature "ss" on interface "org.freedesktop.DBus.Properties"
doesn't exist

And if I try to click "on" on the network dropdown in the upper right
menu, there's this error:

Window manager warning: Log level 16: Device activation failed: (32)
Not authorized to control networking.

If I select Network settings in the drop down, and then hit on there:

(gnome-control-center:16161): Gtk-Warning **: Overriding tab label for notebook

This sets the tab to "on" but doesn't seem to do anything else.

Its possible that that eventually fixes the network because it did
come on, either from that or from me running "nm-applet" on the
console (not as root) and then hitting ctrl-c to kill it.

But even if networking does come back, the dropdown menu in the upper
right lists it as off, even if its working.

The only way to fix all of this is just to reboot completely and this
happens every time the connection drops.



--- End Message ---
--- Begin Message ---
On 23.04.2012 22:07, PJ Weisberg wrote:
> This no longer happens if I use gdm3 as my x-display-manager.  That
> solves the mystery of when it stopped working: the first time I tried
> to change my network settings after dropping Gnome3.
> 
> So this might be a bug in both slim and xdm (both of which I've
> tried), or it might be that network-manager is expecting something
> non-standard.

Yeah, those display-managers do not properly support ConsoleKit, so your
desktop session won't be marked as active (you can check with
ck-list-sessions).

slim, xdm and consolekit have relevant bugs about this, so I'm going to
close this one.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to