GNOME Bugzilla – Bug 402745
crash in Font: I just clicked the 'Deta...
Last modified: 2007-06-03 18:34:28 UTC
Version: 2.16.1 What were you doing when the application crashed? I just clicked the 'Details button and it wiped out. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 54673408 vsize: 0 resident: 54673408 share: 0 rss: 13107200 rss_rlim: 0 CPU usage: start_time: 1170230780 rtime: 0 utime: 38 stime: 0 cutime:36 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-font-properties' (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 -1225443024 (LWP 26798)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 106763
Thread 1 (Thread -1225443024 (LWP 26798))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I installed the control center debug package and then repeated the actions that caused the thing to crash, here's the new stack trace: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 54681600 vsize: 0 resident: 54681600 share: 0 rss: 13103104 rss_rlim: 0 CPU usage: start_time: 1170271131 rtime: 0 utime: 40 stime: 0 cutime:38 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-font-properties' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225123536 (LWP 7013)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 106905
Thread 1 (Thread -1225123536 (LWP 7013))
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. *** This bug has been marked as a duplicate of 378338 ***
*** Bug 443414 has been marked as a duplicate of this bug. ***