There's a lot of stuff about getting rid of it, but it looks like a Thing That's Here to Stay, like it or not, so I'm wondering if anybody has figured out how to get the blasted thing to work (and, oh, yeah, how'd you do that)?

Tronayne,

Check out this thread.

There seems to be an issue with Mysql that causes problems with Akonadi for some people. One possible solution, as outlined in the thread above is to:

1. Upgrade to -current
2. Donload KDE 4.3.2 as built by Vincent Batts
3. Run upgradepkg on the files downloaded from Vincent's server.

Upgrading to -current has this fix to Mysql:

The word on the street is that that update fixes the problem with Akonadi. The upgrade to -current also upgrades QT, which is required to run KDE 4.3.2.

Naturally, there's a risk to running packages from the -current branch, as they may not be as stable as the -stable branch ( ), but in this case, I at least am willing to try it to get the benefits of running KDE 4.3.2.

Regards,

Hmm.

Well, I don't really want to mess with current and I'm also not too sure that I want to fiddle with KDE 4.3.2 either. However, rebuilding MySQL with the --with-innodb argument... now that seems more feasible.

Thanks for the information.

Bah, that's defeatist talk. You young whippersnappers have no stamina.

Until basically just now, I felt exactly the same way. The (to me, unknown) risks of running -current seemed too great.

However, right now (mid-October 2009) seems to be a good time to work with -current. There aren't any major changes to the core of the system (gcc, the kernel, etc.). Instead, -current has some rebuilt or upgraded packages. Nothing is added or removed that I can tell.

This seems to be a good window of opportunity to upgrade a handful of packages from -current without having a drastically different system from the stock download. The benefit is being able to run KDE 4.3.2.

I read a bunch of complaints about KDE 4.2, which comes with Slackware 13 on this board. For that reason, when I installed 13, I did not install KDE, but instead used Vincent Batts's KDE 4.3.1 packages. These packages do not require upgrading to -current.

I'm very happy with KDE 4.3.1, and I'll keep that on my Laptop computer. I'm about to start the upgrade to Slackware 13_64 on my desktop computer and figured that a quick upgrade to -current right after installation and then installing KDE 4.3.2 would be less trouble than trying to do all that later.

If worse comes to worse, I can always revert to the standard installation. In fact, I can even write a script to do just that in case I don't like the results.

If it gets even worse, I can always revert back to the standard installation and install KDE 3.10 from the unsupported directory of my favorite Slackware mirror.

Or, you could do that.

Regards,

OK, you've convinced me -- but, where are those packages? Been looking all over the place and can't seem to see anything.

Thanks! I'll give it a shot.

Here you go: Vincent Batts's KDE 4.3.2 packages.

And of course, get the -current packages from your favorite Slackware mirror.

Let us know how it turns out.

Regards,

Just FYI, the latest hplip from the -current packages doesn't work, i.e., it doesn't fire up. It gives an error and says to check the hplip installation.

Bummer. But, I don't need that one, so I'll see what happens if I don't upgrade it.

Thanks for the heads-up.

For the record, here's the list of packages updated in -current as of 10/20/09:

Regards,

Try KDE 4.3.2 on -Current..
It has just been included. Perhaps it might bring the Akonadi fixes

Thanks to all for the good advice. I'm off in the north woods of Michigan for six weeks or so (and on a dial-up line to boot; maybe get Hughes Net installed in a week or so) and a brand-new Dell Inspiron 17 was delivered yesterday (this laptop's display quit, after much trouble shooting, it's the motherboard, fixing it costs $85 more than the new one, thus the new one). The new one, of course, comes with the POS Vista (and, pant, pant, they're going to drop-ship 7 when it becomes available, be still my heart). I haven't decided to leave it dual-boot or just wipe Microjunk completely and maybe -- maybe -- install the stuff in VirtualBox...

At any rate it's going to be a while before I get back to fiddling with Akonadi; I'm thinking get Slackware installed on the new machine, take it over to the library (well, 20 miles away), hook up to their broadband, download the latest and greatest from -current and see what happens.

Thanks again for the good advice.

Yeah, it's fixed now
no more akonadi problem on KDE 4.3.2