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 493431 - crash in About GNOME: Automatic update
crash in About GNOME: Automatic update
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-04 17:07 UTC by dfwoodhouse
Modified: 2007-11-05 08:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dfwoodhouse 2007-11-04 17:07:27 UTC
Version: 2.18.0

What were you doing when the application crashed?
Automatic update


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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 42643456 vsize: 42643456 resident: 12824576 share: 8212480 rss: 12824576 rss_rlim: 4294967295
CPU usage: start_time: 1194195397 rtime: 9 utime: 8 stime: 1 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
0x00bc9402 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 wait
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 <signal handler called>
  • #3 pthread_mutex_init
    from /lib/i686/nosegneg/libpthread.so.0
  • #4 ??
    from /usr/lib/libcairo.so.2
  • #5 ??
    from /usr/lib/libcairo.so.2
  • #6 ??
    from /usr/lib/libcairo.so.2
  • #7 cairo_scaled_font_text_extents
    from /usr/lib/libcairo.so.2
  • #8 ??
    from /usr/lib/libpangocairo-1.0.so.0
  • #9 ??
    from /usr/lib/libpangocairo-1.0.so.0
  • #10 ??
    from /usr/lib/libpangocairo-1.0.so.0
  • #11 pango_font_get_glyph_extents
    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_shape
    from /usr/lib/libpango-1.0.so.0
  • #15 ??
    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 pango_layout_get_pixel_extents
    from /usr/lib/libpango-1.0.so.0
  • #20 pango_layout_get_pixel_size
    from /usr/lib/libpango-1.0.so.0
  • #21 ??
    from /usr/lib/libgnomecanvas-2.so.0
  • #22 g_object_set_valist
    from /lib/libgobject-2.0.so.0
  • #23 gnome_canvas_item_set_valist
    from /usr/lib/libgnomecanvas-2.so.0
  • #24 gnome_canvas_item_set
    from /usr/lib/libgnomecanvas-2.so.0
  • #25 _start


----------- .xsession-errors ---------------------
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
--------------------------------------------------
Comment 1 Christoph Wolk 2007-11-05 08:59:48 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 ***