Bug#523322: [Pkg-xfce-devel] Bug#523322: Bug#523322:

2010-09-01 Thread Luca Niccoli
On 1 September 2010 07:31, Yves-Alexis Perez cor...@debian.org wrote

 I'm not using an older version, I'm using a more recent version :)

 ii  gnome-keyring  2.30.3-1       GNOME keyring services (daemon and
 tools)

I'm using that too. Probably the version of Xfce you're using has the bug fixed

 That's because of the OnlyShowIn line.

I had changed that; it was becaus xfce doesn't check /usr/share/gnome/autostart.
Copying the modified file in /etc/xdg/autostart made it appear and run
at login, but gnome-keyring still doesn't work as a SSH agent.

 Good point. So yes, either it's run as part of Xsession.d stuff (which
 was not possible, aiui?) or xfce4-session runs it, and do it correctly,
 for example using your patch.

It used to be possible to start it in Xsession.d, but now it messes up
the new DBus interface to gnome-keyring (it starts too early I seem to
remember)

 And I'm afraid it might break existing systems. For example, I have
 gnome-keyring installed (and it manages password for stuff like
 evolution) but I *dont* want to use it as ssh-agent. If I tune
 xfce4-session to fix g-k-d start, will it force that behavior?

I think the default is for gnome-keyring to be a ssh-agent; this can
be changed via gconf (setting
/apps/gnome-keyring/daemon-components/ssh to false).
I realise that this is a bit inconvenient; but I'd say that if one
uses many gnome applications will have to install gconf-editor anyway.
(I don't like the fact that there isn't a simpler way to configure
gnome-keyring if you're not using gnome, but this is what upstream has
chosen and I don't think that relying on a bug in xfce4-session not to
impose the ssh-agent to people would be a sensisble choice)
Cheers,

Luca



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523322: [Pkg-xfce-devel] Bug#523322: Bug#523322: Bug#523322:

2010-09-01 Thread Yves-Alexis Perez
On 01/09/2010 11:38, Luca Niccoli wrote:
 On 1 September 2010 07:31, Yves-Alexis Perez cor...@debian.org wrote
 
 I'm not using an older version, I'm using a more recent version :)

 ii  gnome-keyring  2.30.3-1   GNOME keyring services (daemon and
 tools)
 
 I'm using that too. Probably the version of Xfce you're using has the bug 
 fixed
 
 That's because of the OnlyShowIn line.
 
 I had changed that; it was becaus xfce doesn't check 
 /usr/share/gnome/autostart.
 Copying the modified file in /etc/xdg/autostart made it appear and run
 at login, but gnome-keyring still doesn't work as a SSH agent.

Hmh, yeah. Maybe “start gnome services” in Xfce should look at that
autostart dir though (but that deserve a different bug).
 
 Good point. So yes, either it's run as part of Xsession.d stuff (which
 was not possible, aiui?) or xfce4-session runs it, and do it correctly,
 for example using your patch.
 
 It used to be possible to start it in Xsession.d, but now it messes up
 the new DBus interface to gnome-keyring (it starts too early I seem to
 remember)

dbus is usually started using 75dbus_dbus-launch. On my system it's
gpg-agent - dbus-launch - startxfce4.

It might depend on how you start Xfce (if dbus isn't started when
startxfce4 is run, it will start it itself), but in any case, making
sure gnome-keyring is run *after* 75 should work (and would be cleaner
since it'd work in other DE too).
 
 And I'm afraid it might break existing systems. For example, I have
 gnome-keyring installed (and it manages password for stuff like
 evolution) but I *dont* want to use it as ssh-agent. If I tune
 xfce4-session to fix g-k-d start, will it force that behavior?
 
 I think the default is for gnome-keyring to be a ssh-agent; this can
 be changed via gconf (setting
 /apps/gnome-keyring/daemon-components/ssh to false).

I *really* don't like that. Gnome-keyring is pulled by way too much
stuff and if it breaks users system, it's *not* good.

 I realise that this is a bit inconvenient; but I'd say that if one
 uses many gnome applications will have to install gconf-editor anyway.
 (I don't like the fact that there isn't a simpler way to configure
 gnome-keyring if you're not using gnome, but this is what upstream has
 chosen and I don't think that relying on a bug in xfce4-session not to
 impose the ssh-agent to people would be a sensisble choice)

Yes, I agree, but before breaking it for ssh-agent (ang gpg-agent as as
ssh-agent) users systems, I'd prefer having more comments from g-k people.

Cheers,
-- 
Yves-Alexis



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523322: [Pkg-xfce-devel] Bug#523322: Bug#523322: Bug#523322:

2010-09-01 Thread Luca Niccoli
On 1 September 2010 12:23, Yves-Alexis Perez cor...@debian.org wrote:

 dbus is usually started using 75dbus_dbus-launch. On my system it's
 gpg-agent - dbus-launch - startxfce4.

 It might depend on how you start Xfce (if dbus isn't started when
 startxfce4 is run, it will start it itself), but in any case, making
 sure gnome-keyring is run *after* 75 should work (and would be cleaner
 since it'd work in other DE too).

I remember trying that, but it didn't work. I don't remember why
though, I''ll try again later and see what's the problem.
Anyway, this would be a system only setting, which is the opposite of
what you are looking for, i.e. simple user configuration.
I'm positive that putting it in .Xsessionrc didn't work when I tried.

 I *really* don't like that. Gnome-keyring is pulled by way too much
 stuff and if it breaks users system, it's *not* good.

One solution would be to add an option in xfce4-session just to start
gnome-keyring as a ssh agent; simply ignoring the SSH_AUTH_SOCK
variable if that is not set.
Sounds a bit hacky though.

 Yes, I agree, but before breaking it for ssh-agent (ang gpg-agent as as
 ssh-agent) users systems, I'd prefer having more comments from g-k people.

g-k maintainer in debian has been quite silent about this bug (that
was originally filed against it)
Cheers,

Luca



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#523322: [Pkg-xfce-devel] Bug#523322: Bug#523322:

2010-08-31 Thread Yves-Alexis Perez
On mar., 2010-08-31 at 23:24 +0200, Yves-Alexis Perez wrote:
 Btw, I can see that:
 
 /usr/share/gnome/autostart/gnome-keyring-ssh.desktop
 
 contains OnlyShowIn=GNOME;LXDE;
 
 If gnome-keyring-ssh is what you need, wouldn't it be simpler to add
 Xfce to that list? 


And same thing for /usr/share/gnome/autostart/gnome-keyring-secrets.desktop 
which has:

Exec=/usr/bin/gnome-keyring-daemon --start --components=secrets
OnlyShowIn=GNOME;LXDE;

Cheers,
-- 
Yves-Alexis


signature.asc
Description: This is a digitally signed message part


Bug#523322: [Pkg-xfce-devel] Bug#523322: Bug#523322:

2010-08-31 Thread Yves-Alexis Perez
On mar., 2010-08-31 at 23:52 +0200, Luca Niccoli wrote:
 On 31 August 2010 23:24, Yves-Alexis Perez cor...@debian.org wrote:
 
  Hmh, to be honest, gnome-keyring is started properly here (though I'm
  not using 4.6 on that box and can't check on another one).
 
 Maybe if you're not using 4.6 you have an old version of gnome-keyring
 as well? The way it was supposed to be started changed in version 2.26

I'm not using an older version, I'm using a more recent version :)

ii  gnome-keyring  2.30.3-1   GNOME keyring services (daemon and
tools)


 
  Btw, I can see that:
 
  /usr/share/gnome/autostart/gnome-keyring-ssh.desktop
 
  contains OnlyShowIn=GNOME;LXDE;
 
  If gnome-keyring-ssh is what you need, wouldn't it be simpler to add
  Xfce to that list?
 
 It doesn't work; SSH Key Agent doesn't even show up as an option
 among the autostarted applications in xfce4-session-settings .

That's because of the OnlyShowIn line.

 And I don't think that starting it this way could export
 $SSH_AUTH_SOCK to the session (gnome-keyring-daemon just prints it on
 stdout together with other variables, and it's up to the caller to
 export them).

Good point. So yes, either it's run as part of Xsession.d stuff (which
was not possible, aiui?) or xfce4-session runs it, and do it correctly,
for example using your patch.

 Moreover, I think the proper way to decide whether gnome-keyring
 should act as a ssh agent would be via gconf (this is a quite minor
 point).

And I'm afraid it might break existing systems. For example, I have
gnome-keyring installed (and it manages password for stuff like
evolution) but I *dont* want to use it as ssh-agent. If I tune
xfce4-session to fix g-k-d start, will it force that behavior?

Cheers,
-- 
Yves-Alexis


signature.asc
Description: This is a digitally signed message part