** Description changed:

  Binary package hint: tracker
  
  I've already raised this at
  http://bugzilla.gnome.org/show_bug.cgi?id=578159, but I'm also raising
  it here to keep it on the radar, as it has the potential to hurt a lot
  of users upgrading from Intrepid where tracker is still installed by
  default.
  
  Tracker will begin indexing when removable media is inserted, despite
  being explicitly disabled in the preferences (and it is disabled by
  default in Ubuntu anyway). It doesn't just index the removable device,
  but all of the users watch directories (by default, the users entire
  home directory). When doing this, the tracker-applet doesn't appear like
  it normally should when indexing, and the usual notifications warning
  the user that indexing is beginning do not appear either. The
  performance hit of this for many users could be quite severe whilst the
  indexing is happening, and the user will be left wondering why this is
  so.
+ 
+ ***TEST CASE FOR SRU***
+ 
+ * With the current version of Tracker (0.6.93-0ubuntu1):
+ 1) Disable indexing in System -> Preferences -> Search and Indexing
+ 2) Insert removable media (eg, USB drive)
+ 3) After a minute or so, note that trackerd and tracker-processes are 
consuming some CPU cycles.
+ 4) For further verification, monitor the output of "dbus-monitor --session". 
A short while after inserting the removable drive, you will see some 
org.freedesktop.Tracker.IndexStateChange signals on the bus
+ 
+ * With the updated version of Tracker (0.6.93-0ubuntu2):
+ 1) Disable indexing in System -> Preferences -> Search and Indexing
+ 2) Insert removable media (eg, USB drive)
+ 3) Note that trackerd and tracker-processes use no significant CPU cycles.
+ 4) Monitoring the session bus with "dbus-monitor --session" should show no 
org.freedesktop.Tracker.IndexStateChange signals on the bus.

-- 
tracker starts indexing when removable media is inserted, even when indexing is 
disabled
https://bugs.launchpad.net/bugs/359207
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to