GNOME Bugzilla – Bug 439076
crash in About GNOME: One more time I was trin...
Last modified: 2007-05-17 09:35:47 UTC
Version: 2.18.1 What were you doing when the application crashed? One more time I was tring to read the news on Gnome news.gnome.org when I get teh anomaly report it is not the first time I allready report this problem I was doing the following step in my foresight linux 1.2.2 from system I went to gnome about and when the window on gnome open I choose news to read the news about gnome I acceed the page and the anomaly report after 2mn. I still don't understand why this happen. this is my 6th report on the same problem. Distribution: Unknown Gnome Release: 2.18.1 2007-04-10 (Foresight Linux) BugBuddy Version: 2.18.1 System: Linux 2.6.20.11-1.smp.gcc3.4.x86.i686 #1 SMP Fri May 4 11:27:57 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Foresight Icon Theme: gnome Memory status: size: 31531008 vsize: 31531008 resident: 12218368 share: 8581120 rss: 12218368 rss_rlim: 4294967295 CPU usage: start_time: 1179393427 rtime: 23 utime: 22 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-about' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226021184 (LWP 3199)] (no debugging symbols found) 0xb7f4e410 in ?? ()
+ Trace 134577
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (gnome-about:3199): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Bitstream Vera Sans Bold Not-Rotated 0' /usr/share/bug-buddy/gdb-cmd:2: Error in sourced command file: Previous frame inner to this frame (corrupt stack?) --------------------------------------------------
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 431990 ***