Bug 436169 – crash in About GNOME: leyendo

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 436169 - crash in About GNOME: leyendo


Summary:	crash in About GNOME: leyendo


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-05-05 18:43 UTC by suratla
Modified:	2007-05-08 07:33 UTC

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

Description suratla 2007-05-05 18:43:44 UTC

Version: 2.18.0

What were you doing when the application crashed?
leyendo


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.3116.fc7 #1 SMP Thu Apr 26 10:36:44 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: 39256064 vsize: 39256064 resident: 13557760 share: 8892416 rss: 13557760 rss_rlim: 4294967295
CPU usage: start_time: 1178390546 rtime: 30 utime: 25 stime: 5 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 -1208366656 (LWP 3659)]
(no debugging symbols found)
0x00d42402 in __kernel_vsyscall ()

+ Trace 132593

Thread 1 (Thread -1208366656 (LWP 3659))

#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 ---------------------
open(/dev/video2): No such file or directory
open(/dev/video3): No such file or directory
vid-probe: trying: v4l... 
open(/dev/video0): No such file or directory
open(/dev/video1): No such file or directory
open(/dev/video2): No such file or directory
open(/dev/video3): No such file or directory
DCOP: register 'anonymous-3643' -> number of clients is now 2
DCOP: unregister 'anonymous-3643'
kdeinit: PID 3511 terminated.
kdeinit: PID 3510 terminated.
kdeinit: PID 3500 terminated.
kdeinit: PID 3501 terminated.
(gnome-about:3659): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------

Comment 1 Vincent Untz 2007-05-08 07:33:30 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 ***