GNOME Bugzilla – Bug 454511
crash in About GNOME: I selected Desktop -> Ab...
Last modified: 2007-07-07 12:07:16 UTC
Version: 2.18.2 What were you doing when the application crashed? I selected Desktop -> About Gnome I was watching the messages and I started to list peoples names who Gnome is brought to you by and it crashed. :/ Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-686 #1 SMP Wed Apr 18 09:55:10 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 21159936 vsize: 21159936 resident: 11366400 share: 8118272 rss: 11366400 rss_rlim: 4294967295 CPU usage: start_time: 1183798851 rtime: 17 utime: 13 stime: 4 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 -1224476992 (LWP 18429)] (no debugging symbols found) 0xb7dcdaee in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 146294
Thread 1 (Thread -1224476992 (LWP 18429))
----------- .xsession-errors --------------------- ** (gnome-cups-icon:3236): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3236): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3236): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3236): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3236): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3236): WARNING **: IPP request failed with status 1280 (gnome-about:18429): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Bitstream Vera Sans Bold Not-Rotated 0' Failed to read a valid object file image from memory. --------------------------------------------------
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 ***