sometimes fails to start on edgy - 100% hang on 'scanning folders in "Exchange server..."'

Bug #60899 reported by John Leach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-exchange (Ubuntu)
Invalid
Undecided
Bill Gjestvang

Bug Description

It doesn't actually freeze, it just never leaves this state. It's generating no network traffic and uses 100% CPU (evolution-exchange-storage process)

2 entries in taskbar, bothing saying:
'scanning folders in "Exchange server 10.0.0.254" (...)'

My password is saved in the gnome password manager.

This happens on start-up once in a while. Strace and Ltrace show *no* output for that thread.

gdb gives me:
gdb /usr/lib/evolution/2.8/evolution-exchange-storage 5027
<snip>
(gdb) bt
#0 0xb6e9a3d7 in ?? () from /usr/lib/libglib-2.0.so.0
#1 0xb6ed50af in g_str_equal () from /usr/lib/libglib-2.0.so.0
#2 0xb6eac1e6 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
#3 0xb72ef4a1 in exchange_account_is_save_password () from /usr/lib/libexchange-storage-1.2.so.2
#4 0xb6f7c199 in g_cclosure_marshal_VOID__POINTER () from /usr/lib/libgobject-2.0.so.0
#5 0xb6f6f83b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#6 0xb6f7fc43 in g_signal_chain_from_overridden () from /usr/lib/libgobject-2.0.so.0
#7 0xb6f81167 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#8 0xb6f81329 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#9 0xb72f8bce in exchange_hierarchy_new_folder () from /usr/lib/libexchange-storage-1.2.so.2
#10 0xb72f7d87 in exchange_hierarchy_webdav_parse_folder () from /usr/lib/libexchange-storage-1.2.so.2
#11 0xb72f7eb3 in exchange_hierarchy_webdav_parse_folder () from /usr/lib/libexchange-storage-1.2.so.2
#12 0xb72f7eb3 in exchange_hierarchy_webdav_parse_folder () from /usr/lib/libexchange-storage-1.2.so.2
#13 0xb72f7eb3 in exchange_hierarchy_webdav_parse_folder () from /usr/lib/libexchange-storage-1.2.so.2
#14 0xb72f7eb3 in exchange_hierarchy_webdav_parse_folder () from /usr/lib/libexchange-storage-1.2.so.2
#15 0xb72f7eb3 in exchange_hierarchy_webdav_parse_folder () from /usr/lib/libexchange-storage-1.2.so.2
#16 0xb72f863c in exchange_hierarchy_scan_subtree () from /usr/lib/libexchange-storage-1.2.so.2
#17 0xb72f1f3d in exchange_account_rescan_tree () from /usr/lib/libexchange-storage-1.2.so.2
#18 0x0805ea43 in mail_stub_exchange_new ()
#19 0x08063b63 in mail_stub_get_type ()
#20 0xb6ee1d1d in g_io_channel_unix_get_fd () from /usr/lib/libglib-2.0.so.0
#21 0xb6eb8872 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb6ebb84f in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#23 0xb6ebbbf9 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#24 0xb718ca23 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#25 0x0805b9a3 in main ()

Revision history for this message
John Leach (johnleach) wrote :

This is with package version 2.8.0-0ubuntu1 in Edgy. Launchpad doesn't seem (to me) to make that clear anywhere.

Revision history for this message
Said Babayev (phoenix49) wrote :

Same here. I just waited for 10 minutes and it finished "scanning" folder.

Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

Is anyone still seeing this in current releases (feisty or gutsy)? Answers either way would be helpful. Feisty was much improved for this sort of evolution stuff, in my experience.

Changed in evolution-exchange:
assignee: nobody → bill-launchpad
status: New → Incomplete
Revision history for this message
Bill Gjestvang (bgjestvang) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. (Namely, whether it still happens in more recent releases.) Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in evolution-exchange:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.