On Mon, Mar 7, 2011 at 8:09 AM, Arjan van de Ven <ar...@linux.intel.com> wrote: > To be clear, this does not mean that "tracker" is completely removed; > tracker is still being used (together with tumbler) for indexing media > on the device. At this point we are seeing serious issues > (performance/stability) with this solution, but the first attempt will be to > fix the deficiencies rather than a replacement.
Actually, where exactly are tracker's results used in the Netbook UX for indexing media? I thought banshee was independently indexing media as well... sometimes they even get into a fight about it: http://lists.meego.com/pipermail/meego-community/2011-February/003597.html At least on the 1.2 Netbook release, tracker does cause problems -- I've disabled its media scanning to prevent issues ongoing issues: http://lists.meego.com/pipermail/meego-community/2011-February/003605.html For Maemo issues with tracker -- and potential customizations to prevent performance issues: http://lists.meego.com/pipermail/meego-community/2011-February/003598.html There appears to be duplicated functionality between tracker and banshee's media indexing. If other tracker functionality has been removed for 1.2, and tracker's media indexing results seem to be unused by banshee, what about removing tracker entirely from the 1.2 Netbook UX? > there's a lot of impact from this currently, both in terms of just raw CPU > cycles to power impact to stability (we're seeing quite some crashes, which > worries me from a security pov) I'm glad this is being considered and I concur. One other issue for indexing: if a gstreamer codec needs to be invoked first, e..g. for indexing or thumbnailing media, then is that potentially untrusted or closed-source codec sandboxed, when executing? What of the security of the gstreamer pipeline against media-based attack vector? -- Niels http://nielsmayer.com _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
