Bug 364923 – crash in Evolution: Recovering a lost email

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 364923 - crash in Evolution: Recovering a lost email


Summary:	crash in Evolution: Recovering a lost email


Status:	RESOLVED DUPLICATE of bug 357939

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-25 07:48 UTC by andykitchen
Modified:	2006-10-25 13:19 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description andykitchen 2006-10-25 07:48:05 UTC

What were you doing when the application crashed?
Recovering a lost email


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 225624064 vsize: 0 resident: 225624064 share: 0 rss: 32911360 rss_rlim: 0
CPU usage: start_time: 1161762440 rtime: 0 utime: 170 stime: 0 cutime:160 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232910672 (LWP 21233)]
[New Thread -1380688992 (LWP 21249)]
[New Thread -1372296288 (LWP 21247)]
[New Thread -1333490784 (LWP 21244)]
[New Thread -1296045152 (LWP 21243)]
[New Thread -1287652448 (LWP 21239)]
[New Thread -1276793952 (LWP 21238)]
[New Thread -1268364384 (LWP 21236)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78188

Thread 8 (Thread -1268364384 (LWP 21236))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 __assert_fail
from /lib/tls/i686/cmov/libc.so.6
#8 cairo_ft_scaled_font_unlock_face
from /usr/lib/libcairo.so.2
#9 cairo_ft_scaled_font_lock_face
from /usr/lib/libcairo.so.2
#10 pango_cairo_fc_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#11 pango_fc_font_lock_face
from /usr/lib/libpangoft2-1.0.so.0
#12 script_engine_init
from /usr/lib/pango/1.5.0/modules/pango-basic-fc.so
#13 pango_coverage_new
from /usr/lib/libpango-1.0.so.0
#14 pango_shape
from /usr/lib/libpango-1.0.so.0
#15 pango_layout_set_width
from /usr/lib/libpango-1.0.so.0
#16 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#17 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#18 pango_layout_iter_get_char_extents
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 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#22 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#23 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#24 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#25 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#26 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#27 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#28 rsvg_handle_render_cairo_sub
from /usr/lib/librsvg-2.so.2
#29 rsvg_handle_get_pixbuf_sub
from /usr/lib/librsvg-2.so.2
#30 rsvg_handle_get_pixbuf
from /usr/lib/librsvg-2.so.2
#31 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
#32 ??
#33 ??

Comment 1 Karsten Bräckelmann 2006-10-25 13:19:12 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 357939 ***