GNOME Bugzilla – Bug 430047
crash in About GNOME: Has simply closed a brow...
Last modified: 2007-09-28 09:11:38 UTC
Version: 2.18.1 What were you doing when the application crashed? Has simply closed a browser. Distribution: Unknown Gnome Release: 2.18.1 2007-04-15 (FreeBSD GNOME Project) BugBuddy Version: 2.18.1 System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #15: Wed Mar 7 19:48:15 NOVT 2007 root@void.network:/usr/src/sys/i386/compile/VOID i386 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: glass-icons Memory status: size: 30480 vsize: 30480 resident: 16324 share: 27231268 rss: 16324 rss_rlim: 4081 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133 Backtrace was generated from '/usr/local/bin/gnome-about' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100209] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100209] 0x28faae4d in wait4 () from /lib/libc.so.6
+ Trace 128018
----------- .xsession-errors --------------------- (epiphany:42851): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany:42851): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany:42851): libgnomevfs-WARNING **: Failed to create service browser: Bad state (gnome-about:42849): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Bitstream Vera Sans Bold Not-Rotated 0' warning: Unable to get location for thread creation breakpoint: generic error /usr/local/share/gnome/bug-buddy/gdb-cmd:2: Error in sourced command file: Previous frame inner to this frame (corrupt stack?) --------------------------------------------------
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!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 478245 has been marked as a duplicate of this bug. ***