KDE5 Version - running XFCE as well [Tracker keeps running in KDE5 session]

Hi, hope everyone is doing well and having a great weekend!
I’m KDE5 user, experimenting with XFCE right now.
I’ve installed the default XFCE patterns from Yast and after that made a reboot.
First session I logged in XFCE (no baloo obvious) noted the tracker process through
xfce4-tarkmanager. After that (logged out from XFCE) I’ve logged in KDE5 and for my
surprise (open ksysguard [1]) I see the tracker processes running as well with baloo one.

[1] https://dl.dropboxusercontent.com/u/9093640/Screenshot_20160723_102821.png

So, I’ve logged out from KDE5 and logged in again in the XFCE session to see whether
baloo had the same behavior - no, it didn’t run in XFCE [2] Very nice!

[2] https://dl.dropboxusercontent.com/u/9093640/Captura%20de%20tela_2016-07-23_10-45-59.png

Okay here is my question.
Is it normal tracker keeps running in the KDE session?



I’ve found that when multiple Desktops are installed…

  • The Display Manager of the original Desktop is used in all Desktops, not the default display manager for any other Desktop.
  • Often when an application is installed in any Desktop, it will become available in all Desktops (This may be your observation) as long as it doesn’t actually conflict with another application.


Yes, I’ve been seeing that for many versions.

I usually turn it off in XFCE settings. And then tracker no longer runs in KDE either. But I think it still runs in Gnome.

Personally, I have no use for these search functions. There only purpose seems to be to consume disk space and make backups larger.

It is even worst, it always starts in kde session - even if you don’t start other (in my case xfce) DE.


The first app I usually use/open is Dolphin and use (ctrl + I and ctrl + F) search options a lot.

@tsu2, yes I’ve seen this as well.
In this particular case, tracker insists in start up even in the KDE session.