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-gnome: Should not create system-wide connections by
default
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-gnome
Version: 0.9.0-3
Severity: important
Dear Maintainer,
nm-connection-editor creates system-wide connections by default. This forces
the active user to authenticate as an administrative user or as root.
The previous behaviour (I'd say before 0.9 but not 100% sure) was imho
correct: standard users could create private connections without needing
extra rights. The current default behaviour prevents standard users from
creating any connection, even private.
Cheers,
Julien
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-rc7-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-gnome depends on:
ii dbus-x11 1.4.16-1
ii gconf2 2.32.4-1
ii gnome-icon-theme 3.2.0-1
ii libatk1.0-0 2.2.0-2
ii libc6 2.13-21
ii libcairo-gobject2 1.10.2-6.1
ii libcairo2 1.10.2-6.1
ii libdbus-1-3 1.4.16-1
ii libdbus-glib-1-2 0.98-1
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.6-2
ii libgconf2-4 2.32.4-1
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.8-1
ii libgnome-bluetooth8 3.2.0-2
ii libgnome-keyring0 3.2.0-2
ii libgtk-3-0 3.0.12-2
ii libnm-glib-vpn1 0.9.0-2
ii libnm-glib4 0.9.0-2
ii libnm-util2 0.9.0-2
ii libnotify4 0.7.4-1
ii libpango1.0-0 1.29.4-1
ii network-manager 0.9.0-2
ii policykit-1-gnome 0.102-2
Versions of packages network-manager-gnome recommends:
ii gnome-bluetooth 3.2.0-2
ii libpam-gnome-keyring [libpam-keyring] 3.0.3-2
ii mobile-broadband-provider-info 20110806-1
ii notification-daemon 0.7.3-1
ii notify-osd [notification-daemon] 0.9.30-1
Versions of packages network-manager-gnome suggests:
pn network-manager-openvpn-gnome <none>
pn network-manager-pptp-gnome <none>
pn network-manager-vpnc-gnome <none>
-- no debconf information
--
.''`. Julien Valroff ~ <[email protected]> ~ <[email protected]>
: :' : Debian Developer & Free software contributor
`. `'` http://www.kirya.net/
`- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1
--- 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 ---
