Hey everyone, I'm the upstream Beagle maintainer. There are a few different issues in this bug:
* Excessive CPU usage in beagled-helper on certain files (.jar, .js, .m being the main ones): This is a bug in the freedesktop.org xdgmime implementation which Beagle uses. It was fixed in the GTK+ copy of this code, which we now consider to be the "canonical" upstream release. We incorporated the fixes into Beagle 0.2.10, which was released on 18 September. * 100% CPU usage in beagled or beagled-helper when the screensaver is active: This is not a bug. This is by design. The idea is that when you are not using your computer, Beagle can your data index as fast as possible and not worry about the impact on your user experience because, again, you're not using the machine interactively. This does not happen when you are on battery, however, so if you have a laptop you can test this by unplugging it from the wall and seeing if the CPU usage continues. (Give it a couple of seconds to finish indexing the file it's working on, though.) * There are other instances where certain types of files (often MS PowerPoint documents) can cause 100% CPU utilization. There have been fixes for problems like these in newer releases, the latest of which is 0.2.12. Please pester your packagers to update to the latest code. Any other instances where beagled or beagled-helper peg the CPU for extended periods of time is a bug. I don't regularly track bugs on Launchpad (nor do I in the Red Hat bugzilla, or any other vendor bug tracker), so filing them upstream in the GNOME Bugzilla is the best way to get the attention of not only me, but the other Beagle developers. -- beagled-helper loads CPU https://launchpad.net/bugs/64326 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs