This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Kmail, Not getting lock

Tags: None
(comma "," separated)
Dave-P
Registered Member
Posts
30
Karma
0

Kmail, Not getting lock

Mon Feb 20, 2017 10:45 pm
Hi,
Running Pc-Linux 64 bit, fully updated. KDE Desktop. I have 2 POP Email accounts.
When opening Kmail after a short delay the following message appears.
[ message ]
The Email programe encountered a fatal error and will terminate now.
The error was :
Timeout trying to get lock,
[ end ]
Sometimes the two password entry windows appear before I open Kmail, if I enter the
passwords then open Kmail, it opens and works Ok. However if only one password
entry appears and is used then the fatal error message appears.
If I ignore the error message and click on Check Mail it brings up the password entry
Kmail still terminates, one or two attempts like that and Kmail can be opened and works Ok.

Also I have to enter the password every time I send an Email.

a ) Is there a fix for the 'Timeout trying to get lock' problem ?
b ) As the only user, is it possible to use Kmail without entering the passwords every time ?

Any help most welcome. Dave P..
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: Kmail, Not getting lock

Sun Feb 26, 2017 8:36 am
What distribution are you using?


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
Dave-P
Registered Member
Posts
30
Karma
0

Re: Kmail, Not getting lock

Sun Feb 26, 2017 9:08 pm
Using uname -r I get 4.4.44-pclos1
its 64 bit, and has been updated regularly with all updates.
I don't know how to get any info on Kmail version etc.
Dave P..

Monday 20:30 Just tried to send an Email, it does not appear to be sent, but is moved to the Inbox,
with nothing in the Sent-Mail folder.

GIVEN UP, and gone on Holiday !!!!!!
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: Kmail, Not getting lock

Mon Mar 13, 2017 7:30 pm
kmail --version would help in this case.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
lanczos
Registered Member
Posts
1
Karma
0

Re: Kmail, Not getting lock

Fri Oct 27, 2017 9:01 pm
Looks like the original poster has given up.

I expect that he is/was using Kmail 5.2.3, since I am having the same problem using Debian stretch (installed from .iso DVD 5 days ago).

Here's what I am seeing:

$ kontact -v
kontact 5.2.3


Synaptic reports something different (probably a Debian internal number):
kontact 4:16.04.3-4~deb9u


So I get the same error: About 10-15 seconds after starting Kontact (or Kmail), a popup box shows:
The Email program encountered a fatal error and will terminate now.
The error was:
Timeout trying to get lock.


and then it vomits the following:
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_waIAcs" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_BKrfPH" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_npu1hd" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_jWcjhm" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_Ccbvts" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_snCDK5" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_SntiGY" false
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_vcF6S5" false
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_BKrfPH"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_waIAcs"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_npu1hd"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_Ccbvts"
Database "akonadi" opened using driver "QMYSQL"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_SntiGY"
New notification bus: "/subscriber/kmail2_19665_vcF6S5"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_jWcjhm"
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_snCDK5"
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_9SU55U" false
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_9SU55U"
Database "akonadi" opened using driver "QMYSQL"
QDBusObjectPath Akonadi::Server::NotificationManager::subscribe(const QString&, bool) Akonadi::Server::NotificationManager(0x5618d30b5660) "kmail2_19665_Y4EQMu" false
Database "akonadi" opened using driver "QMYSQL"
New notification bus: "/subscriber/kmail2_19665_Y4EQMu"
Shutting down "/subscriber/kmail2_19665_Y4EQMu" ...
Shutting down "/subscriber/kmail2_19665_BKrfPH" ...
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_Y4EQMu" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_9SU55U" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_vcF6S5" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_SntiGY" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_snCDK5" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_Ccbvts" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_jWcjhm" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_npu1hd" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_BKrfPH" now serving: ()
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kmail2_19665_waIAcs" now serving: ()
Shutting down "/subscriber/kmail2_19665_9SU55U" ...
Shutting down "/subscriber/kmail2_19665_vcF6S5" ...
Shutting down "/subscriber/kmail2_19665_SntiGY" ...
Shutting down "KMail Kernel ETM" ...
Shutting down "/subscriber/kmail2_19665_snCDK5" ...
Shutting down "/subscriber/kmail2_19665_jWcjhm" ...
Shutting down "/subscriber/kmail2_19665_waIAcs" ...
Shutting down "/subscriber/kmail2_19665_npu1hd" ...
Shutting down "/subscriber/kmail2_19665_Ccbvts" ...
Shutting down "kmail2-1186278907" ...




Thanks for any ideas/suggestions you might be able to offer...
dMaggot
Registered Member
Posts
1
Karma
0

Re: Kmail, Not getting lock

Fri Jan 12, 2018 1:03 pm
The output I got in my console was a lot more helpful, specifically pointing at the DBus name KMail2 could not acquire. I am sorry I cannot give exact details right now because I was able to fix this just in time to send important emails (KMail2 tends to break only when I need it the most), but as far as I remember:

  • The DBus name it could not acquire had a name related to Mail, right now with everything working properly I see the following candidates

    Code: Select all
    $ qdbus | grep Mail
     org.freedesktop.Akonadi.MailDispatcherAgent
     org.freedesktop.Akonadi.NewMailNotifierAgent
     org.freedesktop.Akonadi.ArchiveMailAgent
     org.freedesktop.Akonadi.MailFilterAgent
  • I ultimately found out it was the Mail Dispatcher Agent that took that name first. I forget exactly how I figured this out. I quit the Mail Dispatcher Agent from DBus using qdbusviewer, but I recommend you quit it from Akonadi Console. If you need instructions on any of these two procedures let me know.
  • I started KMail2 and I believe I had to start the mail dispatcher separately from Akonadi Console.


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], ourcraft