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 443368 - crash in About GNOME: rien je lisais
crash in About GNOME: rien je lisais
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-06-02 23:25 UTC by jump221281
Modified: 2007-06-03 17:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jump221281 2007-06-02 23:25:53 UTC 
Version: 2.18.0

What were you doing when the application crashed?
rien je lisais


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

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 38289408 vsize: 38289408 resident: 12591104 share: 7938048 rss: 12591104 rss_rlim: 4294967295
CPU usage: start_time: 1180826657 rtime: 88 utime: 68 stime: 20 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 -1208994080 (LWP 2553)]
(no debugging symbols found)
0x006b7402 in __kernel_vsyscall ()

+ Trace 137639

Thread 1 (Thread -1208994080 (LWP 2553))

  • #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 ---------------------
localuser:Pier-Luc being added to access control list
SESSION_MANAGER=local/fedora.intrajumpinc.com:/tmp/.ICE-unix/2256
(gnome-about:2553): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------
Comment 1 palfrey 2007-06-02 23:48:58 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Pedro Villavicencio 2007-06-03 17:21:44 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 432093 ***