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 500119 - crash in About GNOME: browsing www.gnomefiles....
crash in About GNOME: browsing www.gnomefiles....
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-28 04:35 UTC by dan.merino
Modified: 2008-01-07 23:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description dan.merino 2007-11-28 04:35:03 UTC 
Version: 2.18.3

What were you doing when the application crashed?
browsing www.gnomefiles.org 	


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.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 307167232 vsize: 307167232 resident: 38928384 share: 28200960 rss: 38928384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1196223364 rtime: 172 utime: 168 stime: 4 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496360256 (LWP 16213)]
(no debugging symbols found)
0x0000003634c0d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 179903

Thread 1 (Thread 46912496360256 (LWP 16213))

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


----------- .xsession-errors ---------------------
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
(gnome-about:16213): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:16213): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:16213): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:16213): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
(gnome-about:16213): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------
Comment 1 Vincent Untz 2008-01-07 23:19:28 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 ***