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#70230 - [cmus] crashes on AAC files / update to latest release
Attached to Project:
Community Packages
Opened by Curtis (foxcm2000) - Tuesday, 30 March 2021, 12:53 GMT
Last edited by Alexander F. Rødseth (xyproto) - Friday, 09 April 2021, 07:32 GMT
Opened by Curtis (foxcm2000) - Tuesday, 30 March 2021, 12:53 GMT
Last edited by Alexander F. Rødseth (xyproto) - Friday, 09 April 2021, 07:32 GMT
|
DetailsDescription:
cmus 2.8.0-5 crashes with a segmentation fault whenever trying to play back AAC encoded audio files. These files are not corrupted and play back fine with other software including straight ffmpeg (ffplay -i ./aacfile.m4a). Furthermore, this is a regression because the files I have used to work fine with this version of cmus. My guess is a supporting library got updated and the installed version of cmus does not like the change. Wiping out my entire .cmus directory with the music database and other configuration data did not fix the problem. I have installed cmus-git from AUR and it works fine with these files, so my suggestion is to update cmus to the newest released version [2.9.1] to fix the issue. Additional info: cmus 2.8.0.-5 Steps to reproduce: 1. Run cmus 2. Try to play back an AAC encoded file, and there is an immediate segfault. |
This task depends upon
Comment by Alexander F. Rødseth (xyproto) -
Thursday, 08 April 2021, 18:01 GMT
I updated cmus to 2.9.1, please confirm that this is now working.
Comment by Curtis (foxcm2000) -
Thursday, 08 April 2021, 18:08 GMT
That fixed the issue! Thanks for the update and the bug can be closed.