Bug 587539 - seahorse-daemon.desktop should not contain an autostart condition by default
seahorse-daemon.desktop should not contain an autostart condition by default
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: Daemon
2.26.x
Other All
: Normal minor
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
:
: 587632 (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2009-07-01 16:55 UTC by Tasos Latsas
Modified: 2009-07-02 19:43 UTC (History)
2 users (show)

See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Tasos Latsas 2009-07-01 16:55:26 UTC 
Remove the autostart condition :
AutostartCondition=GNOME /apps/seahorse/sharing/sharing_enabled

because nautilus encryption plugin is not working without seahorse-daemon, which has nothing to do about the sharing keys over the network.

Other information:
when trying to encrypt a file via nautilus right click without running the daemon the following pop-up appears: 

No encryption keys were found with which to perform the operation you requested.  The program Passwords and Encryption Keys will now be started so that you may either create a key or import one.
Comment 1 Adam Schreiber 2009-07-02 19:22:29 UTC 
*** Bug 587632 has been marked as a duplicate of this bug. ***
Comment 2 Adam Schreiber 2009-07-02 19:32:10 UTC 
commit 2e2a3d529b62ea39b69b707b6dde7a1425ba7ca4
Author: Adam Schreiber <sadam@gnome.org>
Date:   Thu Jul 2 15:29:25 2009 -0400

    Bug 587539 – seahorse-daemon should autostart by default
    
    Remove the autostart condition on the sharing gconf key.
Comment 3 rom 2009-07-02 19:39:40 UTC 
Do you have a workaround? I didn't find this key in gconf-editor…
Comment 4 Adam Schreiber 2009-07-02 19:43:03 UTC 
It's installed by the schemas file data/seahorse.schemas.in and defaults to FALSE.  If you don't have it, there's a problem with your gconf install or you need to reapply the schemas file.  The key is right where the OP indicated in my gconf tree.
Note You need to log in before you can comment on or make changes to this bug.