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: Connecting to a wifi network requires
org.freedesktop.NM.settings.modify.system privileges
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.0-2
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Since NetworkManager 0.9, a simple user is not allowed to connect to
some wireless network unless it is granted (through policy kit or
appropriate permissions)
org.freedesktop.NetworkManager.settings.modify.system. This permission
allows to alter existing connections as well. An active user should be
authorized to use any wireless network if he wants to by default (like
in previous versions). Or it should be possible to configure network
manager to allow users to connect to wireless networks without
enabling them to modify other system settings.
- -- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.113
ii dbus 1.4.14-1
ii isc-dhcp-client 4.1.1-P1-17
ii libc6 2.13-21
ii libdbus-1-3 1.4.14-1
ii libdbus-glib-1-2 0.94-4
ii libgcrypt11 1.5.0-3
ii libglib2.0-0 2.28.6-1
ii libgnutls26 2.12.10-2
ii libgudev-1.0-0 172-1
ii libnl1 1.1-7
ii libnm-glib4 0.9.0-2
ii libnm-util2 0.9.0-2
ii libpolkit-gobject-1-0 0.102-1
ii libuuid1 2.19.1-5
ii lsb-base 3.2-28
ii udev 172-1
ii wpasupplicant 0.7.3-3.1
Versions of packages network-manager recommends:
ii dnsmasq-base 2.58-3
ii iptables 1.4.12-1
ii modemmanager 0.5-1
ii policykit-1 0.102-1
ii ppp 2.4.5-5
Versions of packages network-manager suggests:
pn avahi-autoipd <none>
- -- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
no-auto-default=60:eb:69:ce:6e:a0,
[ifupdown]
managed=false
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk53hrAACgkQKFvXofIqeU7MZgCfUhWv55uMe7XwAloAlsV5luLq
fI8AnRgNNKT/2gFxN/zbNdDvO/wDPOCf
=PlLS
-----END PGP SIGNATURE-----
--- 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?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
