GNOME Bugzilla – Bug 384393
crash in Help: Trying to find out why r...
Last modified: 2007-05-13 15:19:19 UTC
Version: 2.16.0 What were you doing when the application crashed? Trying to find out why recent updates killed my ability to access the Internet. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- ** (eggcups:2330): WARNING **: IPP request failed with status 1030 You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. error getting update info: Cannot find a valid baseurl for repo: extras (yelp:2781): Yelp-WARNING **: An error occurred getting the gconf value '/apps/yelp/variable_font' (yelp:2781): Yelp-WARNING **: An error occurred getting the gconf value '/apps/yelp/fixed_font' ** (bug-buddy:2802): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 142536704 vsize: 0 resident: 142536704 share: 0 rss: 41893888 rss_rlim: 0 CPU usage: start_time: 1165765190 rtime: 0 utime: 186 stime: 0 cutime:172 cstime: 0 timeout: 14 it_real_value: 0 frequency: 1 Backtrace was generated from '/usr/bin/yelp' (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 -1208330528 (LWP 2781)] [New Thread -1275929712 (LWP 2791)] [New Thread -1265439856 (LWP 2790)] [New Thread -1254950000 (LWP 2789)] [New Thread -1244460144 (LWP 2788)] [New Thread -1210430576 (LWP 2787)] (no debugging symbols found) 0x00e13402 in __kernel_vsyscall ()
+ Trace 93055
Thread 1 (Thread -1208330528 (LWP 2781))
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 437966 has been marked as a duplicate of this bug. ***