[kmail2] [Bug 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."

Tim Holy holy at pcg.wustl.edu
Mon Jun 9 16:09:23 BST 2014


https://bugs.kde.org/show_bug.cgi?id=246027

--- Comment #22 from Tim Holy <holy at pcg.wustl.edu> ---
I did some random sequence of deleting all akonadi resources (multiple times),
starting kontact (multiple times), manually specifying a resource at
~/.local/share/local-mail, and restarting the mysql server. At a certain point
I got to a stage where there was just one "Local Folders" resource listed in
Akonadi Control. At the time is was listed as "syncing," so I waited until that
finished and said Ready. From that point forward I have a better sense for my
specific steps and the consequences were.

I started Akonadi Control (with kontact not running) and then restarted the
akonadi server. This produced two resources labeled "Local Folders" with status
Ready. Restarting a second time, without launching kontact, kept it at 2 (it
did not go to 3).

Then, I tried starting kontact. For the first time, it did not crash, and I
could even send a mail to myself. (yay!) However, there are two "Local Folders"
in my list of mailboxes. One with a blue folder icon is empty. The other with
some other icon (a computer?) seems to have my mail. "outbox", "sent-mail", and
"trash" are not in their usual places near the top, instead they are sorted in
alphabetical order, and they have standard folder-icons rather than the custom
icons for things like "inbox", "outbox", etc. The new message I sent ended up
inside the "new" (empty) Local Folders sent-mail folder, not my old one. I
opened the properties on it, and unchecked "Act on new/unread mail in this
folder". Then I sent another test message. It still ended up in the new
(undesired) resource. I haven't yet dared to download my email, there will be
quite a lot waiting and I am concerned it will target the wrong set of folders.

I quit kontact, went back to Akonadi Control, and deleted the resource that was
named something like ~/.local/share/akonadi_resource_6 or something. (Not my
".local/share/local-mail" one.) Then I restarted mysql to see if it would
created a 2nd resource again. This time it did what it had done at the
beginning:  it gave me a startup error, and clicking on the link showed a file
with lines like
    InnoDB: Unable to lock .libdata1, error:11
    InnoDB: Check that you do not already have another mysqld process
    InnoDB: using the same InnoDB data or log files.

I'm going to try logging out and logging back in again, so I'll hit submit
here.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list