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 359134 - crash in Keyring Manager:
crash in Keyring Manager:
Status: RESOLVED DUPLICATE of bug 355008
Product: gnome-keyring-manager
Classification: Deprecated
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Keyring manager maintainers
Keyring manager maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-02 21:53 UTC by agj
Modified: 2006-10-02 22:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description agj 2006-10-02 21:53:07 UTC 
Version: 2.16.0

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 35586048 vsize: 0 resident: 35586048 share: 0 rss: 14090240 rss_rlim: 0
CPU usage: start_time: 1159825873 rtime: 0 utime: 250 stime: 0 cutime:229 cstime: 0 timeout: 21 it_real_value: 0 frequency: 0

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

(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 -1225636176 (LWP 7488)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74160

Thread 1 (Thread -1225636176 (LWP 7488))

  • #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 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_str_equal
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 






Comment 1


Elijah Newren





          2006-10-02 22:02:19 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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