![]() Registered Member ![]()
|
when I try to reset the kontact/kmail to default settings the kontact manual http://docs.kde.org/stable/de/kdepim/kmail/clean-start-after-a-failed-migration.html tells me how it should be done.
BUT IT DOES NOT WORK AS EXPLAINED
Be honest folks. Nobody uses kontact anymore, because it's not working, isn't it? |
![]() Registered Member ![]()
|
It works fine here, and ever did. And I'm using the Akonadified version since it was released in 2011. To your problem: What does not work as explained? What did you do? What problem do you have now? The output you posted show that neither mysql nor akonadi are running, so you successfully completed step 1 in that tutorial you mentioned.
So now carry on with step 2. |
![]() Registered Member ![]()
|
sorry,
![]() ~/.local/share/akonadi ~/.config/akonadi and in ~/.kde/share/config/ and not /.kde4/share/config/ as written ( at least for Kubuntu 14.04) I deleted everything that starts with akonadi. then
everything not in root because I don't see the necessity. And akonadi/mysql gives me the following Output
|
![]() Registered Member ![]()
|
Well, it _is_ .kde4 here on openSUSE. .kde is exclusively used for KDE3 here to make them co-installable... ![]() But you're right, it should be mentioned that this could also be .kde depending on your distribution. Please file a bug report. The main problems I see in your output (I hope I didn't overlook something obvious) are these:
Not sure if those can make the Akonadi server crash, but anyway. The first one is baloo crashing, maybe the problem lies there. Sounds similar to this: https://bugs.kde.org/show_bug.cgi?id=336287 (also reported by a Kubuntu user). The possible "fix" from that bug report will be included in 4.13.3, but that's to be released next week, and it might take even longer until Ubuntu provides updated packages. Akonadi should work fine when started fresh though. It works fine here on a fresh KUbuntu 14.04 installation in a VM. Try to remove ~/.local/share/baloo, maybe the search index is corrupted. You could try to remove the file /usr/share/akonadi/agents/akonadibalooindexingagent.desktop (that's the path on openSUSE, I hope it's the same on Ubuntu), so that baloo's PIM indexer is not started. Does Akonadi start then? Oh, and of course make sure that you have all updates installed. If you install updates, better log out and in again, so that there's no mixture of versions running. Another thing to try is to create a new user. If Akonadi starts fine there, it's some user specific issue. If it doesn't work there either, it's a system-wide issue. Might help to pinpoint the problem. If it's user-specific, deleting KMail's configuration might help as well. For some reasons that's not mentioned in the docs you refer to. ~/.kde/share/config/kmail2rc, ~/.kde/share/apps/kmail2(PS: this one is of course not relevant to your problem, as you cannot even start Akonadi) Hope that helps! |
![]() Registered Member ![]()
|
Thanks so far, wolfi323.
With the exception of creating a new user I tried all your advices you gave me in the last post. I guess, I have to add some more input which might be the cause of the problem but which seemed to me not so important on first sight. After having executed the steps to put kmail to default settings http://docs.kde.org/stable/de/kdepim/kmail/clean-start-after-a-failed-migration.html I observe that everytime when I start the akonadi server a mail-import process continues. This, I guess, has s.th. to do with the interruption of the kmail-import-wizard https://userbase.kde.org/Kmail/Import_Options process which I did due to the fact it was importing from ~/.thunderbird/x1y2y3.default/Mail/Local Folders/Outlook-Import.sbd/local a local mail folder which was already imported before in Kmail. But that does not change the fact that setting Kmail to default must set KMail to default, no matter which process was initiated before, I think. If there is an external ( not within Kmail) process like the import-wizard programmed by Laurant Montel kmail or akonadi might not have anything to do with the original problem, I'm afraid. I hope you are able to decrypt my descriptions... |
![]() Registered Member ![]()
|
No. It's not KMail that's not starting, it's Akonadi. It's normal that some migration processes run when starting it the first time. That's unrelated to that mail import you mention. If you removed ~/.config/akonadi/, ~/.local/share/akonadi/ and ~/.kde/share/config/akonadi*, Akonadi should be set back to default.
Well, you did restore Akonadi to default, and you cannot start Akonadi. That's not directly related to KMail. Please try with a new user. If it doesn't work there either, you have some installation problem. |
![]() Registered Member ![]()
|
In the old user account the akonadi server is started
but it still shows mails in KMail. What I do not understand, what execatly do I have to reproduce in a new user account? Same situation? Import everything from thunderbird and then interrupting the import sequence? Sorry to ask. |
![]() Registered Member ![]()
|
So, what is your problem now?
No. That was just to find out if it would work at all. But if it works now with your normal account, there's no need to do that. Or am I misunderstanding something here now? |
![]() Registered Member ![]()
|
I had to interrupt Kmail-import-wizard, written by Laurant Montel, with which I imported local mail as well as imap mails from Thunderbird.
Since then I want to set kontact to default settings to repeat the import process cleanly. |
![]() Registered Member ![]()
|
imap mails? Those are stored on the server, no need for importing anything. Configure an IMAP account, and they should be there.
Well, just run the import again. You can select a folder where to import the mails to. If you want to get rid of the already imported mails, just delete them. Normally the local maildir resource stores the mail in ~/.local/share/local-mail/ , so remove that to completely start clean. |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell