Hallo
Yesterday I upgraded from F15 to F16. This went smoothly (almost) but after the restart there were ugly processes running and tacking much of the CPU power: tracker-*
AFAIK these processes are the "nepomuk" part of gnome and I don't need them. Why are the tracker processes activated in a typical KDE environment?
Martin
On 11/27/2011 06:09 AM, Martin (KDE) wrote:
Hallo
Yesterday I upgraded from F15 to F16. This went smoothly (almost) but after the restart there were ugly processes running and tacking much of the CPU power: tracker-*
AFAIK these processes are the "nepomuk" part of gnome and I don't need them. Why are the tracker processes activated in a typical KDE environment?
tracker stuff is running on my system as well but not using any significant amount of CPU.
Not sure why they would be installed but on my system tracker is needed by:
brasero
brasero-nautilus grilo-plugins shotwell totem totem-nautilus
If you don't use of of those apps it should be safe to just "yum remove tracker" .
Martin _______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Am Sonntag, 27. November 2011, 07:47:52 schrieb Patrick Boutilier:
On 11/27/2011 06:09 AM, Martin (KDE) wrote:
Hallo
Yesterday I upgraded from F15 to F16. This went smoothly (almost) but after the restart there were ugly processes running and tacking much of the CPU power: tracker-*
AFAIK these processes are the "nepomuk" part of gnome and I don't need them. Why are the tracker processes activated in a typical KDE environment?
tracker stuff is running on my system as well but not using any significant amount of CPU.
Not sure why they would be installed but on my system tracker is needed by:
brasero
brasero-nautilus grilo-plugins shotwell totem totem-nautilus
If you don't use of of those apps it should be safe to just "yum remove tracker" .
I removed it. But every now and then I used brasero and tracker tried to "track" all my photos and music and this took quite a lot CPU power (and as the data is store on a NFS server quite a lot of network bandwidth).
The question was regarded to the autostart of tracker: It was started by XDG autostart but as it is a gnome thingy it would be great that is is started in the gnome environment only (like network manager).
Martin
Martin (KDE) wrote:
The question was regarded to the autostart of tracker: It was started by XDG autostart but as it is a gnome thingy it would be great that is is started in the gnome environment only (like network manager).
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
On Sun, Nov 27, 2011 at 11:16 AM, Timothy Murphy gayleard@eircom.net wrote:
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
I think he was referring to "nm-applet", the NetworkManager applet for GNOME, which in GNOME 2 times appeared in /etc/xdg/autostart but had "OnlyShowIn=GNOME" so it doesn't start in KDE. (GNOME 3 doesn't use it anymore except in fallback mode AFAIK.)
-T.C.
Am Sonntag, 27. November 2011, 11:21:20 schrieb T.C. Hollingsworth:
On Sun, Nov 27, 2011 at 11:16 AM, Timothy Murphy gayleard@eircom.net
wrote:
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
I think he was referring to "nm-applet", the NetworkManager applet for GNOME, which in GNOME 2 times appeared in /etc/xdg/autostart but had "OnlyShowIn=GNOME" so it doesn't start in KDE. (GNOME 3 doesn't use it anymore except in fallback mode AFAIK.)
That's the one I had in mind. And it would be grat if tracker could get the same settings. otherwise I have tracker and nepomuk/strigi cluttering my hard disk.
Martin
-T.C.
On 27/11/11 18:26, Martin (KDE) wrote:
Am Sonntag, 27. November 2011, 11:21:20 schrieb T.C. Hollingsworth:
On Sun, Nov 27, 2011 at 11:16 AM, Timothy Murphy gayleard@eircom.net
wrote:
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
I think he was referring to "nm-applet", the NetworkManager applet for GNOME, which in GNOME 2 times appeared in /etc/xdg/autostart but had "OnlyShowIn=GNOME" so it doesn't start in KDE. (GNOME 3 doesn't use it anymore except in fallback mode AFAIK.)
That's the one I had in mind. And it would be grat if tracker could get the same settings. otherwise I have tracker and nepomuk/strigi cluttering my hard disk.
So just to follow this up, we are now seeing tracker-store sometimes taking over 3GB memory on some systems, with poor consequences for other processes. I wonder if this is a bug or whether its actually doing something useful?
I'm also wondering if its sensible to stop tracker from starting in KDE? I could submit a BZ requesting that they not start in KDE, but what happens if someone runs eg totem or shotwell which seem to have a dependency on tracker? Do those apps start the tracker processes on the fly or do they just miss the tracker functionality?
Oh, I see someone got to the BZ nearly two months before me: https://bugzilla.redhat.com/show_bug.cgi?id=771601
Does anyone have a view on this? Maybe we are just hitting a bug in tracker-store and it would be ok to have it running if the bug were not there?
Thanks.
Roderick
On Thursday 01 March 2012 10:32:58 Roderick Johnstone wrote:
On 27/11/11 18:26, Martin (KDE) wrote:
Am Sonntag, 27. November 2011, 11:21:20 schrieb T.C. Hollingsworth:
On Sun, Nov 27, 2011 at 11:16 AM, Timothy Murphy gayleard@eircom.net
wrote:
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
I think he was referring to "nm-applet", the NetworkManager applet for GNOME, which in GNOME 2 times appeared in /etc/xdg/autostart but had "OnlyShowIn=GNOME" so it doesn't start in KDE. (GNOME 3 doesn't use it anymore except in fallback mode AFAIK.)
That's the one I had in mind. And it would be grat if tracker could get the same settings. otherwise I have tracker and nepomuk/strigi cluttering my hard disk.
So just to follow this up, we are now seeing tracker-store sometimes taking over 3GB memory on some systems, with poor consequences for other processes. I wonder if this is a bug or whether its actually doing something useful?
I'm also wondering if its sensible to stop tracker from starting in KDE? I could submit a BZ requesting that they not start in KDE, but what happens if someone runs eg totem or shotwell which seem to have a dependency on tracker? Do those apps start the tracker processes on the fly or do they just miss the tracker functionality?
Oh, I see someone got to the BZ nearly two months before me: https://bugzilla.redhat.com/show_bug.cgi?id=771601
Does anyone have a view on this? Maybe we are just hitting a bug in tracker-store and it would be ok to have it running if the bug were not there?
Hi Roderick,
I don't want to start a rant, but you can use the following workaround:
1. cp /etc/xdg/autostart/tracker-* to ~/.config/autostart/ 2. Edit each copied tracker desktop file: change: X-GNOME-Autostart-enabled=true to X-GNOME-Autostart-enabled=false 3. Open System Settings -> Startup and Shutdown (-> Autostart) 4. Unckeck all tracker Desktop Files
Now the tracker is diabled, it will not be started.
Hope this helps for the time being.
Martin Kho
Thanks.
Roderick
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
On 01/03/12 13:51, Martin Kho wrote:
On Thursday 01 March 2012 10:32:58 Roderick Johnstone wrote:
On 27/11/11 18:26, Martin (KDE) wrote:
Am Sonntag, 27. November 2011, 11:21:20 schrieb T.C. Hollingsworth:
On Sun, Nov 27, 2011 at 11:16 AM, Timothy Murphy gayleard@eircom.net
wrote:
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
I think he was referring to "nm-applet", the NetworkManager applet for GNOME, which in GNOME 2 times appeared in /etc/xdg/autostart but had "OnlyShowIn=GNOME" so it doesn't start in KDE. (GNOME 3 doesn't use it anymore except in fallback mode AFAIK.)
That's the one I had in mind. And it would be grat if tracker could get the same settings. otherwise I have tracker and nepomuk/strigi cluttering my hard disk.
So just to follow this up, we are now seeing tracker-store sometimes taking over 3GB memory on some systems, with poor consequences for other processes. I wonder if this is a bug or whether its actually doing something useful?
I'm also wondering if its sensible to stop tracker from starting in KDE? I could submit a BZ requesting that they not start in KDE, but what happens if someone runs eg totem or shotwell which seem to have a dependency on tracker? Do those apps start the tracker processes on the fly or do they just miss the tracker functionality?
Oh, I see someone got to the BZ nearly two months before me: https://bugzilla.redhat.com/show_bug.cgi?id=771601
Does anyone have a view on this? Maybe we are just hitting a bug in tracker-store and it would be ok to have it running if the bug were not there?
Hi Roderick,
I don't want to start a rant, but you can use the following workaround:
- cp /etc/xdg/autostart/tracker-* to ~/.config/autostart/
- Edit each copied tracker desktop file: change: X-GNOME-Autostart-enabled=true to X-GNOME-Autostart-enabled=false
- Open System Settings -> Startup and Shutdown (-> Autostart)
- Unckeck all tracker Desktop Files
Now the tracker is diabled, it will not be started.
Hope this helps for the time being.
Thanks Martin
Following: http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html (section "OnlyShowIn and NotShowIn Keys"), I was considering changing:
OnlyShowIn=GNOME;KDE;XFCE; to OnlyShowIn=GNOME;XFCE;
in /etc/xdg/autostart/tracker*.desktop
to make sure tracker is not started for any of my KDE users on my systems.
Roderick
Martin Kho
Thanks.
Roderick
On Thursday 01 March 2012 15:10:51 Roderick Johnstone wrote:
On 01/03/12 13:51, Martin Kho wrote:
On Thursday 01 March 2012 10:32:58 Roderick Johnstone wrote:
On 27/11/11 18:26, Martin (KDE) wrote:
Am Sonntag, 27. November 2011, 11:21:20 schrieb T.C. Hollingsworth:
On Sun, Nov 27, 2011 at 11:16 AM, Timothy Murphy gayleard@eircom.net
wrote:
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
I think he was referring to "nm-applet", the NetworkManager applet for GNOME, which in GNOME 2 times appeared in /etc/xdg/autostart but had "OnlyShowIn=GNOME" so it doesn't start in KDE. (GNOME 3 doesn't use it anymore except in fallback mode AFAIK.)
That's the one I had in mind. And it would be grat if tracker could get the same settings. otherwise I have tracker and nepomuk/strigi cluttering my hard disk.
So just to follow this up, we are now seeing tracker-store sometimes taking over 3GB memory on some systems, with poor consequences for other processes. I wonder if this is a bug or whether its actually doing something useful?
I'm also wondering if its sensible to stop tracker from starting in KDE? I could submit a BZ requesting that they not start in KDE, but what happens if someone runs eg totem or shotwell which seem to have a dependency on tracker? Do those apps start the tracker processes on the fly or do they just miss the tracker functionality?
Oh, I see someone got to the BZ nearly two months before me: https://bugzilla.redhat.com/show_bug.cgi?id=771601
Does anyone have a view on this? Maybe we are just hitting a bug in tracker-store and it would be ok to have it running if the bug were not there?
Hi Roderick,
I don't want to start a rant, but you can use the following workaround:
cp /etc/xdg/autostart/tracker-* to ~/.config/autostart/
Edit each copied tracker desktop file: change: X-GNOME-Autostart-enabled=true to
X-GNOME-Autostart-enabled=false
Open System Settings -> Startup and Shutdown (-> Autostart)
Unckeck all tracker Desktop Files
Now the tracker is diabled, it will not be started.
Hope this helps for the time being.
Thanks Martin
Following: http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html (section "OnlyShowIn and NotShowIn Keys"), I was considering changing:
OnlyShowIn=GNOME;KDE;XFCE; to OnlyShowIn=GNOME;XFCE;
in /etc/xdg/autostart/tracker*.desktop
to make sure tracker is not started for any of my KDE users on my systems.
You can do that too, but when tracker is updated your changes will be lost.
Martin Kho
Roderick
Martin Kho
Thanks.
Roderick
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Am Sonntag, 27. November 2011, 18:16:23 schrieb Timothy Murphy:
Martin (KDE) wrote:
The question was regarded to the autostart of tracker: It was started by XDG autostart but as it is a gnome thingy it would be great that is is started in the gnome environment only (like network manager).
I don't know anything about tracker, but your throw-away remark about NetworkManager seemed rather odd to me.
Surely NM starts under KDE as well? In fact NM seems to be a more-or-less essential part of Fedora nowadays? Is there any alternative?
You got me wrong (and I left out details). NM is running (it is a system service) but I meant GnomeNetworkManager.
Instead of NM you can try wicd.
Martin