Bug 463661 – crash in About GNOME: using pidgin & firefox. ...

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 463661 - crash in About GNOME: using pidgin & firefox. ...


Summary:	crash in About GNOME: using pidgin & firefox. ...


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-08-05 14:34 UTC by zdynew
Modified:	2007-09-02 11:31 UTC

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

Description zdynew 2007-08-05 14:34:55 UTC

Version: 2.18.3

What were you doing when the application crashed?
using pidgin & firefox.  n sending a mail via Evolution.

btw,i set a CPU speed monitor at the tool bar.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 72957952 vsize: 72957952 resident: 24629248 share: 17051648 rss: 24629248 rss_rlim: 4294967295
CPU usage: start_time: 1186324299 rtime: 181 utime: 171 stime: 10 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 -1209071904 (LWP 4333)]
(no debugging symbols found)
0x00802402 in __kernel_vsyscall ()

+ Trace 152965

Thread 1 (Thread -1209071904 (LWP 4333))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libpangoft2-1.0.so.0
#5 pango_fc_font_get_glyph
from /usr/lib/libpangoft2-1.0.so.0
#6 ??
from /usr/lib/pango/1.6.0/modules/pango-hangul-fc.so
#7 ??
from /usr/lib/pango/1.6.0/modules/pango-hangul-fc.so
#8 ??
from /usr/lib/libpango-1.0.so.0
#9 pango_shape
from /usr/lib/libpango-1.0.so.0
#10 ??
from /usr/lib/libpango-1.0.so.0
#11 ??
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_layout_get_pixel_extents
from /usr/lib/libpango-1.0.so.0
#15 pango_layout_get_pixel_size
from /usr/lib/libpango-1.0.so.0
#16 ??
from /usr/lib/libgnomecanvas-2.so.0
#17 g_object_set_valist
from /lib/libgobject-2.0.so.0
#18 gnome_canvas_item_set_valist
from /usr/lib/libgnomecanvas-2.so.0
#19 gnome_canvas_item_set
from /usr/lib/libgnomecanvas-2.so.0
#20 _start
#0 __kernel_vsyscall



----------- .xsession-errors (11 sec old) ---------------------
(evolution:4265): evolution-mail-WARNING **: unable to open /home/Backy/.evolution/mail/config/gtkrc-mail-fonts
(evolution:4265): evolution-mail-WARNING **: unable to open /home/Backy/.evolution/mail/config/gtkrc-mail-fonts
(evolution:4265): evolution-mail-WARNING **: unable to open /home/Backy/.evolution/mail/config/gtkrc-mail-fonts
(evolution:4265): evolution-mail-WARNING **: unable to open /home/Backy/.evolution/mail/config/gtkrc-mail-fonts
(evolution:4265): evolution-mail-WARNING **: unable to open /home/Backy/.evolution/mail/config/gtkrc-mail-fonts
** (evolution:4265): WARNING **: aspell error: No word lists can be found for the language "zh_CN".
(gnome-about:4333): Pango-WARNING **: shape engine failure, expect ugly output. the offending font is 'DejaVu LGC Sans Bold Not-Rotated 0'
--------------------------------------------------

Comment 1 Vincent Untz 2007-09-02 11:31:29 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 ***