GNOME Bugzilla – Bug 356356
crash in Keyring Manager: select a key
Last modified: 2007-12-28 20:58:46 UTC
Version: 2.16.0 What were you doing when the application crashed? select a key Distribution: Debian testing/unstable Gnome Release: 2.16.0 2006-09-08 (GARNOME) BugBuddy Version: 2.16.0 Memory status: size: 28303360 vsize: 0 resident: 28303360 share: 0 rss: 16932864 rss_rlim: 0 CPU usage: start_time: 1158468381 rtime: 0 utime: 120 stime: 0 cutime:94 cstime: 0 timeout: 26 it_real_value: 0 frequency: 0 Backtrace was generated from '/home/boat/garnome/bin/gnome-keyring-manager' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225831616 (LWP 14553)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72545
Thread 1 (Thread -1225831616 (LWP 14553))
According to simple-dup-finder this is a unique stack trace.
*** Bug 356644 has been marked as a duplicate of this bug. ***
*** Bug 359942 has been marked as a duplicate of this bug. ***
It crashes because 'path' is NULL:
+ Trace 74737
$1 = 0x0 (gdb) p app_path $2 = 0x8234090 "/home/gjc/projects/gnome/gnome-keyring-manager/src/gnome-keyring-manager"
Created attachment 74067 [details] [review] patch
The patch looks fine to me. Please apply it with a ChangeLog entry. Thanks.
*** Bug 366505 has been marked as a duplicate of this bug. ***
*** Bug 355008 has been marked as a duplicate of this bug. ***
*** Bug 373896 has been marked as a duplicate of this bug. ***
*** Bug 379590 has been marked as a duplicate of this bug. ***
*** Bug 379674 has been marked as a duplicate of this bug. ***
*** Bug 379728 has been marked as a duplicate of this bug. ***
*** Bug 381852 has been marked as a duplicate of this bug. ***
*** Bug 393603 has been marked as a duplicate of this bug. ***
*** Bug 390789 has been marked as a duplicate of this bug. ***
*** Bug 399791 has been marked as a duplicate of this bug. ***
*** Bug 415294 has been marked as a duplicate of this bug. ***
*** Bug 416071 has been marked as a duplicate of this bug. ***
*** Bug 416379 has been marked as a duplicate of this bug. ***
*** Bug 416587 has been marked as a duplicate of this bug. ***
*** Bug 447813 has been marked as a duplicate of this bug. ***