GNOME Bugzilla – Bug 143488
Crashes on clicking "Preferences" menu item
Last modified: 2004-12-22 21:47:04 UTC
Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251352 From: Gung Ye LIAO <gongyi.liao@msa.hinet.net> Steps to reproduce the crash: 1.cicked the "edit" item on the menubar 2.clicked the "Preference" item in the pop-down menu 3.crash. ... gungye@Gontop:~17:06:52$ gdb /usr/lib/epiphany/epiphany GNU gdb 6.1-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...(no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) run Starting program: /usr/lib/epiphany/epiphany (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)...[Thread debugging using libthread_db enabled] [New Thread 1075058080 (LWP 1621)] [New Thread 1122692016 (LWP 1626)] (epiphany:1621): Gtk-WARNING **: Unable to parse accelerator 'gtk-open' for action 'OpenImage' (epiphany:1621): GLib-GObject-CRITICAL **: file gobject.c: line 1579 (g_object_unref): assertion `G_IS_OBJECT (object)' failed [New Thread 1132092336 (LWP 1627)] [New Thread 1144777648 (LWP 1628)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1075058080 (LWP 1621)] 0x443e0242 in ?? () from /usr/lib/pango/1.4.0/modules/pango-hangul-fc.so Thanx! -- Gung Ye LIAO <gongyi.liao@msa.hinet.net>
Most probably there's a corrupted font in your setup [for example, the Mathematica 3MB font is known to cause this crash].
Most likely you have a bad font installed. (Do you have the mathematica fonts?the Mathematica3mb font has this problem.) Unfortunately, that stack trace is not very useful in determining the exactcause of the crash. Please make sure that the package and the libraries itdepens on were compiled with debugging symbols and not stripped, and see http://bugzilla.gnome.org/getting-traces.cgi for more information about usefulstack traces.