Bug 435072 – crash in Evolution: closing evolution

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 435072 - crash in Evolution: closing evolution


Summary:	crash in Evolution: closing evolution


Status:	RESOLVED DUPLICATE of bug 334966

Product:	evolution
Classification:	Applications
Component:	general
Version:	unspecified
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:	2007-05-02 01:47 UTC by thanate
Modified:	2007-05-21 13:10 UTC

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

Description thanate 2007-05-02 01:47:12 UTC

Version: 2.12.x

What were you doing when the application crashed?
closing evolution


Distribution: Debian lenny/sid
Gnome Release: 2.18.1 2007-04-29 (GARNOME)
BugBuddy Version: 2.18.1

System: Linux 2.6.21.1 #1 PREEMPT Fri Apr 27 18:37:44 MST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 103743488 vsize: 103743488 resident: 26718208 share: 17862656 rss: 26718208 rss_rlim: 4294967295
CPU usage: start_time: 1178070351 rtime: 255 utime: 241 stime: 14 cutime:43 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/home/boat/garnome/bin/evolution-2.12'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233279296 (LWP 4282)]
[New Thread -1294972016 (LWP 4294)]
[New Thread -1286165616 (LWP 4293)]
[New Thread -1277772912 (LWP 4292)]
[New Thread -1250223216 (LWP 4290)]
[New Thread -1268884592 (LWP 4289)]
[New Thread -1241789552 (LWP 4285)]
0xb7f3f410 in __kernel_vsyscall ()

+ Trace 131803

Thread 1 (Thread -1233279296 (LWP 4282))

#0 __kernel_vsyscall
#1 ??
from /lib/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 <signal handler called>
#4 e_shell_window_set_title
at e-shell-window.c line 1266
#5 impl_ShellView_setTitle
at e-shell-view.c line 48
#6 _ORBIT_skel_small_GNOME_Evolution_ShellView_setTitle
at Evolution-common.c line 24
#7 ORBit_c_stub_invoke
at poa.c line 2630
#8 GNOME_Evolution_ShellView_setTitle
at Evolution-stubs.c line 27
#9 e_component_view_set_title
at e-component-view.c line 136
#10 view_changed_timeout
at mail-component.c line 582
#11 g_timeout_dispatch
at gmain.c line 3488
#12 IA__g_main_context_dispatch
at gmain.c line 2061
#13 g_main_context_iterate
at gmain.c line 2694
#14 IA__g_main_loop_run
at gmain.c line 2898
#15 bonobo_main
at bonobo-main.c line 311
#16 main
at main.c line 592
#0 __kernel_vsyscall



----------- .xsession-errors (61 sec old) ---------------------
***MEMORY-WARNING***: gconftool-2[4204]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this pro
CalDAV Eplugin starting up ...
** (evolution-2.12:4207): DEBUG: mailto URL command: evolution-2.12 %s
** (evolution-2.12:4207): DEBUG: mailto URL program: evolution-2.12
Loading Spamassasin as the default junk plugin
report junk?? Misplaced Test?
report junk?? For Your Eyes Only
***MEMORY-WARNING***: firefox-bin[4262]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this pro
CalDAV Eplugin starting up ...
** (evolution-2.12:4282): DEBUG: mailto URL command: evolution-2.12 %s
** (evolution-2.12:4282): DEBUG: mailto URL program: evolution-2.12
--------------------------------------------------

Comment 1 André Klapper 2007-05-21 13:10:24 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 334966 ***