Bug 697990 - Evo-MAPI folder tree switches between expandable and non-expandable
Summary: Evo-MAPI folder tree switches between expandable and non-expandable
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-mapi
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-19 20:31 UTC by Charles Bovy
Modified: 2011-04-22 16:45 UTC (History)
2 users (show)

Fixed In Version: evolution-mapi-3.0.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-22 16:45:23 UTC
Type: ---


Attachments (Terms of Use)
Non-expandable folder tree (93.16 KB, image/png)
2011-04-19 20:31 UTC, Charles Bovy
no flags Details
Expandle folder tree (83.48 KB, image/png)
2011-04-19 20:31 UTC, Charles Bovy
no flags Details

Description Charles Bovy 2011-04-19 20:31:12 UTC
Created attachment 493282 [details]
Non-expandable folder tree

Description of problem:

During use of Evo with MAPI account, the expand possibility of the main folder switches to on and off. 


Version-Release number of selected component (if applicable):

evolution-3.0.0-1.fc15.i686
evolution-data-server-3.0.0-1.fc15.i686
evolution-mapi-3.0.0-1.fc15.i686


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:

See attached screenshot and check left pane, folder hierarchy.

Expected results:

Just an expandable folder tree all times.

Additional info:

When Evo-MAPI is switching between expandable and non-expandable folder tree, the following message appears on console (for each toggle a different foldername):

(evolution:10048): camel-mapi-provider-WARNING **: camel_mapi_folder_new: cannot find 'Mailbox - Username/Folder1' in known folders

Comment 1 Charles Bovy 2011-04-19 20:31:44 UTC
Created attachment 493283 [details]
Expandle folder tree

Comment 2 Milan Crha 2011-04-20 07:16:48 UTC
Thanks for a bug report. It seems like it failed to fetch folder names from your MAPI server for some reason, and then clears all folders, treating them as removed. Could you run evolution like this:
   $ MAPI_DEBUG=10 evolution &>log.txt
and then get values surrounding GetHierarchyTable lines, please? The log will be pretty large and contains private information, thus do not attach it here whole.

I suppose you are using samba4 and openchange provided in F15, right? Which are those for you, please?

Comment 3 Charles Bovy 2011-04-20 09:17:27 UTC
I'm using:

* samba4-libs-4.0.0-25.alpha11.fc15.i686
* openchange-0.9-15.fc15.i686

I'll try to get the value arround GetHierarchyTable.

Comment 4 Milan Crha 2011-04-20 11:47:31 UTC
Thanks, I received the log and it seems fine, unfortunately. I'm afraid that I would create a test package for you, with some specialized debugging, but before that, to avoid local cache issues (like breakage), could you disable the MAPI account, close evolution and e-calendar-factory with e-addressbook-factory, maybe also evolution-alarm-notify process, then remove (or rather move away):
   ~/.local/share/evolution/mail/mapi/*
   ~/.local/share/evolution/mapi*
then run evolution, edit the account, authenticate it, confirm with OK and enable that MAPI account, please? Maybe it'll require evolution's restart in some phases, like at the end, I'm not 100% sure.

Comment 5 Milan Crha 2011-04-20 14:36:42 UTC
We spoke on IRC and did few tests and realized that I broke it with this commit:
http://git.gnome.org/browse/evolution-mapi/commit/?h=gnome-3-0&id=154b7325ec4c76fe185016b5d33360588bc902f5

I'll investigate further and try to find some fix.

Comment 6 Milan Crha 2011-04-22 14:45:39 UTC
So I installed F15, in a hope to get as closest environment as you, and tried to reproduce this, but no luck. It may mean that this is rather something about the server, in a sense that that yours is behaving differently from that mine. We may try to debug this together further.

Comment 7 Milan Crha 2011-04-22 16:45:23 UTC
Thanks for a help with this, we finally found where I did a mistake, and fixed it in [1]. This change will be also included in the next release (should be on the next Wednesday) of evolution-mapi 3.0.1.

[1] http://git.gnome.org/browse/evolution-mapi/commit/?id=5e1854b


Note You need to log in before you can comment on or make changes to this bug.