Bug 389896

Summary: Better GNOME integration in the login scripts
Product: [openSUSE] openSUSE 11.0 Reporter: Vincent Untz <vuntz>
Component: X.OrgAssignee: Dr. Werner Fink <werner>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Enhancement    
Priority: P5 - None    
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Vincent Untz 2008-05-13 17:20:03 UTC 
Right now, in /etc/X11/xdm/sys.xsession, gpg-agent and ssh-agent are started. This is not something that should be done when the session is a GNOME session:

 + gnome-keyring (started by PAM, or later by gnome-session) is an SSH agent, so ssh-agent isn't needed

 + seahorse-agent is the GPG agent used in GNOME, which offers some nice features. So "seahorse-agent -x $command" should be used instead of gpg-agent. (note: in the future, seahorse-agent will be removed and integrated in gnome-keyring, but it won't happen for openSUSE 11.0).

I'm not quite sure what's the best way to fix this. Should it be hardcoded in /etc/X11/xdm/sys.xsession? Or maybe we could add some files in /etc/X11/xinit/xinitrc.d/? (eg: a file that sets a RUN_SSH_AGENT environment variable to 0, and a file that prepends "seahorse-agent -x" to the command and sets RUN_GPG_AGENT to 0)

In both cases, we need /etc/X11/xdm/sys.xsession to be updated. If required, we can ship files in gnome-keyring/seahorse packages and install in /etc/X11/xinit/xinitrc.d/.
Comment 2 Stefan Dirsch 2008-05-13 19:20:41 UTC 
Werner knows these scripts best.

I'm wondering that you are requesting such changes *after* Beta2. A better time to integrate such changes are *before* Beta1.
Comment 3 Vincent Untz 2008-05-13 19:52:27 UTC 
(In reply to comment #2 from Stefan Dirsch)
> I'm wondering that you are requesting such changes *after* Beta2. A better time
> to integrate such changes are *before* Beta1.

I completely agree with your point. It's just that I become aware of this today, while trying to understand why a bug is occuring. If you feel strong about it, we can delay these changes to 11.1.
Comment 4 Vincent Untz 2008-05-13 21:52:25 UTC 
Actually, the bug I investigated is directly related to this: see bug 383353.
Comment 5 Dr. Werner Fink 2008-05-14 15:55:50 UTC 

*** This bug has been marked as a duplicate of bug 38335 ***
Comment 6 JP Rosevear 2008-05-28 18:14:43 UTC 

*** This bug has been marked as a duplicate of bug 383353 ***