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#21501 - [xfmedia] --next action high CPU usage
Attached to Project:
Community Packages
Opened by Jiri Brachtl (paladin) - Wednesday, 27 October 2010, 21:02 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 01 November 2010, 10:21 GMT
Opened by Jiri Brachtl (paladin) - Wednesday, 27 October 2010, 21:02 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 01 November 2010, 10:21 GMT
|
DetailsDescription:
If I press the "next" button when the playlist is empty, xfmedia starts to take a lot of CPU time. The same happens for "xfmedia-remote --next". Other actions/buttons seem fine. Additional info: * xfmedia-0.9.2-6 Steps to reproduce: 1. Run xfmedia 2. Make the playlist clear 3. Click "next" button |
This task depends upon
Closed by Sergej Pupykin (sergej)
Monday, 01 November 2010, 10:21 GMT
Reason for closing: Fixed
Additional comments about closing: try 0.9.2-7
Monday, 01 November 2010, 10:21 GMT
Reason for closing: Fixed
Additional comments about closing: try 0.9.2-7
Steps to reproduce should be:
1. Run xfmedia
2. Make the playlist clear
3. Exit xfmedia
4. Start xfmedia
5. Click "next" button
It looks like upstream bug