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 697895 - seahorse-tool / Nautilus integration broken
seahorse-tool / Nautilus integration broken
Status: RESOLVED DUPLICATE of bug 698081
Product: seahorse
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
: 707667 709682 (view as bug list)
Depends on:
Blocks: 325803
 
 
Reported: 2013-04-12 16:27 UTC by ftkw
Modified: 2013-11-23 15:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Add correct flag for reaping the progress child (1.15 KB, patch)
2013-08-16 17:27 UTC, Stef Walter
none Details | Review

Description ftkw 2013-04-12 16:27:34 UTC
Seahorse versions tested: 3.6.3-0ubuntu1 and 3.7.91-0ubuntu1~raring1
Distribution: Ubuntu 13.04 raring ringtail

Using 'seahorse-tool' or Nautilus context menu to encrypt, sign, decrypt or verify a file does not work. The gLib-WARNING is always the same.

$ seahorse-tool -s test.txt 

[Key selection window pops up, i select a key, click OK, window disappears.]

(seahorse-tool:11136): 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 Andy 2013-05-23 10:25:36 UTC
I can confirm, and I got the same GLib-Warning.

Somebody also posted this as a question on Ask Ubuntu: http://askubuntu.com/questions/288982/updating-quantal-12-10-to-raring-13-04-broke-seahorse-nautilus
Comment 2 Larry Tate 2013-06-20 14:41:35 UTC
I can confirm this too under 13.04.
Comment 3 Stef Walter 2013-06-21 14:37:37 UTC
Hmmm, looks like glib has changed its behavior.

See: https://bugzilla.gnome.org/show_bug.cgi?id=698081

Will try to get a test case.
Comment 4 spi 2013-07-10 14:39:08 UTC
Have the same issue in 13.04.

Very often I even can't open seahorse. I then get following error 

GLib-GIO-CRITICAL **: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "DescribeAll" with signature "" on interface "org.gtk.Actions" doesn't exist
Comment 5 Stef Walter 2013-07-12 11:10:04 UTC
(In reply to comment #4)
> Have the same issue in 13.04.
> 
> Very often I even can't open seahorse. I then get following error 
> 
> GLib-GIO-CRITICAL **: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod:
> Method "DescribeAll" with signature "" on interface "org.gtk.Actions" doesn't
> exist

Sounds like an Ubuntu bug to me. Have you reported it in Launchpad?
Comment 6 spi 2013-07-12 12:42:47 UTC
(In reply to comment #5)
> Sounds like an Ubuntu bug to me. Have you reported it in Launchpad?

Yes, there's a bug report here https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1154049.
Comment 7 Jérémy Bobbio 2013-07-27 09:07:56 UTC
(In reply to comment #3)
> Hmmm, looks like glib has changed its behavior.
> 
> See: https://bugzilla.gnome.org/show_bug.cgi?id=698081
> 
> Will try to get a test case.

Any progress on making a test case? #698081 is marked as solved but
seahorse-nautilus is still broken with current glib HEAD according to my
tests.
Comment 8 Philipp Gampe 2013-08-01 10:43:12 UTC
Some bug in fedora: https://bugzilla.redhat.com/show_bug.cgi?id=981580
Comment 9 Stef Walter 2013-08-08 15:09:16 UTC
Ryan Lortie, told me commit in Glib was reverted here: bug #698081

*** This bug has been marked as a duplicate of bug 698081 ***
Comment 10 Stef Walter 2013-08-16 17:27:17 UTC
Created attachment 251918 [details] [review]
Add correct flag for reaping the progress child

This fixes the WARNING about ECHILD that comes from some versions
of glib. The WARNING was removed in later versions of glib, but this
is also a good fix.
Comment 11 Stef Walter 2013-10-10 16:55:00 UTC
*** Bug 709682 has been marked as a duplicate of this bug. ***
Comment 12 Michael Catanzaro 2013-11-23 15:42:09 UTC
*** Bug 707667 has been marked as a duplicate of this bug. ***