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 436680 - crash in About GNOME: nothing.
crash in About GNOME: nothing.
Status: RESOLVED DUPLICATE of bug 432093
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-05-07 19:24 UTC by raul.saura
Modified: 2007-05-08 01:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description raul.saura 2007-05-07 19:24:54 UTC
Version: 2.18.0

What were you doing when the application crashed?
nothing.


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.21-1.3116.fc7 #1 SMP Thu Apr 26 10:36:44 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 37408768 vsize: 37408768 resident: 13365248 share: 8564736 rss: 13365248 rss_rlim: 4294967295
CPU usage: start_time: 1177574127 rtime: 89 utime: 44 stime: 45 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 -1208825408 (LWP 13420)]
(no debugging symbols found)
0x008b5402 in __kernel_vsyscall ()

Thread 1 (Thread -1208825408 (LWP 13420))

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


----------- .xsession-errors (14 sec old) ---------------------
smartd (pid 2293) is running...
smartd
smartd (pid 2293) is running...
yum-updatesd
yum-updatesd (pid 2144) is running...
yum-updatesd
yum-updatesd (pid 2144) is running...
** (yelp:13409): WARNING **: failure: no device event controller found.
** (yelp:13409): WARNING **: failure: no device event controller found.
(gnome-about:13420): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-05-08 01:14:28 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 432093 ***