![]() Registered Member ![]()
|
Hello guys,
after fighting now every day with Kontact/akonadi this is my last attempt to improve the situation. All I need is a setup that allows me to start Kontact in a way that it is simply usable. Currently I need about 50 start attempts to get it working right at least one time at all. And this is more than annoying, I need this for my daily work. I have the following situations in various order: 1/ akonadi has already been started: 1a/ Simply nothing happens when starting Kontact - the waiting curser vanishes after some time. No Kontact process. 1b/ KWallet dialog pops up starting Kontact. After entering the passowrd nothing happens anymore again. Kontact procerss is running, but no application window appears. Kontact has to be killed. 1c/ The Kontact application window appears, but the application area is locked and shows the waiting cursor. Application behaves like showing a hidden modal dialog. Kontact has to be killed. 1d/ In rare cases Kontact triggers the KWallet dialog and appears normally after entering the password. 2/ akonadi has been stopped: 2a/ akonadi starts, an error about the LDAP address book resource appears, KWallet appears, but after entering password and acknowledging the error, the akonadi start window never disappears and kontact does not show up. Kontact has to be killed. It take me sometimes up to half an hour to reach situation 1d. When Kontact finally runs, the integration with the KAddressbook and the LDAP resource works fine. Another very bad side-effect is, that any unsaved mail gets lost. Kontact/KMail normally restores those at startup. Akonadi itself seems to be setup well: Akonadi Server Self-Test Report =============================== Test 1: SUCCESS -------- Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/jos/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi User=akonadi Password=XXXXX Options= ServerPath=/usr/sbin/mysqld StartServer=false Host=localhost [Debug] Tracer=null [QPSQL] Name=akonadi Host= User= Password= Port=5432 Test 2: SKIP -------- MySQL server executable not tested. Details: The current configuration does not require an internal MySQL server. Test 3: SKIP -------- MySQL server error log not tested. Details: The current configuration does not require an internal MySQL server. Test 4: SKIP -------- MySQL server configuration not tested. Details: The current configuration does not require an internal MySQL server. Test 5: SUCCESS -------- akonadictl found and usable Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully. Result: Akonadi 1.3.1 Test 6: SUCCESS -------- Akonadi control process registered at D-Bus. Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational. Test 7: SUCCESS -------- Akonadi server process registered at D-Bus. Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational. Test 8: SUCCESS -------- Nepomuk search service registered at D-Bus. Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational. Test 9: SUCCESS -------- Nepomuk search service uses an appropriate backend. Details: The Nepomuk search service uses one of the recommended backends. Test 10: SKIP -------- Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 11: SUCCESS -------- Resource agents found. Details: At least one resource agent has been found. Directory listing of '/usr/share/akonadi/agents': birthdaysresource.desktop contactsresource.desktop icalresource.desktop imapresource.desktop kabcresource.desktop kcalresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop microblog.desktop mtdummyresource.desktop nepomukcalendarfeeder.desktop nepomukcontactfeeder.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Directory listing of '/usr/share/akonadi/agents': birthdaysresource.desktop contactsresource.desktop icalresource.desktop imapresource.desktop kabcresource.desktop kcalresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop microblog.desktop mtdummyresource.desktop nepomukcalendarfeeder.desktop nepomukcontactfeeder.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/local/share:/usr/share' Test 12: SUCCESS -------- No current Akonadi server error log found. Details: The Akonadi server did not report any errors during its current startup. Test 13: SUCCESS -------- No previous Akonadi server error log found. Details: The Akonadi server did not report any errors during its previous startup. Test 14: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 15: SUCCESS -------- No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup. - Jörg |
![]() KDE Developer ![]()
|
Very strange.
Can you try starting the individual applications instead? E.g. kaddressbook, kmail, etc. Maybe this gives a hint were the Kontact shell hangs when it is loading the components. Cheers, _
anda_skoa, proud to be a member of KDE forums since 2008-Oct.
|
![]() Registered Member ![]()
|
I can start all the individual applications from command line without any problem: kmail, kaddressbook, korganizer, knode, knotes. They start all up within 2-10 seconds with kmail triggering kwallet.
|
![]() Manager ![]()
|
Please check ~/.kde/share/config/kontact_summaryrc - if there is any reference to the Special Dates plugin, remove it. That has been shown to cause this problem on many systems.
annew, proud to be a member of KDE forums since 2008-Oct and a KDE user since 2002.
Join us on http://userbase.kde.org |
![]() Registered Member ![]()
|
Removing the special dates plugin had no (positive) effect.
However, when starting kontact from konsole, I can see a lot of repeating messages like:
Since this sounds like the topic in the "Akonadi 4.4/Troubleshouting" page in the UserBase, I did follow that advice and removed the "Local Folder" resource. I tried this with akonadiconsole as well as with the standard akonadi settings page. In both cases the "Local Folder" resource is added immediately again. Funny enough, kmail has no problems to start and run although it emits this line on the console also:
Actually I don't know where this setting is coming from, there's no entry pointing to such a location:
|
![]() Registered Member ![]()
|
If I start akonadi and later kontact from console, I get following output:
That's it. The kontact process hangs in memory, produces the last line forever, but no window appears, simply nothing! |
![]() Manager ![]()
|
/Local not found is a well-known issue, but a very old one. I'm surprised that you have found it in 4.4. http://userbase.kde.org/Akonadi_4.4/Tro ... 2FLocal.22 explains what this is about and how to deal with it.
Between the Akonadi pages and the KAddressBook pages (they are all cross-linked) you will find solutions to many problems. Most people manage to get things working after going through the four pages.
annew, proud to be a member of KDE forums since 2008-Oct and a KDE user since 2002.
Join us on http://userbase.kde.org |
![]() Registered Member ![]()
|
As I already wrote, I did what was recommended and the situation above is the result. So, no changte so far! |
![]() Registered Member ![]()
|
I have deleted now the .kde4/share/config/kontact*rc files and the situation is more deterministic now. When starting Kontact, the KWallet dialog appears and after entering the passowrd Kontact starts with the tip of the day. However, the application is "locked" like if another modal dialog is hidden. Kontact has to be killed at that stage
![]() |
![]() Administrator ![]()
|
Try starting Akregator? If it locks up on startup, remove its configuration file also.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Apart from the "Unknown error" with the LDAP ressource, akonadi starts always fine.
Funny enough, this morning I had the first time the case that Kontact responded after start (I closed the tooltip dialog, switched to Kmail component and back to overwiew), but it was locked about a minute later. Regarding the missing "/Local" folder I checked the console output of another KDE 4.4.4 Kontact/KMail installation where these problems do not arise and the line appears there also. So it seems rather normal. |
![]() Administrator ![]()
|
Did you check with the RSS Feed Reader, Akregator? ( not Akonadi )
I am aware of a few cases where it has locked up on startup, and so could be causing this.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Hmm. I never had problems with akregator. Especially since akregator is not enabled by default when you remove the kontact*rc files, I doubt that it is responsible for the lock.
However, it seems that the overview plugin is invlolved in the ptoblem. I have now set kmail as default view and for now kontact starts up without this locked working area. I'll observe this in the next days. |
![]() Registered Member ![]()
|
OK, it seems it is really the overview plugin if it is shown at startup of kontact. At least for me ...
|
Registered users: Bing [Bot], Evergrowing, Google [Bot], ourcraft