Bug 249771 - Regression: 'Local Folders' and Kolab resource do not synchronize anymore
Summary: Regression: 'Local Folders' and Kolab resource do not synchronize anymore
Status: CLOSED FIXED
Alias: None
Product: KMail Mobile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-01 19:02 UTC by Sabine Faure
Modified: 2010-10-02 00:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sabine Faure 2010-09-01 19:02:18 UTC
Version:           unspecified (using Devel) 
OS:                Linux

'Local Folders' and the Kolab resource are not synchronizing anymore.
Up til last Friday when launching a sync I was seeing a message, an update pourcentage and a folder name but now nothing happens.

Reproducible: Always

Steps to Reproduce:
- Launch Kmail-mobile on the N900
- Connect Akonadi console to the N900 from another computer
- Open the 'Actions tab'
- Click on 'Home'
- And then on 'Synchronize all emails'

Actual Results:  
There is no status displayed in Akonadi console next the 'Local Folders' and Kolab resource.
Nothing happens when a sync is launched whereas it worked fine last week when I last tested it.

Expected Results:  
Both Local Folders and the Kolab resource should have a 'Ready' status.
They should display a message, an update pourcentage and a folder name (folder being updated) while synchronizing.

Launching a synchronization from Akonadi console does not work either.

N900, 4:4.5~20100901.1170517-1maemo1.1170522
Comment 1 Sabine Faure 2010-09-01 20:15:37 UTC
I've just retested that now and it seems to be fixed with the new revision: both Local folders and Kolab resource now display 'Ready' and after launching a sync 'syncing collection, pourcentage and folder name'

I'll reopen if needed.

N900,4:4.5~20100901.1170574-1maemo1.1170522
Comment 2 Sabine Faure 2010-10-02 00:44:14 UTC
I retested this bug today and I still cannot reproduce it so I am closing it.

N900, 4:4.5~20101001.1181533-1maemo1.1181469