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 751776 - spurious PackageKit authentication request on login for remote session
spurious PackageKit authentication request on login for remote session
Status: RESOLVED FIXED
Product: gnome-software
Classification: Applications
Component: General
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-07-01 11:26 UTC by Pierre Ossman
Modified: 2016-02-23 12:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pierre Ossman 2015-07-01 11:26:21 UTC
Pretty much the same as bug 751775, but this time for PackageKit. PackageKit changed their default policy in commit 4888afef which now makes Gnome pop up an unprovoked authentication dialog on login on remote sessions.

The request is "org.freedesktop.packagekit.system-network-proxy-configure" with the message "Authentication is required to set the network proxy used for downloading software". Not sure if more requests will be triggered once that is fixed.
Comment 1 Bastien Nocera 2015-07-01 11:42:17 UTC
There's no PackageKit code in gnome-settings-daemon anymore.
Comment 2 Richard Hughes 2015-07-01 11:49:42 UTC
I'm pretty sure remote sessions just need to be marked as active.
Comment 3 Michael Catanzaro 2015-07-01 13:50:12 UTC
(In reply to Richard Hughes from comment #2)
> I'm pretty sure remote sessions just need to be marked as active.

No, the definition of "active" is "active session on local console." Use allow_any to control settings for remote users (VNC users). See the Declaring Actions section of polkit(8).

If an action is ever performed without user intervention, then it must never require authentication, so either the permissions for allow_active and allow_inactive should be changed to yes (probably not the right thing to do), or we should investigate why that action is triggered just by logging into the desktop.
Comment 4 Pierre Ossman 2015-07-02 06:19:52 UTC
(In reply to Bastien Nocera from comment #1)
> There's no PackageKit code in gnome-settings-daemon anymore.

Sorry, it's difficult, if not impossible, to figure out where these requests come from. I tried grepping for the request name but I couldn't find anything. And dbus-monitor doesn't seem to catch these things either. :/
Comment 5 Pierre Ossman 2015-10-16 12:52:48 UTC
Found the culprit. Check gs_proxy_settings_init() in src/gs-proxy-settings.c. It will:

 a) Change PackageKit's proxy settings whenever it sees a change in gsettings.

 b) Send the current configuration to PackageKit.

The biggest problem right now is b), but a) is problematic as well. You don't want to pester a user with this dialog whenever they update their proxy settings in order to get their browser working.


Not sure what the cleanest UI here is. Perhaps it is wrong to assume that PackageKit should just blindly follow the desktop proxy settings?


In any case, you need to stop this thing from harassing users on login. Perhaps run it before any transaction that might require network activity?
Comment 6 Richard Hughes 2016-02-22 20:44:05 UTC
I think we just need to make the VNC sessions as active, no?
Comment 7 Pierre Ossman 2016-02-23 07:07:20 UTC
"active" still means something that isn't correct for VNC sessions. See comment 2 and comment 3. ;)
Comment 8 Richard Hughes 2016-02-23 12:51:57 UTC
Author: Richard Hughes <richard@hughsie.com>
Date:   Tue Feb 23 12:50:02 2016 +0000

    Never request auth for setting the proxy
    
    Resolves: https://bugzilla.gnome.org/show_bug.cgi?id=751776