Bug#775189: mate-session spawns gnome-keyring unconditionally
infirit at gmail.com
Mon Jan 12 20:25:47 UTC 2015
On Mon, 12 Jan 2015 13:37:29 +0000 Mike Gabriel
<mike.gabriel at das-netzwerkteam.de> wrote:
> On Mo 12 Jan 2015 13:38:40 CET, Faidon Liambotis wrote:
> > Since upstream commit 8a20baf39f781184d6126e0947e9fd4d9a115fab,
> > mate-session-manager spawns gnome-keyring-daemon, with no option to turn
> > it off, or pass arguments to it (such as --components).
> > While this is bad in itself, it gets worse: keyring is spawned *after*
> > the regular user-configured autostart programs are run. gnome-keyring's
> > default set of components includes a GPG & a SSH agent and rightfully
> > exports SSH_AUTH_SOCK and GPG_AGENT_INFO.
The gnome compat code is one of the first things to run, even before the
main manager is started that handles autostart. I am surpised you see it
being run after autostart... Start mate-session with --debug and look
for "MsmGnome" in the log to see when it is run.
> The "clobbering" could be disabled via gconf in GNOMEv2 and I am
> pretty sure there is something similar possible by manipulating with
There is no way to disable it atm other than removing gnome-keyring.
The reason it is run this way is that MATE relies on
gnome-keyring/libsecret instead of the forked 2.32 versions. And as
gnome-keyring does not export the env variables we run gnome-keyring
which outputs the variables that mate-session then exports them before
autostarting the wm, desktop etc etc..
Attached is a preliminary patch that uses a gsettings key to determine
which parts of the gnome compat should be started. Modify the list in
gnome-compat-startup and remove the 'keyring' value. This should stop
the "clobbering" of the variables.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3436 bytes
Desc: not available
More information about the pkg-mate-team