Version: 6.3 Severity: normal Reportbug eats about 30% of cpu doing essentially nothing. I guess code which does progress bar updating is called too often and overhead is just so big. Reportbug can be in such state for few minutes, if for example smtp connection is very slow.