GNOME Bugzilla – Bug 336491
seahorse-agent clutters ~/.gnome2
Last modified: 2007-12-11 15:23:00 UTC
Please describe the problem: seahorse-agent leaves the directories it uses to store sockets behind when it exits. This causes ~/.gnome2 to have a lot of seahorse-* directories. Steps to reproduce: 1. start seahorse-agent 2. kill seahorse-agent (stop it, not a literal kill) 3. check ~/.gnome2 (or equivalent) for directories Actual results: seahorse-agent leaves the socket directory behind Expected results: the socket directory should be deleted when seahorse-agent exits Does this happen every time? yes Other information: ubuntu bug filed for this at: https://launchpad.net/malone/bugs/31336
This is a known bug and is being worked on in head. Thanks for the report
Anybody is working on this?
No, I don't think anyone is actively working on this at the moment. If you'd be interested in lending a hand I'd be more than happy to assist you with understanding the code base.
*** Bug 350680 has been marked as a duplicate of this bug. ***
Fixed in seahorse-0-8: * agent/seahorse-agent.c: Fix problem with leaving temp directories in ~/.gnome2/. Fixes #336491 Used GnomeClient to get notification of the session ending.
Strange... I cannot find traces of that changelog in version 1.0 tarball (http://ftp.gnome.org/pub/GNOME/sources/seahorse/1.0/)... And the problem seems to still be here in Debian on version 0.9* (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454929)... however I would have expected to see it fixed, as it seems to have been fixed in version 0.8 if I get it right... A regression maybe ?
(In reply to comment #6) > Strange... I cannot find traces of that changelog in version 1.0 tarball > (http://ftp.gnome.org/pub/GNOME/sources/seahorse/1.0/)... > > And the problem seems to still be here in Debian on version 0.9* > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454929)... however I would > have expected to see it fixed, as it seems to have been fixed in version 0.8 if > I get it right... > > A regression maybe ? > Probably just something which was fixed without a clear mention in changelogs, as it appears to be fixed in version 1.0 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454929#10). Sorry about the noise.