version: gdm-2.30.2-1 XSession shouldn't start ssh-agent for XFCe, just like GNOME, since gnome-keyring-daemon deals with that, and it's started automatically.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Yes. I can confirm that this is still a problem in Fedora 16. It's rather annoying as it means that the passphrase for SSH keys is not taken from the gnome-keyring -- it asks you every time. I *think* the problem stems from, /etc/xdg/xfce4/xinitrc Possibly somewhere around, ... # ignore stale ssh-agents if test "$SSH_AGENT_PID"; then if ! kill -0 $SSH_AGENT_PID; then unset SSH_AGENT_PID unset SSH_AUTH_SOCK fi fi ... which I suspect overrides the gnome-keyring settings. But it's probably a bit of a stab in the dark. Can anyone else shed some light on this?
Created attachment 536936 [details] Patch to let XFce determine whether to start an agent This patch fixes the issue for me, combined with running: xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -s false -t bool to disable XFce's ssh-agent starting.
Thanks, Daniel. But this patch + command did not work for me. Peter.
FYI. This is a wider problem than I first thought. More information can be found at the following locations, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646938 https://bugzilla.xfce.org/show_bug.cgi?id=8014 One workaround that I can confirm works is to "Launch GNOME services on startup" in the Xfce "Session and Startup" settings under the "Advanced" tab. But this is a really bloated way of addressing this problem. What I did was add the following to my ~/.bashrc export `/usr/bin/gnome-keyring-daemon --start --components=ssh` which seems to work quite nicely.
Correction, this is better placed in ~/.bash_profile rather than ~/.bashrc -- but both would work.
I don't think that would work, because AFAIK, those are sourcerd very late in the process. Probably ~/.profile would work, if this is applied: https://bugzilla.redhat.com/show_bug.cgi?id=551508 But wouldn't it be better to just take gnome-keyring-daemon, and strip it down to have something generic that Xfce can depend on?
(In reply to comment #15) > I don't think that would work, because AFAIK, those are sourcerd very late in > the process. I was just posting what worked for me in the hope that it might help someone else. > Probably ~/.profile would work, if this is applied: > https://bugzilla.redhat.com/show_bug.cgi?id=551508 > > But wouldn't it be better to just take gnome-keyring-daemon, and strip it down > to have something generic that Xfce can depend on? Of course... But until this is done (and I won't be holding my breath), a workaround is required.
Looks like Fedora developers don't care about Xfce.