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 434163 - crash in About GNOME: I was reading the web pa...
crash in About GNOME: I was reading the web pa...
Status: RESOLVED DUPLICATE of bug 431255
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-04-28 17:22 UTC by aauzi
Modified: 2007-04-28 17:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description aauzi 2007-04-28 17:22:20 UTC 
Version: 2.18.0

What were you doing when the application crashed?
I was reading the web page the "News" link linked me to.


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.5.fc7xen #1 SMP Thu Mar 22 13:51:40 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 302804992 vsize: 302804992 resident: 16556032 share: 9883648 rss: 16556032 rss_rlim: 18446744073709551615
CPU usage: start_time: 1177780795 rtime: 9 utime: 5 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 46912661568288 (LWP 14322)]
(no debugging symbols found)
0x00002aaaaf63d805 in waitpid () from /lib64/libpthread.so.0

+ Trace 131125

Thread 1 (Thread 46912661568288 (LWP 14322))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #4 ??
    from /usr/lib64/libcairo.so.2
  • #5 ??
    from /usr/lib64/libcairo.so.2
  • #6 ??
    from /usr/lib64/libcairo.so.2
  • #7 cairo_scaled_font_text_extents
    from /usr/lib64/libcairo.so.2
  • #8 ??
    from /usr/lib64/libpangocairo-1.0.so.0
  • #9 ??
    from /usr/lib64/libpangocairo-1.0.so.0
  • #10 ??
    from /usr/lib64/libpangocairo-1.0.so.0
  • #11 ??
    from /usr/lib64/libpango-1.0.so.0
  • #12 pango_shape
    from /usr/lib64/libpango-1.0.so.0
  • #13 ??
    from /usr/lib64/libpango-1.0.so.0
  • #14 ??
    from /usr/lib64/libpango-1.0.so.0
  • #15 ??
    from /usr/lib64/libpango-1.0.so.0
  • #16 ??
    from /usr/lib64/libpango-1.0.so.0
  • #17 pango_layout_get_pixel_extents
    from /usr/lib64/libpango-1.0.so.0
  • #18 pango_layout_get_pixel_size
    from /usr/lib64/libpango-1.0.so.0
  • #19 ??
    from /usr/lib64/libgnomecanvas-2.so.0
  • #20 g_object_set_valist
    from /lib64/libgobject-2.0.so.0
  • #21 gnome_canvas_item_set_valist
    from /usr/lib64/libgnomecanvas-2.so.0
  • #22 gnome_canvas_item_set
    from /usr/lib64/libgnomecanvas-2.so.0
  • #23 _start
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (8 sec old) ---------------------
See http://www.realvnc.com for information on VNC.
Sat Apr 28 18:21:21 2007
 CConn:       connected to host aauzi-home.dyndns.org port 5901
Sat Apr 28 18:21:22 2007
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
Sat Apr 28 18:21:31 2007
 TXImage:     Using default colormap and visual, TrueColor, depth 24.
 CConn:       Using pixel format depth 6 (8bpp) rgb222
 CConn:       Using ZRLE encoding
(gnome-about:14322): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------
Comment 1 palfrey 2007-04-28 17:59:37 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 431255 ***