Bug#329130: Open its dialog at gnome start if seahorse-agent is enabled (0.7.9)

2005-09-21 Thread Jean-Luc Coulon (f5ibh)

Jose,

Le 20.09.2005 23:26:22, Jose Carlos Garcia Sogo a écrit :

El mar, 20-09-2005 a las 05:04 +, Jean-Luc Coulon (f5ibh)
escribió:
 Jose,

[...]

 I've just enabled seahorse-agent in sessions preferences of gnome.

 How I reproduce the problem:
 - update seahorse ;-)
 - exit gnome
 - restart gnome (so far, no problem)
 - start balsa
 - write a message and sign it, the password is cached
 - stop balsa
 - exit gnome

 If I've a look in .gnome2/session, I've now this entry:
 5,id=11c0a8010f0001127192298019977
 5,Program=seahorse
 5,CurrentDirectory=/home/jean-luc
 5,CloneCommand=seahorse
 5,RestartCommand=seahorse --sm-client-id
 11c0a8010f0001127192298019977 -

 - restart gnome, I've now the Encryption Key Manager displayed.

 When I use the previous version of seahorse, I've not this entry
 created in .gnome2/session

  It seems you have saved your session with seahorse-agent loaded, and
it must be trying to load it twice. Please, remove that entry from
that
file, and restart GNOME.


When I strart hnome for the first time, I've not the seahorse window.
I've seahorse-agent in the program at start as decribed in encryption  
properties
If I look in .gnome/session just after gnome starts, I cas see two  
entries:

one for seahorse-agent
one for seahorse

If I delete (or set the trash attribute) to seahorse, I've (of course)  
not the problem at the next run. Otherwise seahorse is in  
.gnome2/session and starts



If seahorse-agent does not start automatically, you have to go to
third
tab in session config window and add it there (this will create
a .gnome2/session-manual file).


This si what I did but both seahorse-agent and seahorse are present.

If I revert to the previous version (0.7.8-2) of seahorse, I've not  
this problem.




 This should solve your problem. Please, tell me if this works.

--
Jose Carlos Garcia Sogo


Regards

Jean-Luc


pgpPrT1PMQGZv.pgp
Description: PGP signature


Bug#329130: Open its dialog at gnome start if seahorse-agent is enabled (0.7.9)

2005-09-20 Thread Jose Carlos Garcia Sogo
El mar, 20-09-2005 a las 05:04 +, Jean-Luc Coulon (f5ibh) escribió:
 Jose,
 
[...]

 I've just enabled seahorse-agent in sessions preferences of gnome.
 
 How I reproduce the problem:
 - update seahorse ;-)
 - exit gnome
 - restart gnome (so far, no problem)
 - start balsa
 - write a message and sign it, the password is cached
 - stop balsa
 - exit gnome
 
 If I've a look in .gnome2/session, I've now this entry:
 5,id=11c0a8010f0001127192298019977
 5,Program=seahorse
 5,CurrentDirectory=/home/jean-luc
 5,CloneCommand=seahorse
 5,RestartCommand=seahorse --sm-client-id  
 11c0a8010f0001127192298019977 -
 
 - restart gnome, I've now the Encryption Key Manager displayed.
 
 When I use the previous version of seahorse, I've not this entry  
 created in .gnome2/session

  It seems you have saved your session with seahorse-agent loaded, and
it must be trying to load it twice. Please, remove that entry from that
file, and restart GNOME. 
If seahorse-agent does not start automatically, you have to go to third
tab in session config window and add it there (this will create
a .gnome2/session-manual file).

 This should solve your problem. Please, tell me if this works.

-- 
Jose Carlos Garcia Sogo
   [EMAIL PROTECTED]



Bug#329130: Open its dialog at gnome start if seahorse-agent is enabled (0.7.9)

2005-09-19 Thread Jean-Luc Coulon (f5ibh)

Jose,


 Hi,

 With version 0.7.9-2, if seahorse-agent is enabled in the gnome
session then the
 seahorse dialog is opened each time gnome starts.

 I've reverted to the previous version ad this doesnt happens with
0.7.8-2

 Sorry, but it is unreproducible here. Please, check you're only
running
one copy, and that you're not launching any problem that can be trying
to verify one signature, so you get asked for a password for it, after
runnning seahorse-agent.


I've just enabled seahorse-agent in sessions preferences of gnome.

How I reproduce the problem:
- update seahorse ;-)
- exit gnome
- restart gnome (so far, no problem)
- start balsa
- write a message and sign it, the password is cached
- stop balsa
- exit gnome

If I've a look in .gnome2/session, I've now this entry:
5,id=11c0a8010f0001127192298019977
5,Program=seahorse
5,CurrentDirectory=/home/jean-luc
5,CloneCommand=seahorse
5,RestartCommand=seahorse --sm-client-id  
11c0a8010f0001127192298019977 -


- restart gnome, I've now the Encryption Key Manager displayed.

When I use the previous version of seahorse, I've not this entry  
created in .gnome2/session



Jose Carlos Garcia Sogo


--
Regards

Jean-Luc


pgpuxHZI8JLS7.pgp
Description: PGP signature