After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619323 - sleep/enable need PolicyKit authorization
sleep/enable need PolicyKit authorization
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-05-21 20:52 UTC by Andy Lutomirski
Modified: 2010-09-01 21:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andy Lutomirski 2010-05-21 20:52:45 UTC
[This is actually F13's NetworkManager 0.8.1-0.1.git20100510, but upstream git doesn't look like anything's changed.]

IMO NetworkManager should use policykit for all setting changes.  Here are two problems with the current state of affairs:

1. Set up a machine running nm.  ssh in as a random user (who isn't logged in locally) and type 'nmcli nm sleep.'  Don't try this on a machine you're not sitting in front of.

2. Set up a multiuser machine that users are expected to log into locally but where you don't want them messing up ssh users.  Become annoyed when you can't figure out how to make policykit do that.

(Of course, you can use whatever setting plugin you have to prevent NM from managing your connections, but then firefox always thinks you're offline, which is a whole different bug (if you even think it's a bug).)
Comment 1 Dan Williams 2010-05-22 15:58:07 UTC
This is something I'm working on right now actually.
Comment 2 Dan Williams 2010-09-01 21:42:19 UTC
Fixed back in June (Enable Networking) and last week (Enable Wifi).