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 404034 - Searching for remote key...
Searching for remote key...
Status: RESOLVED DUPLICATE of bug 528150
Product: seahorse
Classification: Applications
Component: general
0.9.7
Other All
: Normal major
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
: 402624 405496 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-03 19:14 UTC by steve10k
Modified: 2008-05-05 01:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description steve10k 2007-02-03 19:14:17 UTC
What were you doing when the application crashed?
searching for remote key using the string:
58403026387EE263

This was reported as a missing signing key (Wine distribution key) 
by Synaptic.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 55664640 vsize: 0 resident: 55664640 share: 0 rss: 14499840 rss_rlim: 0
CPU usage: start_time: 1170529896 rtime: 0 utime: 145 stime: 0 cutime:135 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/seahorse'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226525008 (LWP 22329)]
[New Thread -1252664416 (LWP 22347)]
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1252664416 (LWP 22347))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 pthread_mutex_lock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 IA__g_source_attach
    at gmain.c line 907
  • #6 soup_add_idle
    from /usr/lib/libsoup-2.2.so.8
  • #7 soup_dns_lookup_resolve_async
    from /usr/lib/libsoup-2.2.so.8
  • #8 g_thread_create_proxy
    at gthread.c line 553
  • #9 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #10 clone
    from /lib/tls/i686/cmov/libc.so.6

Comment 1 Adam Schreiber 2007-02-03 19:28:12 UTC
Could you indicate which keyserver you were trying to find the key on and if your internet was connected at the time?
Comment 2 André Klapper 2007-02-06 01:19:59 UTC
*** Bug 402624 has been marked as a duplicate of this bug. ***
Comment 3 Timm 2007-02-06 07:51:52 UTC
Hello,

I had the same bug.

My main keyserver is keyserver.ubuntu.com

But for the search the following where searched:
hkp://pgp.mit.edu:11371
ldap://keyserver.pgp.com
hkp://keyserver.ubuntu.com

I hope this helps.
Comment 4 Adam Schreiber 2007-02-07 03:27:56 UTC
I changed my key servers to match Timm's and was not able to replicate the bug with HEAD.  Could one of you please download either HEAD or 0.9.10, compile it with --enable-debug and paste the terminal output if you can still replicate the bug?
Comment 5 Timm 2007-02-07 19:41:28 UTC
Ok, I will install Seahorse 0.9.10.

Maybe I can reproduce the Bug, or maybe their was also something else involved.
Comment 6 Timm 2007-02-07 19:50:49 UTC
So, was not to hard to crash seahorse again, just opening multiply Search Windows and then Close them as they did not show results (probably they were actually fetching).

See Bug 405496

And here is the console output:
timm@timm-desktop:~/Desktop/deb-dev$ seahorse
** Message: init gpgme version 1.1.2

** (seahorse:10208): WARNING **: DNS-SD initialization failed: Daemon not running

** (seahorse:10208): CRITICAL **: seahorse_multi_operation_take: assertion `SEAHORSE_OPERATION (op) != SEAHORSE_OPERATION (mop)' failed

** (seahorse:10208): CRITICAL **: seahorse_multi_operation_take: assertion `SEAHORSE_OPERATION (op) != SEAHORSE_OPERATION (mop)' failed

(seahorse:10208): GLib-GObject-WARNING **: invalid cast from `SeahorsePGPKey' to `SeahorseOperation'

(seahorse:10208): GLib-GObject-WARNING **: invalid cast from `SeahorsePGPKey' to `SeahorseOperation'

(seahorse:10208): GLib-GObject-WARNING **: invalid cast from `SeahorsePGPKey' to `SeahorseOperation'

(seahorse:10208): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

** (seahorse:10208): CRITICAL **: seahorse_multi_operation_take: assertion `SEAHORSE_OPERATION (op) != SEAHORSE_OPERATION (mop)' failed

(seahorse:10208): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `SeahorseOperation'

(seahorse:10208): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'

(seahorse:10208): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(seahorse:10208): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'

(seahorse:10208): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(seahorse:10208): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `SeahorseOperation'

(seahorse:10208): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject'

(seahorse:10208): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(seahorse:10208): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `SeahorseOperation'

** (bug-buddy:10236): WARNING **: Couldn't load icon for Decrypt File

** (bug-buddy:10236): WARNING **: Couldn't load icon for Epiphany Web Bookmarks

** (bug-buddy:10236): WARNING **: Couldn't load icon for Import Key

** (bug-buddy:10236): WARNING **: Couldn't load icon for Open Folder

** (bug-buddy:10236): WARNING **: Couldn't load icon for Verify Signature
Applications can not close shared connections.  Please fix this in your app.  Ignoring close request and continuing.
Comment 7 Timm 2007-02-13 21:23:13 UTC
Updated to 0.9.91, but still the same error:

#########################
Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 81178624 vsize: 0 resident: 81178624 share: 0 rss: 16277504 rss_rlim: 0
CPU usage: start_time: 1171401869 rtime: 0 utime: 246 stime: 0 cutime:211 cstime: 0 timeout: 35 it_real_value: 0 frequency: 1

Backtrace was generated from '/usr/local/bin/seahorse'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226467664 (LWP 16230)]
[New Thread -1266791520 (LWP 16244)]
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1266791520 (LWP 16244))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 IA__g_source_attach
    at gmain.c line 910
  • #5 soup_add_idle
    at soup-misc.c line 442
  • #6 resolver_thread
    at soup-dns.c line 511
  • #7 g_thread_create_proxy
    at gthread.c line 553
  • #8 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #9 clone
    from /lib/tls/i686/cmov/libc.so.6

So if you have any tips, debugging libsoup2, I will do so, and give you better feedback.

This is what I have installed:
timm@timm-desktop:~/Desktop/seahorse/seahorse-0.9.91$ aptitude search libsoup2
i   libsoup2.2-8                    - an HTTP library implementation in C -- Sha
i   libsoup2.2-8-dbgsym             - debug symbols for package libsoup2.2-8    
i   libsoup2.2-dev                  - an HTTP library implementation in C -- Dev
p   libsoup2.2-doc                  - an HTTP library implementation in C -- API
Comment 8 Stef Walter 2007-04-06 15:26:19 UTC
*** Bug 405496 has been marked as a duplicate of this bug. ***
Comment 9 Adam Schreiber 2008-05-05 01:26:53 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 528150 ***