Bug 277711 - Migration "fails to fail" if KWallet prompt cancelled
Summary: Migration "fails to fail" if KWallet prompt cancelled
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: 4.6
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-13 17:12 UTC by Szczepan Hołyszewski
Modified: 2017-01-07 22:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Szczepan Hołyszewski 2011-07-13 17:12:32 UTC 
Version:           2.1.1 (using KDE 4.6.4) 
OS:                Linux

The KMail migration shows KWallet prompt which is WRONG WRONG WRONG (and will be reported as a separate bug)

... but this report is about the fact that migration "fails to fail" when the KWallet prompt is cancelled. Every stage of migration shows a green tick mark and no warnings or errors are displayed, but of course messages and folders are not migrated.


Reproducible: Didn't try

Steps to Reproduce:
Start kmail2 for the first time (of course must have used kmail1 before so there is something to migrate).

Actual Results:  
Migrator appears to succeed after KWallet prompt is cancelled, but no messages or folders are migrated.

Expected Results:  
The migrator should fail with clear error message when the KWallet prompt is cancelled.

OS: Linux (i686) release 2.6.39-ARCH
Compiler: gcc
Comment 1 Szczepan Hołyszewski 2012-04-04 22:52:36 UTC 
At this point probably everyone who were to suffer from this bug suffered from it and got over it...
Comment 2 Denis Kurz 2016-09-24 20:31:15 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:02:46 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.