That's a common misunderstanding. While the source code may not have obvious spyware, the compiled code may have had patches applied before compilation to perform spying functions.

1 members found this post helpful.

I do not know if anyone else gets this, but another reason to remove Akonadi - after exiting X Session - it just sits on this message until you ^C out of it.


To be fair this is still KDE4, maybe this is addressed in KDE5 Plasma who knows - but yea even when you exit an X Session Akonadi likes to be that much of a nuisance.

That's unlikely to be an issue in Full Recommended Install of Slackware and anyone that worries about it can just compile it all from source since that comes with the full set of disks. Any additional software, excepting a few firmware items and the obvious nVidia blob, is or can be compiled locally as well so malware infested patches really aren't at all likely.

1 members found this post helpful.

Is this a function of akonadi or Virtual Box?.. 'cuz that doesn't happen for me.

I don't know how this is an intended function of virtualbox

-edit

As for Akonadi - it is clearly not exiting properly for some unknown reason.

Isn't that su "hanging" until you killed it?

Did you actually just try a <ENTER> ? It's possible that the final Akonadi message did not end with a newline and thus obscures your login prompt until you press the Enter key or just login.

1 members found this post helpful.

To be fair I was going into su just to shutdown - even if I didn't su , that message was there; Akonadi was just spitting out errors still long after me exiting KDE.

I don't see any errors at all ... just Application 'akonadiserver' exited normally...

Here I just launched the VM session again, went into KDE and simply logged out of KDE and I am not doing anything further and this is what the result is:


It will literally STAY like this until I do a ^C. Right now I haven't done anything and it has been over a minute.


-edit

Now I just hit ^C
-edit 2

Ok maybe not an error, but clearly it just hangs there and will do so until you do a ^C. This is just a normal full installation of --Current I did not modify anything. As far as I know and remember, even under 14.2 at least for me Akonadi has always done this.

It looks like a logging message that is printed after X shuts down, and you are probably sitting at your bash prompt without realising it.

No, I can't do anything until I hit ^C