GNOME Bugzilla – Bug 145662
Crash when accessing preferences on amd64
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Unknown Package: epiphany Severity: blocker Version: GNOME2.6.1 unspecified Gnome-Distributor: Gentoo Linux Synopsis: Crash when accessing preferences on amd64 Bugzilla-Product: epiphany Bugzilla-Component: Preferences Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Following a major font update (*huge* number of TTF fonts added... around 6000+), the epiphany preferences pulldown will crash any currently running epiphany binary. Steps to reproduce the crash: 1. Open an Epiphany browser. 2. Try to open the preferences dialog box. - Crash will bring you to this "report bug" stuff. 3. Expected Results: It should work! Might not have anything to do with the fonts I've added, but I thought I'd report that anyway... How often does this happen? Every time! Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/epiphany-bin' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (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)...0x0000002a96ae58f2 in waitpid () from /lib/libpthread.so.0
+ Trace 47386
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 13:18 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "epiphany". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was brendan_rankin@earthlink.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Looks like an 'bad' font on your system [Mathematica 3MB font is known to cause this crash], apparently this is fixed in pango cvs, but there is no released pang o version with the fix, yet. *** This bug has been marked as a duplicate of 129741 ***