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 544723 - seahorse crashed with SIGSEGV in g_timeout_dispatch() when trying sync with keyserver
seahorse crashed with SIGSEGV in g_timeout_dispatch() when trying sync with k...
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
2.24.x
Other Linux
: High critical
: 2.22.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
: 574750 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-07-25 16:42 UTC by Pedro Fragoso
Modified: 2010-01-26 20:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Pedro Fragoso 2008-07-25 16:42:22 UTC
This bug was open on https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/251876

"When I attempt to Sync keys with a keyserv in Intrepid, it causes a segmentation fault 100% of the time.

I added a new key via the app, then went to Remote > Sync and Publish Keys... everything here is default. When I click "Sync" in the resulting dialog it simply crashes immediately.

When running this from the terminal, it reports only the Segmentation Fault, no additional info or interesting output (only other output is "** Message: init gpgme version 1.1.6" which is unrelated.)

I am also surprised this application doesn't have apport integration... I was under the impression that all apps in main had this useful integration... I wish this report could be more helpful, but for now, this is all the info I have."

seahorse 2.23.5

Stacktrace:
 #0  0x0808252a in ?? ()
 #1  0x08069793 in ?? ()
 #2  0x08078401 in ?? ()
 #3  0xb77e2ec6 in g_timeout_dispatch (source=0x9505a38, callback=0x9441e38,
     user_data=0x956d0d8) at /build/buildd/glib2.0-2.17.4/glib/gmain.c:3527
 No locals.
 #4  0xb77e27a1 in IA__g_main_context_dispatch (context=0x8e9c760)
     at /build/buildd/glib2.0-2.17.4/glib/gmain.c:2068
 No locals.
 #5  0xb77e5e43 in g_main_context_iterate (context=0x8e9c760, block=1,
     dispatch=1, self=0x8eb0198)
     at /build/buildd/glib2.0-2.17.4/glib/gmain.c:2701
        max_priority = 0
        timeout = 0
        some_ready = 1
        nfds = 9
        allocated_nfds = <value optimized out>
        fds = (GPollFD *) 0x9509a00
        __PRETTY_FUNCTION__ = "g_main_context_iterate"
 #6  0xb77e6362 in IA__g_main_loop_run (loop=0x90256f8)
     at /build/buildd/glib2.0-2.17.4/glib/gmain.c:2924
        self = (GThread *) 0x8eb0198
        __PRETTY_FUNCTION__ = "IA__g_main_loop_run"
 #7  0xb7b567c9 in IA__gtk_main ()
     at /build/buildd/gtk+2.0-2.13.5/gtk/gtkmain.c:1172
        tmp_list = (GList *) 0x805a0b0
        functions = (GList *) 0x0
        init = (GtkInitFunction *) 0x80c09d0
        loop = (GMainLoop *) 0x90256f8
 #8  0x0805a2aa in ?? ()
 #9  0xb7661685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #10 0x0805a0d1 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_timeout_dispatch (source=0x9505a38, callback=0x9441e38,
 IA__g_main_context_dispatch (context=0x8e9c760)
ThreadStacktrace:
 .
 Thread 2 (process 30950):
 #0  0xb7f2b424 in __kernel_vsyscall ()
 #1  0xb7721de7 in poll () from /lib/tls/i686/cmov/libc.so.6
 #2  0xb7272872 in __libc_res_nsend () from /lib/tls/i686/cmov/libresolv.so.2
 #3  0xb7270f79 in __libc_res_nquery () from /lib/tls/i686/cmov/libresolv.so.2
 #4  0xb7271390 in __libc_res_nquerydomain ()
   from /lib/tls/i686/cmov/libresolv.so.2
 #5  0xb7271575 in __libc_res_nsearch () from /lib/tls/i686/cmov/libresolv.so.2
 #6  0xb58907e4 in _nss_dns_gethostbyname3_r ()
    from /lib/tls/i686/cmov/libnss_dns.so.2
 #7  0xb5890a8b in _nss_dns_gethostbyname2_r ()
    from /lib/tls/i686/cmov/libnss_dns.so.2
 #8  0xb7746612 in gethostbyname2_r@@GLIBC_2.1.2 ()
    from /lib/tls/i686/cmov/libc.so.6
 #9  0xb770ff9f in gaih_inet () from /lib/tls/i686/cmov/libc.so.6
 #10 0xb7711f4c in getaddrinfo () from /lib/tls/i686/cmov/libc.so.6
 #11 0xb7e400ff in ?? () from /usr/lib/libsoup-2.4.so.1
 #12 0xb780d34f in g_thread_create_proxy (data=0x96d5230)
     at /build/buildd/glib2.0-2.17.4/glib/gthread.c:635
        __PRETTY_FUNCTION__ = "g_thread_create_proxy"
 #13 0xb72974ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 #14 0xb772c64e in clone () from /lib/tls/i686/cmov/libc.so.6
 .
 Thread 1 (process 30890):
 #0  0x0808252a in ?? ()
 #1  0x08069793 in ?? ()
 #2  0x08078401 in ?? ()
 #3  0xb77e2ec6 in g_timeout_dispatch (source=0x9505a38, callback=0x9441e38,
     user_data=0x956d0d8) at /build/buildd/glib2.0-2.17.4/glib/gmain.c:3527
 No locals.
 #4  0xb77e27a1 in IA__g_main_context_dispatch (context=0x8e9c760)
     at /build/buildd/glib2.0-2.17.4/glib/gmain.c:2068
 No locals.
 #5  0xb77e5e43 in g_main_context_iterate (context=0x8e9c760, block=1,
     dispatch=1, self=0x8eb0198)
     at /build/buildd/glib2.0-2.17.4/glib/gmain.c:2701
        max_priority = 0
        timeout = 0
        some_ready = 1
        nfds = 9
        allocated_nfds = <value optimized out>
        fds = (GPollFD *) 0x9509a00
        __PRETTY_FUNCTION__ = "g_main_context_iterate"
 #6  0xb77e6362 in IA__g_main_loop_run (loop=0x90256f8)
     at /build/buildd/glib2.0-2.17.4/glib/gmain.c:2924
        self = (GThread *) 0x8eb0198
        __PRETTY_FUNCTION__ = "IA__g_main_loop_run"
 #7  0xb7b567c9 in IA__gtk_main ()
     at /build/buildd/gtk+2.0-2.13.5/gtk/gtkmain.c:1172
        tmp_list = (GList *) 0x805a0b0
        functions = (GList *) 0x0
        init = (GtkInitFunction *) 0x80c09d0
        loop = (GMainLoop *) 0x90256f8
 #8  0x0805a2aa in ?? ()
 #9  0xb7661685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #10 0x0805a0d1 in ?? ()
Comment 1 Stef Walter 2008-07-25 17:14:39 UTC
Thanks for taking the time to report this bug.

Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. In particular it seems there are no seahorse debug symbols installed. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Pedro Fragoso 2008-07-25 21:04:25 UTC
Here's a new backtrace:

Program received signal SIGSEGV, Segmentation fault.

Thread 3070101248 (LWP 6764)

  • #0 seahorse_pgp_source_export
    at seahorse-pgp-source.c line 1035
  • #1 seahorse_source_export_raw
    at seahorse-source.c line 318
  • #2 start_transfer
    at seahorse-transfer-operation.c line 230
  • #3 g_timeout_dispatch
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 3527
  • #4 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 2068
  • #5 g_main_context_iterate
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 2701
  • #6 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 2924
  • #7 IA__gtk_main
    at /build/buildd/gtk+2.0-2.13.5/gtk/gtkmain.c line 1172
  • #8 main
    at main.c line 89

Thread 1 (Thread 0xb6fe0700 (LWP 6764))

  • #0 seahorse_pgp_source_export
    at seahorse-pgp-source.c line 1035
  • #1 seahorse_source_export_raw
    at seahorse-source.c line 318
  • #2 start_transfer
    at seahorse-transfer-operation.c line 230
  • #3 g_timeout_dispatch
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 3527
  • #4 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 2068
  • #5 g_main_context_iterate
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 2701
  • #6 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.17.4/glib/gmain.c line 2924
  • #7 IA__gtk_main
    at /build/buildd/gtk+2.0-2.13.5/gtk/gtkmain.c line 1172
  • #8 main
    at main.c line 89


Comment 3 Stef Walter 2008-09-14 13:45:38 UTC
Is this now fixed in trunk (soon to become 2.24.0)? I believe we're now initializing threading properly, which should help things. 
Comment 4 Pedro Fragoso 2008-10-23 19:34:14 UTC
This still occurs on 2.24.x

Here's a new backtrace

[Thread debugging using libthread_db enabled]
[New Thread 0xb7058700 (LWP 28078)]
[New Thread 0xb617bb90 (LWP 28090)]

Program received signal SIGABRT, Aborted.

Comment 5 Adam Schreiber 2009-02-27 16:20:39 UTC
Does this still happen in 2.25.x and can you remember which keyserver this was occuring with?
Comment 6 palfrey 2009-03-11 13:43:08 UTC
*** Bug 574750 has been marked as a duplicate of this bug. ***
Comment 7 palfrey 2009-03-11 13:44:13 UTC
Not sure how helpful this is, but the user who reported bug 574750 (a duplicate of this) said:

"The problem occurs when trying to synchronize SSH keys with PGP key servers (or
a combination of both key types). (Of course you can't put SSH keys on PGP key
servers but seahorse should probably test the condition and show an error
message if it's false)"
Comment 8 ulikoehler 2009-03-11 13:56:19 UTC
Seahorse crashes only when using ldap://keyserver.pgp.com, it works with hkp://pgp.mit.edu:11371. (I will test it with other LDAP key servers in a few minutes)
My system:
I'm using OpenSuSE 11.1 x64 (up-to-date) and Seahorse 2.24.1 from the GNOME:Unstable repository. The nautilus, lang, applet and gedit Seahorse packages are installed.
Comment 9 Akhil Laddha 2009-12-11 06:08:38 UTC
Ping, if crash doesn't appear in later versions (2.26.x or 2.28.x), we should close the bug, thanks.
Comment 10 Tobias Mueller 2010-01-26 20:11:33 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!