Hi \t,
in the global /etc/X11/xinit/xinitrc qtile is not called, so that should
not be the case.
The export only works if you call the command before that too:
eval $(/usr/bin/gnome-keyring-daemon --start
--components=gpg,pkcs11,secrets,ssh)
It will start a process and create the named variables. By exporting
they are made available outside of the current scope.
In a shell it would work like following:
$> FOO="fubar"
$> echo $FOO
fubar
$> bash
$> echo $FOO
$> exit
$> export FOO
$> echo $FOO
fubar
$> exit
not sure though how it works in this context.
-- Niklas
On 21.03.2014 17:09, Tycho Andersen wrote:
Hi Niklas,
On Fri, Mar 21, 2014 at 04:54:58PM +0100, Niklas Semmler wrote:
It is! (-rwxr--r--)
If that would be the problem qtile wouldn't start either, right?
I'm not sure, although I think it would just silently failover to
/etc/X11/xinit/xinitrc if it wasn't, giving you the behavior you're
seeing.
Actually though, when I try your syntax I don't get anything either:
hopstrocity:~$ export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO
SSH_AUTH_SOCK
hopstrocity:~$ env | grep GNOME
hopstrocity:~ 1$
So I'd check to make sure you're exporting the environment variables
correctly in the shell.
\t
--
You received this message because you are subscribed to the Google Groups
"qtile-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
