Bug 518446 – crash in About GNOME:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 518446 - crash in About GNOME:


Summary:	crash in About GNOME:


Status:	RESOLVED DUPLICATE of bug 431990

Product:	gnome-desktop
Classification:	Core
Component:	gnome-about
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Desktop Maintainers
QA Contact:	Desktop Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-24 16:45 UTC by margaret
Modified:	2008-03-07 12:30 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description margaret 2008-02-24 16:45:11 UTC

Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 37273600 vsize: 37273600 resident: 19922944 share: 15056896 rss: 19922944 rss_rlim: 4294967295
CPU usage: start_time: 1203870463 rtime: 1074 utime: 838 stime: 236 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 -1209035040 (LWP 19575)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 190313

Thread 1 (Thread -1209035040 (LWP 19575))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libpangoft2-1.0.so.0
#5 pango_fc_font_get_glyph
from /usr/lib/libpangoft2-1.0.so.0
#6 ??
from /usr/lib/pango/1.6.0/modules/pango-hangul-fc.so
#7 ??
from /usr/lib/pango/1.6.0/modules/pango-hangul-fc.so
#8 ??
from /usr/lib/libpango-1.0.so.0
#9 pango_shape
from /usr/lib/libpango-1.0.so.0
#10 ??
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libpango-1.0.so.0
#12 ??
from /usr/lib/libpango-1.0.so.0
#13 ??
from /usr/lib/libpango-1.0.so.0
#14 pango_layout_get_pixel_extents
from /usr/lib/libpango-1.0.so.0
#15 pango_layout_get_pixel_size
from /usr/lib/libpango-1.0.so.0
#16 ??
from /usr/lib/libgnomecanvas-2.so.0
#17 g_object_set_valist
from /lib/libgobject-2.0.so.0
#18 gnome_canvas_item_set_valist
from /usr/lib/libgnomecanvas-2.so.0
#19 gnome_canvas_item_set
from /usr/lib/libgnomecanvas-2.so.0
#20 _start
#0 __kernel_vsyscall



----------- .xsession-errors (127 sec old) ---------------------
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:19575): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------

Comment 1 Gianluca Borello 2008-03-07 12:30:43 UTC

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 ***