Bug 438522 – crash in About GNOME: viewing

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 438522 - crash in About GNOME: viewing


Summary:	crash in About GNOME: viewing


Status:	RESOLVED DUPLICATE of bug 432093

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-05-15 06:51 UTC by mtakahashi
Modified:	2007-05-15 13:33 UTC

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

Description mtakahashi 2007-05-15 06:51:06 UTC

Version: 2.18.0

What were you doing when the application crashed?
viewing "about gnome"


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.3155.fc7 #1 PREEMPT Tue May 15 10:41:23 JST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Fedora

Memory status: size: 58298368 vsize: 58298368 resident: 19148800 share: 10698752 rss: 19148800 rss_rlim: 4294967295
CPU usage: start_time: 1179211788 rtime: 56 utime: 53 stime: 3 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 -1208694336 (LWP 10465)]
(no debugging symbols found)
0x00d4780e in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 134235

Thread 1 (Thread -1208694336 (LWP 10465))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 pthread_mutex_lock
from /lib/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
#0 __waitpid_nocancel
from /lib/libpthread.so.0



----------- .xsession-errors (13 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
ウィンドウ・マネージャの警告: 0x160bcb4 () で指定したウィンドウ 0x4d の WM_TRANSIENT_FOR が間違っています
(gnome-about:10465): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu Sans Bold Not-Rotated 0'
--------------------------------------------------

Comment 1 palfrey 2007-05-15 13:33:14 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 ***