After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 707667 - GPG file encryption with Seahorse is broken in GNOME 3.8
GPG file encryption with Seahorse is broken in GNOME 3.8
Status: RESOLVED DUPLICATE of bug 697895
Product: seahorse-plugins
Classification: Applications
Component: General
3.8.x
Other Linux
: Normal major
: ---
Assigned To: seahorse-plugins-maint
seahorse-plugins-maint
Depends on:
Blocks:
 
 
Reported: 2013-09-07 02:35 UTC by Jean-François Fortin Tam
Modified: 2013-11-23 15:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-François Fortin Tam 2013-09-07 02:35:37 UTC 
Encrypting files to one of my GPG recipients does not work. If I run Nautilus from a terminal, I see the following output:


EXEC: seahorse-tool --encrypt 'file:///home/jeff/foo.pdf'

(seahorse-tool:28878): GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly.
Comment 1 Jean-François Fortin Tam 2013-09-07 02:45:21 UTC 
Actually, this has nothing to do with nautilus. If you run the seahorse-tool --encrypt command above in the terminal, you get the exact same output, 
it is therefore impossible to encrypt with Seahorse...
Comment 2 Michael Catanzaro 2013-11-23 15:42:09 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 697895 ***