[SOLVED] KDE SC 4.10's KMail acting very weird

dimm0k · 02-13-2013, 10:31 PM

So I'm running Slackware64 14.0 and have been upgrading KDE using AlienBob's packages, that of which I'm thankful for. I've gone from 4.8.5 -> 4.9.3 -> 4.9.4 -> 4.9.5 and to finally 4.10.0. Haven't really hit any problems from all these upgrades until 4.10.0 where KMail won't retrieve any e-mails from two of my IMAP servers. I've tried removing those two accounts and adding them back in... it connects, but refuses to retrieve the messages. I've also moved everything from my home directory elsewhere, effectively giving my user account a fresh KDE configuration, but KMail still does the same thing. I've rebooted my machine, removed everything from /tmp, /var/tmp/kde*, and also reinstalled the KDE packages with no change in outcome. I would rather not wipe my system and re-install to resolve this as that is kind of a crappy way to solve an issue, but I also don't want to spend so much time that re-installing would be more feasible so I'm looking for some suggestions.

I have verified that it's definitely something on my system by installing KDE 4.10.0 under virtual instances KUbuntu AND Slackware64 14.0 and they work fine. I can also telnet to the IMAP server with no problems... so any suggestions would be welcome!

Alien Bob · 02-14-2013, 03:55 PM

Recompiling akonadi fixes this issue, which I also experienced. The boost package has been updated after akonadi was compiled for Slackware, and this breaks akonadi.

Code:

$ akonadictl stop
akonadictl: error while loading shared libraries: libboost_program_options.so.1.49.0: cannot open shared object file: No such file or directory

I reported this to Pat so I expect an updated akonadi package will land in -current soon.

Eric

volkerdi · 02-14-2013, 04:26 PM

This was already done in -current on Tuesday.

dimm0k · 02-15-2013, 08:37 AM

Thanks guys! This one baffled the heck outta me!

dimm0k · 02-16-2013, 03:01 AM

Alien_Bob: it's been irking me what you said about the boost package being updated after akonadi was compiled and it was this that was causing the above issue. Perhaps I'm just slow... but while I do in fact see the boost package with a later time stamp in Slackware64 14.0, what baffles me is why this was NOT happening in the fresh virtual machine install of Slackware64 14.0 and directly updating to KDE SC 4.10. If you get the chance, can you please explain?

Alien Bob · 02-16-2013, 05:43 AM

Quote:

Originally Posted by dimm0k

Alien_Bob: it's been irking me what you said about the boost package being updated after akonadi was compiled and it was this that was causing the above issue. Perhaps I'm just slow... but while I do in fact see the boost package with a later time stamp in Slackware64 14.0, what baffles me is why this was NOT happening in the fresh virtual machine install of Slackware64 14.0 and directly updating to KDE SC 4.10. If you get the chance, can you please explain?

In Slackware 14, boost was not updated. My KDE 4.10.0 packages built on Slackware 14 worked OK as a result. On the other hand, when Pat updated to KDE 4.10.0 in slackware-current he did version upgrades of several other packages, among which boost. And boost was built later than the packages related to the KDE update. That is why akonadi in -current failed to find the older boost library against which it had been compiled a long time ago.

Eric