On Tue, 2016-04-12 at 19:07 +0100, Simon McVittie wrote: > On Sun, 13 Mar 2016 at 09:47:43 +0000, Sam Morris wrote: > > > > This is caused by gnome-terminal's design of spawning all child > > processes via gnome-terminal-server which is spawned from the > > user's dbus session. > > > > For a 'fun' reproduction, launch nm-connection-editor from gnome- > > terminal and try to figure out why it doesn't work. :) > > This has been a problem in the past, but your reproducer works fine for me > (under GNOME Shell, which among its other functions acts as the polkit > agent). We fixed several issues related to this in polkit and udisks2 > shortly after I introduced dbus-user-session.
Ok, now I'm lost. At first I assumed that this worked for you because you had policykit-1 from experimental installed, including the fix for #779988; however I just noticed that this patch was backported to the version in testing, and so should already be working on my system. > Is this perhaps specific to running in an environment that does not already > provide its own polkit agent that is a child of the login session? For > instance, if you launch an xterm or other non-client/server terminal from > your desktop environment (Alt+F2 in GNOME/Xfce/probably others), run > /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 there,then > run nm-connection-editor from your gnome-terminal, does that work? I'm not sure where the polkit authentication agent comes in to play... I am using i3, and I launch polkit-gnome-authentication-agent from my .xsessionrc. Processes launched by xterm end up in my user session's scope, which polkit is happy with. It's just processes launched by gnome-terminal- server, which end up in the dbus.session cgroup, that polkit won't authorize. I had planned to work around this by removing dbus-user-session, but now that it seems that the fix for #779988 was backported to the version of polkit on my system, I'm no longer sure what to do! -- Sam Morris <https://robots.org.uk/> CAAA AA1A CA69 A83A 892B 1855 D20B 4202 5CDA 27B9
signature.asc
Description: This is a digitally signed message part
