Bug 492212 – crash in Email: salvando account

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 492212 - crash in Email: salvando account


Summary:	crash in Email: salvando account


Status:	RESOLVED DUPLICATE of bug 449996

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-01 00:09 UTC by camabami
Modified:	2007-12-04 17:31 UTC

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

Description camabami 2007-11-01 00:09:27 UTC

Version: 2.10

What were you doing when the application crashed?
salvando account


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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 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: 133013504 vsize: 133013504 resident: 56246272 share: 40030208 rss: 56246272 rss_rlim: 4294967295
CPU usage: start_time: 1193875289 rtime: 851 utime: 783 stime: 68 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208625440 (LWP 27170)]
[New Thread -1242387568 (LWP 27195)]
[New Thread -1274258544 (LWP 27194)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174246

Thread 1 (Thread -1208625440 (LWP 27170))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 pango_layout_line_unref
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 g_object_unref
from /lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit
from /lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgtk-x11-2.0.so.0
#38 ??
from /usr/lib/libgnomeui-2.so.0
#39 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_widget_unparent
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgtk-x11-2.0.so.0
#44 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#45 ??
from /lib/libgobject-2.0.so.0
#46 g_closure_invoke
from /lib/libgobject-2.0.so.0
#47 ??
from /lib/libgobject-2.0.so.0
#48 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#49 g_signal_emit
from /lib/libgobject-2.0.so.0
#50 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#51 ??
from /usr/lib/libgtk-x11-2.0.so.0
#52 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#53 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#54 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#55 ??
from /usr/lib/libgtk-x11-2.0.so.0
#56 gtk_container_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#57 ??
from /usr/lib/libgtk-x11-2.0.so.0
#58 ??
from /usr/lib/libgtk-x11-2.0.so.0
#59 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#60 ??
from /lib/libgobject-2.0.so.0
#61 g_closure_invoke
from /lib/libgobject-2.0.so.0
#62 ??
from /lib/libgobject-2.0.so.0
#63 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#64 g_signal_emit
from /lib/libgobject-2.0.so.0
#65 ??
from /usr/lib/libgtk-x11-2.0.so.0
#66 ??
from /usr/lib/libgtk-x11-2.0.so.0
#67 ??
from /usr/lib/libgtk-x11-2.0.so.0
#68 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#69 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#70 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#71 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#72 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#73 g_closure_invoke
from /lib/libgobject-2.0.so.0
#74 ??
from /lib/libgobject-2.0.so.0
#75 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#76 g_signal_emit
from /lib/libgobject-2.0.so.0
#77 gnome_druid_page_finish
from /usr/lib/libgnomeui-2.so.0
#78 ??
from /usr/lib/libgnomeui-2.so.0
#79 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#80 g_closure_invoke
from /lib/libgobject-2.0.so.0
#81 ??
from /lib/libgobject-2.0.so.0
#82 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#83 g_signal_emit
from /lib/libgobject-2.0.so.0
#84 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#85 ??
from /usr/lib/libgtk-x11-2.0.so.0
#86 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#87 ??
from /lib/libgobject-2.0.so.0
#88 g_closure_invoke
from /lib/libgobject-2.0.so.0
#89 ??
from /lib/libgobject-2.0.so.0
#90 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#91 g_signal_emit
from /lib/libgobject-2.0.so.0
#92 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#93 ??
from /usr/lib/libgtk-x11-2.0.so.0
#94 ??
from /usr/lib/libgtk-x11-2.0.so.0
#95 ??
from /lib/libgobject-2.0.so.0
#96 g_closure_invoke
from /lib/libgobject-2.0.so.0
#97 ??
from /lib/libgobject-2.0.so.0
#98 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#99 g_signal_emit
from /lib/libgobject-2.0.so.0
#100 ??
from /usr/lib/libgtk-x11-2.0.so.0
#101 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#102 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#103 ??
from /usr/lib/libgdk-x11-2.0.so.0
#104 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#105 ??
from /lib/libglib-2.0.so.0
#106 g_main_loop_run
from /lib/libglib-2.0.so.0
#107 bonobo_main
from /usr/lib/libbonobo-2.so.0
#108 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/evolution/2.10/libetimezonedialog.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libecal-1.2.so.7" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libnm_glib.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libldap-2.3.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Tobias Mueller 2007-12-04 17:31:06 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 449996 ***