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 168570 - gnome-keyring-manager crashes when right-clicking an entry
gnome-keyring-manager crashes when right-clicking an entry
Status: RESOLVED DUPLICATE of bug 153355
Product: gnome-keyring-manager
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Keyring manager maintainers
Keyring manager maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-26 08:19 UTC by Dave Rosky
Modified: 2005-02-26 15:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dave Rosky 2005-02-26 08:19:05 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 when right-clicking an entry
Bugzilla-Product: gnome-keyring-manager
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:

program crashes when right-clicking an entry in the keyring list

Steps to reproduce the crash:
1. open gnome-keyring-manager
2. right-click on an entry (session entry in my case)
3. 

Expected Results:

Not sure.  If there is no action for right-clicking, the program
should at least not crash.

How often does this happen?

3 out of 3 tries.

Additional Information:



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 -1208326464 (LWP 5584)]
(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)...(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)...(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)...(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)...(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)...(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)...(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)...(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)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x001387a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -1208326464 (LWP 5584))

  • #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
    from /usr/lib/libgobject-2.0.so.0
  • #5 gkm_keyring_manager_new
  • #6 gkm_keyring_manager_new
  • #7 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gdk_event_get_graphics_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-26 03:19 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-keyring-manager".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was d_rosky@nccn.net.
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-02-26 15:11:44 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

Matches the stack trace in bug 161660, which has been marked as a duplicate of
153355.

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