https://bugzilla.novell.com/show_bug.cgi?id=351884
User robin.listas@telefonica.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=351884#c4
Carlos Robinson changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|robin.listas@telefonica.net |
--- Comment #4 from Carlos Robinson 2008-01-07 17:24:42 MST ---
Seahorse-agent is started, I think, because once I started the seahorse
program, went to preferences or somewhere and said I wanted the agent. That
must have been months ago, so I don't remember the details. At least, in 10.3 I
can run seahorse without it crashing, it is an improvement.
And you are right, there are entries in ~/.gnome2/session (I'll attach it
complete later):
5,Program=seahorse-agent
5,CurrentDirectory=/home/cer
5,CloneCommand=seahorse-agent --sm-config-prefix /seahorse-agent-V2r6aH/
5,RestartCommand=seahorse-agent --sm-config-prefix /seahorse-agent-V2r6aH/
--sm-client-id 11c0a8010c000119470880700000205230004 --screen 0
12,Program=seahorse-agent
12,CurrentDirectory=/home/cer
12,CloneCommand=seahorse-agent --sm-config-prefix /seahorse-agent-xqyZu2/
12,RestartCommand=seahorse-agent --sm-config-prefix /seahorse-agent-xqyZu2/
--sm-client-id 11c0a8010c000119470830500000184410000 --screen 0
19,RestartCommand=/usr/bin/seahorse-agent
So... is that the culprit of the double seahorse-gent?
[...]
I go to "sessions" in the gnome control center, and in the "startup programs"
tab the "seahorse agent" click box is ticked. I believe I ticked it there the
first time.
I just did a grep search (mc) for the string "seahorse-agent", and I found
another entry, in "./.config/autostart/seahorse-agent.desktop":
Exec=/usr/bin/seahorse-agent
What I still don't understand is how I got three 'seahorse-agent' instances
running. My hypothesis is that after I configured it to start, when some other
time I saved the session, from then on, the session managerwhatever also starts
it: those would be the two entries with parameters (that would be a bug, I
think: save session should not save a program that is defined to start
somewhere else - or viceversa).
There still remains unexplained the other agent without parameters... also save
session?. Plus the ssh-agent, which must started by the script ~/.xsession,
although it is set to "no":
# If ssh is configured and ssh-agent is wanted set "yes"
#
usessh="no"
..
#
# Run ssh-agent only if ssh is configured and avaliable.
#
sshagent="no"
if test "$usessh" = "yes" -a -d $HOME/.ssh ; then
type ssh-agent > /dev/null 2>&1 && sshagent="yes"
fi
There is also an error in .xsession-errors:
(gnome-panel:18228): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion
`text_uri != NULL' failed
can't lock memory: Cannot allocate memoryWARNING: not using secure memory for
passwords
** Message: Another GPG agent already running
** Message: Another GPG agent already running
** Message: Another GPG agent already running
** (seahorse-agent:18334): WARNING **: couldn't connect to SSH agent at:
/tmp/ssh-IoNF18156/agent.18156: Connection refused
** (seahorse-agent:18334): WARNING **: couldn't contact SSH agent. Cannot proxy
SSH key requests.
kbuildsycoca running...
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Nautilus-Share-Message: REFRESHING SHARES
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.