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 496220 - crash in About GNOME: browsing the internet
crash in About GNOME: browsing the internet
Status: RESOLVED DUPLICATE of bug 431990
Product: gnome-desktop
Classification: Core
Component: gnome-about
2.18.x
Other All
: High critical
: ---
Assigned To: Desktop Maintainers
Desktop Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-12 19:40 UTC by g.bossenbroek
Modified: 2007-11-12 20:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description g.bossenbroek 2007-11-12 19:40:51 UTC
Version: 2.18.3

What were you doing when the application crashed?
browsing the internet


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

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 44515328 vsize: 44515328 resident: 26701824 share: 15511552 rss: 26701824 rss_rlim: 4294967295
CPU usage: start_time: 1194894785 rtime: 2486 utime: 1999 stime: 487 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 -1208666400 (LWP 3053)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208666400 (LWP 3053))

  • #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 (7 sec old) ---------------------
(gnome-about:3053): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Tahoma Bold Not-Rotated 0'
(gnome-about:3053): GnomeCanvas-WARNING **: Failed to set cell text from markup due to error parsing markup: Fout in regel 1 teken 13: Ongeldige UTF-8-geëncodeerde tekst
--- Hash table keys for warning below:
--> file:///home/Gerald
(nautilus:3371): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(gnome-about:3053): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Tahoma Bold Not-Rotated 0'
(gnome-about:3053): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Tahoma Bold Not-Rotated 0'
(gnome-about:3053): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'Tahoma Bold Not-Rotated 0'
--------------------------------------------------
Comment 1 Vincent Untz 2007-11-12 20:44:16 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 ***