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 416379 - crash in Keyring Manager: Absturz bei Erstellen ei...
crash in Keyring Manager: Absturz bei Erstellen ei...
Status: RESOLVED DUPLICATE of bug 356356
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: 2007-03-09 10:00 UTC by sebastian.krause
Modified: 2007-12-28 20:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sebastian.krause 2007-03-09 10:00:45 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Absturz bei Erstellen eines neuen Schlüsselbundes


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

Memory status: size: 55668736 vsize: 0 resident: 55668736 share: 0 rss: 15548416 rss_rlim: 0
CPU usage: start_time: 1173434294 rtime: 0 utime: 155 stime: 0 cutime:144 cstime: 0 timeout: 11 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 -1225722192 (LWP 5018)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 117137

Thread 1 (Thread -1225722192 (LWP 5018))

  • #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 ??
  • #6 ??
  • #7 ??
  • #0 __kernel_vsyscall 






Comment 1


Teppo Turtiainen





          2007-12-28 20:58:12 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 356356 ***