Bug 329120 - Migration Agent displays a totally uninformative dialog requiring user input.
Summary: Migration Agent displays a totally uninformative dialog requiring user input.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Migration (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-22 12:47 UTC by jem
Modified: 2017-01-07 21:25 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 jem 2013-12-22 12:47:42 UTC
After 'emerge world' on my Gentoo PC a dialog popped up automatically asking me to take action. The problem is that the dialog gives no indication of what the problem is, the severity of the problem or even what piece of software is involved. The dialog pops out of the blue, it is not associated with any context.
The window title says: "Conflict Resolution - Migration Agent". The text in the dialog: "Two updates conflict with each other. Please choose which update(s) to apply."
"Modification time: Changed contact: 00:00:00, Conflicting Contact 2013-12-22 11:23:40".
Three buttons: "Take left one, Take right one, Keep both".
That's all. This does not tell the user anything and is potentially very scary. What conflict? The Middle East conflict? What's a contact in this context, and why does it look like a timestamp?

Reproducible: Always

Steps to Reproduce:
1. Install Gentoo Linux with KDE.
2. Update the system to the latest versions, this time including KDE 4.12.
3. Restart the system.
Actual Results:  
At next boot gaze at a mysterious dialog asking you to take action on something you haven't got the faintest clue of.

Expected Results:  
The software should either fix the problem automatically or, if it can't be resolved automatically, explain what the problem is, what entities are involved, and what the implications of each of the given alternatives are.
Comment 1 Denis Kurz 2016-09-24 20:42:38 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 2 Denis Kurz 2017-01-07 21:25:42 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.