Bug 445816 – crash in About GNOME: reading info about gnome...

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 445816 - crash in About GNOME: reading info about gnome...


Summary:	crash in About GNOME: reading info about gnome...


Status:	RESOLVED DUPLICATE of bug 431990

Product:	gnome-desktop
Classification:	Core
Component:	gnome-about
Version:	2.18.x
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 17:41 UTC by mlinde
Modified:	2007-06-09 17:44 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description mlinde 2007-06-09 17:41:11 UTC

Version: 2.18.0

What were you doing when the application crashed?
reading info about gnome



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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 265842688 vsize: 265842688 resident: 13991936 share: 8052736 rss: 13991936 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181410783 rtime: 38 utime: 34 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 46912496405888 (LWP 7525)]
(no debugging symbols found)
0x0000003b9960d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 139617

Thread 1 (Thread 46912496405888 (LWP 7525))

#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 ---------------------
--> file:///home/mlinde
(nautilus:6866): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--- Hash table keys for warning below:
--> file:///home/mlinde
(nautilus:6874): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--- Hash table keys for warning below:
--> file:///home/mlinde
(nautilus:6892): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(gnome-about:7525): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------

Comment 1 Jan de Groot 2007-06-09 17:44:46 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 ***