well, It just hit the repos as I wrote that message.  I confirm that the
patch works as intended.  177 second cpu burn is now a 10 second cpu
burn.  I also opened up the filebrowser pane, and it seemed to be
working.  I then went to /var/lib/dpkg/info, and the same 10 second burn
took place, but it worked fine.  I came the the same conclusion as Hew.
I will also report upstream.

mac_v , the proposed solution only attempts to improve the situation
(more aggressive solutions have been postponed till jaunty).  For my
computer, the situation is improved to the point that I don't care, but
I also recognize that this still could be a problem for others with
slower computers.  You should still get a cpu bump, but it should be
allot shorter in duration.  Hopefully, you can provide more details as
to how things got worse for you, because this looks working to me.

-- 
gedit uses %100 CPU when opening a file in /var/lib/dpkg/info/
https://bugs.launchpad.net/bugs/276094
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