Bug 410750 – crash in Evolution: Recreating my groupwise ...

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 410750 - crash in Evolution: Recreating my groupwise ...


Summary:	crash in Evolution: Recreating my groupwise ...


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.12.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	422072 (view as bug list)
Depends on:
Blocks:

Reported:	2007-02-22 10:48 UTC by aloonstra
Modified:	2008-11-16 19:49 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Attachments
gdb backtrace of segfaulting evolution (10.27 KB, text/plain) 2007-07-10 04:15 UTC, Brian Derr	Details

Description aloonstra 2007-02-22 10:48:01 UTC

What were you doing when the application crashed?
Recreating my groupwise account, aftre wizard instant crash


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

Memory status: size: 99221504 vsize: 0 resident: 99221504 share: 0 rss: 25104384 rss_rlim: 0
CPU usage: start_time: 1172141184 rtime: 0 utime: 234 stime: 0 cutime:215 cstime: 0 timeout: 19 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232910672 (LWP 24487)]
[New Thread -1248998496 (LWP 24603)]
[New Thread -1257391200 (LWP 24601)]
[New Thread -1294193760 (LWP 24599)]
[New Thread -1285801056 (LWP 24598)]
[New Thread -1277408352 (LWP 24499)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 112854

Thread 1 (Thread -1232910672 (LWP 24487))

#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 segv_redirect
at main.c line 426
#4 <signal handler called>
#5 strchr
from /lib/tls/i686/cmov/libc.so.6
#6 camel_url_new_with_base
at camel-url.c line 70
#7 camel_url_new
at camel-url.c line 288
#8 enable_folder_tree
at mail-component.c line 667
#9 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 emfb_search_search_activated
at em-folder-browser.c line 1055
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 emit_search_activated
at e-search-bar.c line 161
#21 idle_activate_hack
at e-search-bar.c line 941
#22 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#24 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_iteration
from /usr/lib/libglib-2.0.so.0
#26 ep_msg_send
at e-passwords.c line 186
#27 e_passwords_get_password
at e-passwords.c line 1053
#28 add_addressbook_sources
at camel-gw-listener.c line 479
#29 account_added
at camel-gw-listener.c line 860
#30 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#31 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#35 gconf_accounts_changed
at e-account-list.c line 175
#36 gconf_client_get_type
from /usr/lib/libgconf-2.so.4
#37 gconf_listeners_notify
from /usr/lib/libgconf-2.so.4
#38 gconf_client_value_changed
from /usr/lib/libgconf-2.so.4
#39 gconf_client_value_changed
from /usr/lib/libgconf-2.so.4
#40 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#41 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#42 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#43 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#44 bonobo_main
from /usr/lib/libbonobo-2.so.0
#45 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-04-12 19:28:36 UTC

*** Bug 422072 has been marked as a duplicate of this bug. ***

Comment 2 Sebastien Bacher 2007-06-20 09:44:01 UTC

https://bugs.launchpad.net/evolution/+bug/119636 has a similar backtrace happening on GNOME 2.19.2

Comment 3 Sebastien Bacher 2007-06-20 09:44:42 UTC

Ubuntu bug description:

"Evolution will crash on startup if the inbox has sub folders and these subfolders were visible (Inbox expanded) when evolution was last closed.
If Inbox was not expanded then Evolution starts up fine.

deleting the et-expanded and folder-tree-expand-state XML files resolves the issue."

Comment 4 Brian Derr 2007-07-10 04:15:45 UTC

Created attachment 91526 [details]
gdb backtrace of segfaulting evolution

Comment 5 Brian Derr 2007-07-10 04:18:52 UTC

Sebastien, what similarities are you seeing between this bug report and the ubuntu report 119636. It doesn't seem very similar to me in that this report seems to allow evolution to start up and crashes when making changes to groupwise, whereas the ubuntu bug doesn't allow evolution to start at all.

Comment 6 Pedro Villavicencio 2007-09-13 20:38:19 UTC

Seems to be fixed according to the comments on :
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/119636

Comment 7 Alec Wright 2007-09-14 16:42:41 UTC

Yep it seems to be fixed. Can someone change the status to RESOLVED please? (This is why I prefer launchpad, because there, anyone can change a bug's status!)

Comment 8 Matthew Barnes 2008-03-11 00:33:30 UTC

Bumping version to a stable release.

Comment 9 André Klapper 2008-11-16 19:49:25 UTC

(In reply to comment #7)
> Yep it seems to be fixed. Can someone change the status to RESOLVED please?
> (This is why I prefer launchpad, because there, anyone can change a bug's
> status!)
>