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

[Eric via KDE Bugzilla]

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

--- Comment #35 from Eric  ---
After the 73 new packages to install, 1 source package.
It keep telling me that I need to
Package 'libKF5AkonadiPrivate-devel' has source package 'akonadi-server'.
Resolving package dependencies...

The following source package is going to be installed:
  akonadi-server

1 source package to install.

I'm not even sure how my Kmail have been working so far, even if so-so ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Eric via KDE Bugzilla]

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

Eric  changed:

   What|Removed |Added

 CC||eric.v...@msg4.us

--- Comment #34 from Eric  ---
For the past few months, Kmail keep doing that. In fact, since the first day I
gave Kmail a try I've had different problems with it. It's unfriendly and take
up so much storage space !
Anyway, when I start it it keep saying that error message,
I close it, reopen it, and then it kinda work, at least it doesn't repeat the
same error message, it just work badly, like not filtering incoming messages,
or freezing on refreshing an imap account, etc ...
I have 7 main email addresses in 7 imap account, with all the aliases, and all
including local folder are simlinked to a separate drive.

I've zypper kdepim just now, and it says:
Problem: kdepim-15.12.3-18.5.src requires kalarmcal-devel, but this requirement
cannot be provided
So I zypper Kalarmcal and it says:
Problem: kalarmcal-15.12.3-15.1.src requires libKF5AkonadiPrivate-devel >=
1.72.43, but this requirement cannot be provided
So I zypper si libKF5AkonadiPrivate-devel and it says:
The following 73 NEW packages are going to be installed:
  Mesa-libEGL-devel Mesa-libGL-devel boost-devel cmake damageproto-devel
extra-cmake-modules fixesproto-devel gcc gcc-c++ gcc48 gcc48-c++
  glibc-devel kbproto-devel kf5-filesystem libQt5Core-devel libQt5DBus-devel
libQt5Gui-devel libQt5Network-devel libQt5Sql-devel
  libQt5Test-devel libQt5Widgets-devel libQt5Xml-devel libX11-devel
libXau-devel libXdamage-devel libXext-devel libXfixes-devel
  libXxf86vm-devel libasan0 libatomic1 libboost_atomic1_54_0
libboost_chrono1_54_0 libboost_graph1_54_0 libboost_graph_parallel1_54_0
  libboost_locale1_54_0 libboost_log1_54_0 libboost_math1_54_0
libboost_mpi1_54_0 libboost_python1_54_0 libboost_random1_54_0
  libboost_regex1_54_0 libboost_serialization1_54_0 libboost_signals1_54_0
libboost_test1_54_0 libboost_timer1_54_0 libboost_wave1_54_0
  libdrm-devel libecpg6 libibverbs1 libitm1 libpq5 libqt5-qtbase-common-devel
libstdc++-devel libstdc++48-devel libtsan0 libxcb-devel
  libxcb-res0 libxcb-screensaver0 libxcb-xevie0 libxcb-xf86dri0
libxcb-xinerama0 libxcb-xprint0 libxcb-xtest0 libxcb-xvmc0
  libxshmfence-devel linux-glibc-devel openmpi-libs postgresql94-devel
pthread-stubs-devel sqlite3-devel xextproto-devel
  xf86vidmodeproto-devel xproto-devel

The following source package is going to be installed:
  akonadi-server

73 new packages to install, 1 source package.

Hopefully that will solve it all !!
Eric

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[David Faure via KDE Bugzilla]

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

--- Comment #33 from David Faure  ---
Nope, it's in the code. You can however rebuild your distro package with a
patch added.

On rpm-based distros it's as easy as installing the source package (e.g. zypper
si kdepim), adding a patch in the .spec file, then rpm -ba kdepim.spec.

For deb-based distros I find it a bit more involved, but doable still. I
bookmarked https://wiki.ubuntu.com/UbuntuPackagingGuide/BuildFromDebdiff
http://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.en.html

I won't provide assistance on this though, it's not really my area and there
are plenty more resources on the internet on this topic.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Nancy Anthracite via KDE Bugzilla]

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

--- Comment #32 from Nancy Anthracite  ---
Is there a way a user can add this fix in a config file or something like that?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/akon
   |imlibs/12f594dc74d4e7169497 |adi/9eca06b50cbd695f1cc586e
   |c7ee2286fdf113d36c5f|93bdd26c548608e7d

--- Comment #31 from David Faure  ---
Git commit 9eca06b50cbd695f1cc586e93bdd26c548608e7d by David Faure.
Committed on 27/02/2016 at 10:46.
Pushed by dfaure into branch 'master'.

Akonadi::SpecialCollectionsRequestJob: increase timeout from 10s to 30s

When KMail is started as part of session restoration, many things are
happening at the same time, and it can happen that another program has
the lock for more than 10 seconds.

This reduces the risk of being greeted in the morning by a suicide note:
"The EMail program encountered a fatal error and will terminate now.
The error was: Timeout trying to get lock"
REVIEW: 127175

M  +1-1src/core/jobs/specialcollectionshelperjobs.cpp

http://commits.kde.org/akonadi/9eca06b50cbd695f1cc586e93bdd26c548608e7d

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

  Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep
   |imlibs/cdc600992f8d281fe8f5 |imlibs/12f594dc74d4e7169497
   |c92f59ea5c303a70bb49|c7ee2286fdf113d36c5f

--- Comment #30 from David Faure  ---
Git commit 12f594dc74d4e7169497c7ee2286fdf113d36c5f by David Faure.
Committed on 27/02/2016 at 10:45.
Pushed by dfaure into branch 'Applications/15.12'.

Akonadi::SpecialCollectionsRequestJob: increase timeout from 10s to 30s

When KMail is started as part of session restoration, many things are
happening at the same time, and it can happen that another program has
the lock for more than 10 seconds.

This reduces the risk of being greeted in the morning by a suicide note:
"The EMail program encountered a fatal error and will terminate now.
The error was: Timeout trying to get lock"
REVIEW: 127175

M  +1-1akonadi/src/core/jobs/specialcollectionshelperjobs.cpp

http://commits.kde.org/kdepimlibs/12f594dc74d4e7169497c7ee2286fdf113d36c5f

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
  Latest Commit||http://commits.kde.org/kdep
   ||imlibs/cdc600992f8d281fe8f5
   ||c92f59ea5c303a70bb49

--- Comment #29 from David Faure  ---
Git commit cdc600992f8d281fe8f5c92f59ea5c303a70bb49 by David Faure.
Committed on 27/02/2016 at 10:44.
Pushed by dfaure into branch 'KDE/4.14'.

Akonadi::SpecialCollectionsRequestJob: increase timeout from 10s to 30s

When KMail is started as part of session restoration, many things are
happening at the same time, and it can happen that another program has
the lock for more than 10 seconds.

This reduces the risk of being greeted in the morning by a suicide note:
"The EMail program encountered a fatal error and will terminate now.
The error was: Timeout trying to get lock"
REVIEW: 127175

M  +1-1akonadi/specialcollectionshelperjobs.cpp

http://commits.kde.org/kdepimlibs/cdc600992f8d281fe8f5c92f59ea5c303a70bb49

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[David Faure via KDE Bugzilla]

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

David Faure  changed:

   What|Removed |Added

 CC||albertspijk...@hotmail.com

--- Comment #28 from David Faure  ---
*** Bug 288892 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[David Faure via KDE Bugzilla]

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

--- Comment #27 from David Faure  ---
Timeout increased from 10s to 30s, to help with the morning-session-restore
case: https://git.reviewboard.kde.org/r/127175/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Sérgio Basto via KDE Bugzilla]

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

Sérgio Basto  changed:

   What|Removed |Added

 CC|ser...@serjux.com   |

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Nancy Anthracite via KDE Bugzilla]

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

Nancy Anthracite  changed:

   What|Removed |Added

 CC||na...@anthracite.name

--- Comment #26 from Nancy Anthracite  ---
(In reply to m.eik michalke from comment #25)
> this should be reopened.
> 
> i'm getting a kmail2 crash with this "Timeout trying to get lock" error
> message almost daily when kmail2 is launched automatically after login. i
> have to stop and restart akonadi then and then start kmail manually for it
> to finally work.
> 
> it's going on for weeks now.
> 
> this is with kubuntu 14.04 packages (kontact 4.14.2)

The exact same thing is true for me.  It forces  me to close kmail but when I
restart kmail, it is fine.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[David Faure]

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

David Faure  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[m . eik michalke]

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

m.eik michalke m...@reaktanz.de changed:

   What|Removed |Added

 CC||m...@reaktanz.de

--- Comment #25 from m.eik michalke m...@reaktanz.de ---
this should be reopened.

i'm getting a kmail2 crash with this Timeout trying to get lock error message
almost daily when kmail2 is launched automatically after login. i have to stop
and restart akonadi then and then start kmail manually for it to finally work.

it's going on for weeks now.

this is with kubuntu 14.04 packages (kontact 4.14.2)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Maurel]

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

--- Comment #24 from Maurel guy.mau...@kde.org ---
As I get something like you, I make a check about the versionnumber auf the
packages. And found some bugs. These lead to a lot of bugsby some
filterdefinitions also.
Have a look such as:
 starting akonadi_control from a console:
/usr/local/bin/akonadi_control
I got:
 error while loading shared libraries: libboost_program_options.so.1.54.0:
cannot open 
shared object file: No such file or directory
If one/some background process(es) don't run, the rest isn't stable.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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]

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

Tim Holy h...@pcg.wustl.edu changed:

   What|Removed |Added

 CC||h...@pcg.wustl.edu

--- Comment #21 from Tim Holy h...@pcg.wustl.edu ---
I'm seeing this upon upgrade from Kubuntu 12.04 to 14.04. Doing
strace -f -e trace=file /usr/bin/kmail
revealed the following interesting lines:

kmail2(8480)/libakonadi Akonadi::GetLockJob::Private::timeout: Timeout trying
to get lock. Check who has acquired the name org.kde.pim.SpecialCollections
on DBus, using qdbus or qdbusviewer. 
kmail2(8480)/libakonadi
Akonadi::SpecialCollectionsRequestJobPrivate::lockResult: Failed to get lock:
Timeout trying to get lock. 
kmail2(8480) MailCommon::Kernel::emergencyExit: The Email program encountered
a fatal error and will terminate now.
The error was:
Timeout trying to get lock. 


$ qdbus org.kde.pim.SpecialCollections
/
/Debug
/MailDispatcherAgent
/MainApplication
/Settings

$ qdbus | grep -C5 org.kde.pim.SpecialCollections
 org.kde.akonadi_baloo_indexer-2841
:1.65
 org.freedesktop.Akonadi.Agent.akonadi_maildispatcher_agent
 org.freedesktop.Akonadi.MailDispatcherAgent
 org.kde.akonadi_maildispatcher_agent-2843
 org.kde.pim.SpecialCollections
:1.66
 org.freedesktop.Akonadi.Agent.akonadi_migration_agent
 org.kde.akonadi_migration_agent-2845
:1.67
 org.freedesktop.Akonadi.Agent.akonadi_newmailnotifier_agent


I moved my ~/.config/akonadi and ~/.local/share/akonadi out of the way and
rebooted, but this didn't help.

One oddity is that new local-mail resources get added each time I fail to start
kontact. I can delete them in the Akonadi Configuration module, so I have only
one left.

My mail is stored in ~/.local/share/local-mail. I have two POP3 accounts
configured.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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]

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

--- Comment #22 from Tim Holy h...@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.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[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]

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

--- Comment #23 from Tim Holy h...@pcg.wustl.edu ---
Well, in fact just waiting longer and/or stopping mysql made the InnoDB error
go away, and now things seem to be mostly working. The worst consequences I've
noticed so far are that:

 - My filter rules seem broken. All the old filters exist, but they ask me to
specify the target directory. I presume this is a consequence of having gone
through a period where certain folders didn't exist. This is a little sad,
since I have something like 300 filters.
 - My addressbook settings seem to have been lost. I have an old (from 2012)
backup std.vcf file, so I can recover some but not all.

If anyone has tips about getting past these, I'm happy to hear about it.

On the plus side: things seem noticeably faster, I am really looking forward to
that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Maurel]

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

--- Comment #19 from Maurel guy.mau...@kde.org ---
can you try to make a trace such as:
strace -f -e trace=file /usr/bin/kmail
and store the ouput of the console.
Then, search for lines such as:
statfs(/home/guy-kde/.kde/share/config/emailidentities.lock, 0x7fffbcf09630)
= -1 ENOENT 

and check if the directory is writeable

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Kanwar Plaha]

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

--- Comment #20 from Kanwar Plaha kanwar.pl...@gmail.com ---
@Maurel: thanks for that suggestion. I can explain further when the issue
happens. Let's say I have cleared .config/akonadi and .local/share/akonadi
directories and then tried to restart Kontact. This is usually if I've upgraded
my KDE version. I have several local mail folders. I have noticed I get the
above error when its reading local mail folders and in the meanwhile I'm trying
to add an IMAP account, in particular, and changing settings, in general. Once
local mail is loaded and Kmail is happy, this error does not show.
Is there a race condition somewhere (just guessing!) while local mail is being
read?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

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

[Cédric Bellegarde]

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

Cédric Bellegarde gnu...@gmail.com changed:

   What|Removed |Added

 CC||gnu...@gmail.com

--- Comment #18 from Cédric Bellegarde gnu...@gmail.com ---
Still present here with KDE 4.10.3

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs