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 163711 - gnome-keyring-manager crashes if to rightclick on an item in it
gnome-keyring-manager crashes if to rightclick on an item in it
Status: RESOLVED DUPLICATE of bug 148126
Product: gnome-keyring-manager
Classification: Deprecated
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Keyring manager maintainers
Keyring manager maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-11 18:59 UTC by Peeter Puusemp
Modified: 2005-02-10 07:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peeter Puusemp 2005-01-11 18:59:12 UTC 
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-keyring-manager
Severity: normal
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome-keyring-manager crashes if to rightclick on an item in it
Bugzilla-Product: gnome-keyring-manager
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
gnome-keyring-manager crashes if to rightclick on an item in it.

Steps to reproduce the crash:
1. Open gnome-keyring-manager
2. Rightclick an existing item in the list
3. 

Expected Results:
gnome-keyring-manager crashes

How often does this happen?
Every time I open the gnome-keyring-manager and then rightclick on the
existing item in the list.

Additional Information:
I use Fedora Core 3 with latest updates.


Debugging Information:

Backtrace was generated from '/usr/bin/gnome-keyring-manager'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread -1208097088 (LWP 7074)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...0x0088e7a2 in
_dl_sysinfo_int80 () from /lib/ld-linux.so.2

+ Trace 54391

Thread 1 (Thread -1208097088 (LWP 7074))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_type_check_instance_cast
    at gtype.c line 3160
  • #5 gkm_keyring_manager_new
  • #6 gkm_keyring_manager_new
  • #7 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #8 g_closure_invoke
    at gclosure.c line 437
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #10 g_signal_emit_valist
    at gsignal.c line 2247
  • #11 g_signal_emit
    at gsignal.c line 2281
  • #12 gtk_widget_event_internal
    at gtkwidget.c line 3564
  • #13 gtk_propagate_event
    at gtkmain.c line 2345
  • #14 gtk_main_do_event
    at gtkmain.c line 1583
  • #15 gdk_event_dispatch
    at gdkevents-x11.c line 2189
  • #16 g_main_context_dispatch
    at gmain.c line 1942
  • #17 g_main_context_iterate
    at gmain.c line 2573
  • #18 g_main_loop_run
    at gmain.c line 2777
  • #19 gtk_main
    at gtkmain.c line 1173
  • #20 main 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-11 13:59 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-keyring-manager".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Elijah Newren 2005-01-11 20:03:27 UTC 
Thanks for the bug report.  This appears to be a unique stack trace, according
to the simple-dup-finder.

Is there any chance you could install the gnome-keyring-manager debuginfo rpm as
well (it appears you already have the ones for glib and gtk installed)?  It'd be
great if we could get debugging information for the gkm_* functions as well.
Comment 2 Peeter Puusemp 2005-01-11 20:25:11 UTC 
Installed the gnome-keyring-manager debuginfo rpm and got this backtrace info:


Backtrace was generated from '/usr/bin/gnome-keyring-manager'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208097088 (LWP 7787)]
0x0088e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

+ Trace 54396

Thread 1 (Thread -1208097088 (LWP 7787))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_type_check_instance_cast
    at gtype.c line 3160
  • #5 keyring_tree_popup_menu
    at gnome-keyring-manager-keyring-manager.c line 1082
  • #6 keyring_tree_button_press_callback
    at gnome-keyring-manager-keyring-manager.c line 1142
  • #7 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #8 g_closure_invoke
    at gclosure.c line 437
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #10 g_signal_emit_valist
    at gsignal.c line 2247
  • #11 g_signal_emit
    at gsignal.c line 2281
  • #12 gtk_widget_event_internal
    at gtkwidget.c line 3564
  • #13 gtk_propagate_event
    at gtkmain.c line 2345
  • #14 gtk_main_do_event
    at gtkmain.c line 1583
  • #15 gdk_event_dispatch
    at gdkevents-x11.c line 2189
  • #16 g_main_context_dispatch
    at gmain.c line 1942
  • #17 g_main_context_iterate
    at gmain.c line 2573
  • #18 g_main_loop_run
    at gmain.c line 2777
  • #19 gtk_main
    at gtkmain.c line 1173
  • #20 main
    at gnome-keyring-manager.c line 276 






Comment 3


Chris Kelso





          2005-02-04 14:56:46 UTC
        



This is a dupe of 148126 and has been resolved.  Sorry I don't have access in
bugzilla to alter status so someone else will have to ;)






Comment 4


Christian Kellner





          2005-02-10 07:44:09 UTC
        




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