I was not talking to anyone in particular with my statement.

Well, I don't see a problem there. Akonadi by default uses an internal mysql database, which means it's not starting up a mysql server accessible by anyone else. For sure they could have used something else for storage, but I think the reasons why they chose mysql are outlined pretty well on several info pages/blogs on google.

Akonadi is the future storage engine for anything PIM-related (mail, contacts, calendar, RSS-Feeds, ...). I don't think it's used a lot right now, but afaik kmail is currently being ported to it. I'm not sure about the status of the other PIM apps.

Nepomuk is way more hidden than akonadi. It's primary role currently is for tagging files and storing other metadata. But it will focus much more on semantic data in the next releases, will work together with other apps to display data in a semantic way. The developers are talking about connecting nepomuk with plasma's activities (think of one activity for work-related things, another for gaming, another for ....) and that's just one example.

Granted, the usecases for both technologies are rather limited at the moment. But with every kde release they'll get more and more important.

Yo ppr:kut, please can you tell me why all of a sudden kde 4.3 startup freezes for almost 5 minutes, and the only way to unfreeze is to login to console and kill akonadiserver process!
I have tried adding the kres migrator disable code to disable migration and have removed all resources(which does not solve the problem), and then added them back which should bring back the stability in kde(i.e not freezing). It didnt use to happen first but now all of a sudden it freezes without a cause. Strange thing is everytime I start kde it searches for wallpapers for slide show,which was not the case earlier...any help would be appreciated.

Anyways IMHO akonadi must be made optional or atleast optional to start..afterall linux is all about options!

Sorry, no idea. How about asking the kde-devs about this? There are various options (mailing list, forum, bugtracker, irc...)

lol - ok, please forgive me for not knowing that!

I understand what you're saying, so much so that I decided to give nepomuk a second chance. In particular, the search facility of strigi might come in handy. Unfortunately, the price has been it randomly gobbling up 95% of CPU time, 30% of memory and nigh on 1Gb of disk space and the indexing still shows no sign of ending. But, I can restrict which folders it indexes and even turn it off completely if I wish.

I just have no use for Akonadi just now. My work uses google docs/calendar/mail etc. and I have a G1 phone (which I do love) so all my PIM is take care of by google. I do have concerns about google though, so perhaps in the future I'll turn to Akonadi, but who knows. For now I don't need Akonadi and want to disable it.

But, it has no off switch; that's really my issue with it.

As root, type:
Would you ever change you mind:

All debate on the necessity/usefulness of akonadi and other stuff aside, it is, IMNSHO, quite unforgivable to SHOVE it down my throat! At the very least, there ought to have been a simple dialog box asking me if I wanted to use it! I finally had enough of it throwing up errors everytime I booted up to bother to google a fix! I had to google it, coz it is NOT so trivial and obvious to ELIMINATE it!

And because somebody brought it up, the idea that its wrong to 'whine' about this is nuts! From my perspective, KDE making me use Akonadi is akin to MS bundling IE and Outlook and forcing me to use them!!! If the developers intend it to become an 'integral' piece of the 'KDE-experience', then hide it away where I cannot see it. And if its the type of component that requires user interaction, then allow me the charity of disabling the feature set completely, at whatever cost!

Karthikrr, nobody made you use Akonadi, you chose to install it among other packages (knowing or not what is its purpose, thats_your_problem), so if you are not happy with it just_remove_it_and_stop_complaining.

Futhermore, Akonadi is not part of KDE (the desktop), so KDE make you use KDE, nothing more -- and certainly not Akonadi.

EDIT. And if you are not happy with KDE, why use it ? There are a lot of others Desktops and Windows Managers shipped with Slackware 13.

Didier, I don't know who you are or what your 'standing' is in the 'Open Source Community', I don't care ... From my perspective, the great thing about the Open Source Community is that MY problem is EVERYBODY'S PROBLEM! Thats precisely what makes the linux world tick, IMO! Which means, what you call COMPLAINING, I would call CRITICISM. If you cannot deal with criticism (I doubt you are even a part of the KDE/Akonadi team, so its not even criticism aimed at you!), then "thats_your_problem". If you notice, the major gripe has been with the lack of any visible means to 'turn it off'/'disable' it. It ought to be a simple enough task to add such an option!

As for the question about 'happiness', maybe you are lucky enough to be 'perfectly happy' with what you have, but me and pretty much everybody else I know, we tend to be happy with some aspects, while unhappy with other aspects ... We use what gets our work done for us ... I am happy with most of the stuff KDE throws in, while I am not exactly excited about certain other things it incorporates ... I 'complain' as do others, so that the developers can see what the reaction from the public is to the changes they are bringing in ... If they care to make changes based on our 'cribbing', good for them. If they decide that its not the direction they want to go and so DONT make any changes, good for them again ... I certainly won't lose any sleep over them not making a change ... ESPECIALLY not after I figure out how to eliminate the thing that I dont like ...

Let me give you another example, one that will make EVERY Slackware 'fan-boy' froth at the mouth ... I have never been 'happy' with the NEED to edit xorg.conf each install to enable mouse-scrolling! To me, there is no excuse to NOT incorporate an additional line during the install process itself, using whatever mechanism needed ... But I don't stop using Slackware on account of this ... If they wanted to change it, they would, if they didn't, well, I know the fix, life goes on ... And no, don't start about Slack 13 and how this is no longer needed, it had nothing to do with the Slack team consciously making a change, it was a natural by-product of some fundamental changes they made such as using HAL!

I finally decided to break down and install 13 on my spare box in order to make up my own mind about it about 4 days ago now.
The first thing I did was update it.
I then installed 4.3.1 from a link I found here in the Slack forum.
Sorry, can't remember who rolled the packages but the nickname started with a V.
Akonadi did not start on it's own after that and there is a link to start and stop it in settings.
The errors on start up also went away.
The only thing I've found I don't like about the newer KDE is I havn't a clue as to what the hell a lot of things are, how to turn them off or how to get them back when I go, "I wonder what this button does?"
Pretty much about like I was when I first installed Linux...
I cured that by simply installing XFCE and set it up so that it resembles my KDE look until I can figure KDE out.
I understand disk space is a commodity for some, in my instance it isn't as on that box it's a 160 gig with only the one Slack install on it,,,, but,,,,XFCE is an alternative and pretty much just as simple and similar enough to KDE 3.5 to be able to be happy with it.
It's Linux folks, it's a never ending learning process. ;)

I wonder why they incorporated such changes in the next release ... hmm, could it be because people COMPLAINED?

Anyways, its good to know that 4.3.1 'evolved' ... windtalker, if you can remember the link, please share. I'll do a little search myself too ...

As a matter of fact I just ran across it, but it's for 32 bit.

http://cardinal.lizella.net/~vbatts/...ges/4.3.1/x86/

64 bit is also available I believe and it's on about page 2-3 maybe of the thread, "are there any packages available for Slack 13."

Kharthikr, I am a Slackware user and not part of any developing team. I'm not even a KDE user (I prefer Fluxbox). I guess that your feature request or wish of having a "visible mean to turn off/disable" Akonadi in association with KDE will have more chance to be listen or satisfied if you address it to people in concern, that is to say KDE and/or Akonadi developers. Nor sure any of them will ever read this thread ;)

About X and HAL, I don't need HAL so I do not use it, but I run xorgsetup to create xorg.conf with my settings.

What I would have liked is the Slackware installer proposing me to run xorgsetup -- but my guess it won't happen now that the xorg-server shipped with slackware rely on HAL fdi files by default for its settings :(

windtalker, thanks for the link, and thankfully, Im still on 32-bit as well :) Will give this a try when time permits ...

Didier, many people, including me, post our 'complaints' here, because we are concerned ONLY (as selfish as that may sound) with Slackware and how WE use it ... In a sense, end-user feedback here, chances are that somebody or the other who hangs out here also happens to hang out at the KDE forums, where they MIGHT echo our views ... Its not a science, I admit ... But, there is also the fact that by the time people like us come here to crib about stuff, the developers have already received a fair deal of feedback and are already working on making changes ... as is evident by the apparent fact that 4.3.1 is better than the stock version with Slack 13 ...

As for HAL and xorg support, I do believe you can still turn off HAL and have xorg use a conf file on Slack 13 ... If Im not mistaken, using nVidia drivers (not the open source nv) REQUIRES that nvidia-settings be run to generate an xorg.conf file that holds additional settings ...

As for Slackware presenting the option during install, actually there are quite a large number of such things that could be done ... And I wouldn't even put the burden of this on the core team, I would think building a custom-installer could be a community task ... My dream distro would be one that had Ubuntu's 'out of the box experience' coupled with Slackware's flexibility! I personally DETEST Ubuntu for the fact that it presumes to be my mother, but as I have realised over the last few weeks, when it comes to getting a LAMP server running with least hassles, Ubuntu's server edition is MUCH better than Slack 13! Of course, this holds true ONLY for a n00b like me, I have never setup a server before this ... If I had a lot more technical knowledge, I would start a project myself, but Im nowhere near qualified to even begin to try something like that ...

I should can ... But unfortunately in that case the X server crashes because of a bug in the 1.6.3 version of xorg-server, unless I disable dBus too... But I need dBus, noticeably to use Kontact.

There are two workarounds as of now : use a newer version of xorg-server or recompile xorg-server with the option --disable-config-hal, see this thread
That's how I do it, as suggested in CHANGES_AND_HINTS.TXT. But may be another way could be to edit one of the fdi files? I didn't check nor try, though.

EDIT In fact, I first create xorg.conf with xorgsetup, then edit it by hand to change driver's name from nv to nvidia.

I'm going pretty well letting Hal goes away with mouse, keyboard and synaptics, but setting the video with xorg.conf.