Bug 358754 - Another mailer was found on system. Do you want to import data from it?
Summary: Another mailer was found on system. Do you want to import data from it?
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-29 23:01 UTC by kokotokosoko
Modified: 2018-02-01 09:51 UTC (History)
2 users (show)

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 kokotokosoko 2016-01-29 23:01:45 UTC 
Great to know. But *WHICH* other mailer? It wouldn't hurt to say, would it?


Reproducible: Always
Comment 1 Laurent Montel 2016-01-30 08:09:42 UTC 
screenshot please ?
Comment 2 kokotokosoko 2016-02-04 14:01:04 UTC 
(In reply to Laurent Montel from comment #1)
> screenshot please ?

Sorry can't do as it's already been installed and fully configured. If I get to do a plasma install on a VM I'll try to take a snap, but I'm not planning to at the moment.

What about grep -Ri "Another mailer was found" /path/to/sources/*
Comment 3 Denis Kurz 2017-06-23 21:19:19 UTC 
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x (which version was it reported for anyway?). Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 4 Denis Kurz 2018-02-01 09:51:00 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.