I wish to start kmail silently, without reading messages about starting daemons, how should I change my settings?

My KDE is v4.4.1, I know about kmail depending at akonadi.

Which messages is Akonadi giving out? Is it just "Starting Akonadi Server...." or is it a self test report containing items which have failed?

bcooksley wrote:Is it just "Starting Akonadi Server...."

yes.

I believe this is not possible to be hidden as it shows that the application is responding to the user. If you start the Akonadi Server before running KMail however, it won't show.

Code: Select all

akonadictl start

Thank you. I use kmail as default client, it is started at kde session start and shutdowns only when exiting kde.

How should I autostart akonadi before kmail during kde session initialization?
How kmail starts akonadi, may be I need only edit some .desktop file?

There is no way to stop KMail from starting Akonadi if Akonadi isn't yet running. Given that KMail runs at startup it is virtually impossible to start Akonadi beforehand unfortunately.

Found bug https://bugs.kde.org/show_bug.cgi?id=227925 If you are interested please vote.

Why don't you just do this:
go into System Settings - Autostart.
tell it to execute "akonadictl start" at "pre-KDE startup"
and kmail at "startup"
won't that work? i haven't tried.

or how about a script that executes on after the other?

I tried couple of weeks ago, it did not work well.

Note that at the pre-KDE startup phase, certain user session services such as the D-Bus session server may not be available, and other KDE services, such as kded and klauncher may not be running. Also, the Sycoca may not have finished being updated, so you will end up with Akonadi failing to start in many cases.

Sincerely, I can't understand how it's possible to do something that doesn't work well and force us (users) to use it.
After introducing nepomuk/akonadi in kde4, a tried a lot of ways to get it work, but I quit of using it, because of the resources it consumes, and because that's something unnecessary.
Now, I don't use kontact anymore, I use thunderbird, I suppose I'll have to stop using kopete and I will become an user of amsn or any other, maybe somewhere in the future I will have to stop using kde because I feel I'm not anymore free, because developers don't respect anymore the freedom of choice.


I'm sad, really really sad.

@luispinho: In KDE 4.5, KMail is currently not depending on Akonadi. From 4.5.1 on, it will, but then it'll work só much better because it's built on top of Akonadi in 4.5.1

Sadly, this very issue has caused me to leave KDE. Like luispinho, I am very upset. I love KDE and am a great admirer of the work that so many have put in over the years. It pains me to be using Gnome, as the applications are inferior to KDE in terms of features and interface design. However, I have to use something for my work. Email and contact management not working properly is the straw that broke the camel's back. I can cope with Plasma being bloated and crashing occasionally. I didn't mind stopping using Kopete because it leaked memory like you wouldn't believe. I even soldiered on using my favourite ever text editor Kate for code, even though it didn't work anywhere near as well as in KDE 3. But when Kontact went for a burton, I couldn't cope. I'm sure Akonadi will be great one day, but I'm sorry to say I and many others will never find out, because we just can't cope without some kind of stable stream. This constant shoving of pre-alpha software into "release" versions is what is killing KDE. I'd be really happy to get stuck into KDE development (I still develop apps in Qt even though I've switched to Gnome for my desktop) but I have no incentive too if there is no stable release version. There just doesn't seem to be any objective. KDE really needs to sort out its release policy.

Anyway, end of rant. Thank you to all those who have put in so much effort to make my computing experience better over the last 8 years. I hope you get to wherever it is you want to go. Maybe I'll try KDE 5 when Gnome 3 makes me cry

Have you filed bugs regarding Kopete's memory leaks? ( please ensure to include detailed information, such as detailing which networks you use it with )

Which features in particular are missing from Kate? Did you check it's entire interface in case they were simply relocated? Did you file feature requests regarding these missing features?

Regarding Plasma, did you generate detailed backtraces and submit them? If they commonly had details involving KPixmapCache in them, then this is fixed in KDE 4.5, and was not Plasma's fault. It was fixed by complete refactoring of KPixmapCache.

That you can release kmail, and force users to use akonadi, which has so many resource consuming issues, sends meaningless messages on application startup, depends on one thing after another some of which may not be available, is plainly stupid. Either fix and force your dependencies tree: kmail->akonadi->mysql, and your startup tree: mysql->akonadi->kmail, or get rid of this akonadi rubbish before your users get rid of you.

R.

ps. mind you, this kind of arrogance worked for Windoze, maybe it'll work here too...