Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#37872 - [virtualbox] 4.3.2 100% CPU
Attached to Project:
Community Packages
Opened by Gene (GeneC) - Friday, 22 November 2013, 03:43 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 25 November 2013, 02:16 GMT
Opened by Gene (GeneC) - Friday, 22 November 2013, 03:43 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 25 November 2013, 02:16 GMT
|
DetailsDescription:
virtualbox 4.3.2 exhibits 100% CPU problem - seems to be fixed in 4.3.3 (test) Additional info: Upstream seems to have fix as stated here: https://www.virtualbox.org/ticket/12300 Any chance to get 4.3.3 test version into testing? VB is almost unusable at the moment. * package version(s) virtualbox 4.3.2-1 * config and/or log files etc. Steps to reproduce: Run virtualbox - I am running windows xp as guest. |
Closed by Sébastien Luttringer (seblu)
Monday, 25 November 2013, 02:16 GMT
Reason for closing: Won't implement
Monday, 25 November 2013, 02:16 GMT
Reason for closing: Won't implement
Comment by Sébastien Luttringer (seblu) -
Monday, 25 November 2013, 02:16 GMT
"testing" is a repository to test packages related stuff or risky new releases. Pushing testing version of vbox is not planned. Releases are enough crappy.