LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 02-13-2013, 10:31 PM   #1
dimm0k
Member
 
Registered: May 2008
Location: Brooklyn ZOO
Distribution: Slackware64 14.0
Posts: 385

Rep: Reputation: 23
KDE SC 4.10's KMail acting very weird


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!
 
Old 02-14-2013, 03:55 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,112

Rep: Reputation: Disabled
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
 
1 members found this post helpful.
Old 02-14-2013, 04:26 PM   #3
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620
This was already done in -current on Tuesday.
 
2 members found this post helpful.
Old 02-15-2013, 08:37 AM   #4
dimm0k
Member
 
Registered: May 2008
Location: Brooklyn ZOO
Distribution: Slackware64 14.0
Posts: 385

Original Poster
Rep: Reputation: 23
Thanks guys! This one baffled the heck outta me!
 
Old 02-16-2013, 03:01 AM   #5
dimm0k
Member
 
Registered: May 2008
Location: Brooklyn ZOO
Distribution: Slackware64 14.0
Posts: 385

Original Poster
Rep: Reputation: 23
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?
 
Old 02-16-2013, 05:43 AM   #6
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,112

Rep: Reputation: Disabled
Quote:
Originally Posted by dimm0k View Post
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
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
vhosts acting weird tibberous Linux - Server 3 01-13-2011 02:17 AM
VLC is acting weird mlangdn Slackware 6 01-03-2011 05:59 PM
OS acting weird MTK358 Linux - Newbie 5 01-07-2010 05:08 PM
[SOLVED] computer acting weird baronobeefdip Linux - Desktop 13 10-24-2009 08:29 PM
apache acting weird... Red Squirrel Linux - Newbie 1 03-03-2004 08:29 PM


All times are GMT -5. The time now is 08:07 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration