towsonu2003: >Could you please try to reproduce the problem again after a system update >(apt-get update && apt-get upgrade)? thanks for your bug report.
The system is daily upgraded against ubuntu repositories and the bug is still present. Kevin: > 1) Please see if you can't get a version of 0.2.14 somewhere, overall its > nicer on the CPU/Ram then previous releases. Is there a repository where i can get updated packages or do i need to compile beagled from sources? > 2) A big part of what were seeing here is a behavioral thing. I think you're partially right, I mean I agree that is correct for beagled to work during idle times; what instead is wrong and makes this behaviour a bug is: a) beagled duty is spent all over one out of the two cores avaible on my processor, causing selective overheating (and consequent premature high speed fan activation). Possible fix -> make beagled background indexing multithreaded or debug current code if already multithreaded b) high cpu usage when idle keeps persisting over long periods (i've monitored the pc for about 2 hours and still beagled was indexing), this situation is quite strange since beagled preferences are told to index only my home directory (and recursively all the nested ones) but I don't have so many files to index. This scenario also suggest some bugs during the indexing operations, likely the one reported on bug #64326 where some file types took high time amounts to be indexed. -- 100% cpu load after 5' of inactivity https://launchpad.net/bugs/77106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
