Bug 445697 – crash in About GNOME: Not sure, I had just sta...

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 445697 - crash in About GNOME: Not sure, I had just sta...


Summary:	crash in About GNOME: Not sure, I had just sta...


Status:	RESOLVED DUPLICATE of bug 431990

Product:	gnome-desktop
Classification:	Core
Component:	gnome-about
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Desktop Maintainers
QA Contact:	Desktop Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-09 08:01 UTC by bobroff
Modified:	2007-06-09 10:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description bobroff 2007-06-09 08:01:26 UTC

Version: 2.19.3.1

What were you doing when the application crashed?
Not sure, I had just started reading the Gnome 'about' page at gnome.org when the bug reporting tool opened up.


Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.3 2007-06-04 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3207.fc8 #1 SMP Tue Jun 5 01:19:16 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: 39583744 vsize: 39583744 resident: 21204992 share: 16035840 rss: 21204992 rss_rlim: 4294967295
CPU usage: start_time: 1181375917 rtime: 116 utime: 101 stime: 15 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 -1208801568 (LWP 15185)]
(no debugging symbols found)
0x00cd9402 in __kernel_vsyscall ()

+ Trace 139525

Thread 1 (Thread -1208801568 (LWP 15185))

#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_fc_font_create_metrics_for_context
from /usr/lib/libpangoft2-1.0.so.0
#21 ??
from /usr/lib/libpangocairo-1.0.so.0
#22 pango_font_get_metrics
from /usr/lib/libpango-1.0.so.0
#23 pango_layout_line_get_extents
from /usr/lib/libpango-1.0.so.0
#24 ??
from /usr/lib/libpango-1.0.so.0
#25 ??
from /usr/lib/libpango-1.0.so.0
#26 pango_layout_get_pixel_extents
from /usr/lib/libpango-1.0.so.0
#27 pango_layout_get_pixel_size
from /usr/lib/libpango-1.0.so.0
#28 ??
from /usr/lib/libgnomecanvas-2.so.0
#29 g_object_set_valist
from /lib/libgobject-2.0.so.0
#30 g_object_set
from /lib/libgobject-2.0.so.0
#31 _start
#0 __kernel_vsyscall

Comment 1 Jan de Groot 2007-06-09 10:15:49 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 ***