http://bugzilla.opensuse.org/show_bug.cgi?id=1088564
http://bugzilla.opensuse.org/show_bug.cgi?id=1088564#c5
Neil Rickert changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(nwr10cst-oslnx@ya |
|hoo.com) |
--- Comment #5 from Neil Rickert ---
I'm not quite sure what you are asking.
ssh-agent has always been started for KDE and other desktops.
When Gnome first became available on Wayland, that had the same problem. It is
now corrected, but I think that uses seahorse.
The KaOS distro does start ssh-agent on Wayland session startup (perhaps only
if ".ssh" exists in home directory.
I can manage either way, but some consistency would be useful.
I'm currently starting from my shell startup script. That's ".login" since I
am a csh user. In effect, the startup script checks whether $SSH_AUTH_SOCK is
defined in the environment. If not defined, it uses:
eval `ssh-agent -c`
to start ssh-agent.
This depends on the session startup running the shell startup script. Starting
as a normal autostart application probably would not work, because that would
not set the environment for the entire session.
--
You are receiving this mail because:
You are on the CC list for the bug.
