Summary: | media-sound/audacious-2.4_beta1 segfaults | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Osmialowski <newchief> |
Component: | Current packages | Assignee: | Tony Vroon (RETIRED) <chainsaw> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul Osmialowski
2010-07-23 20:20:48 UTC
Step 2. reminds me of a frequently asked question on various emulation related forums, that the standard response to was banning the user. Seriously though, while it might be something like audacious being more strict in treating mp3 tags than the other mentioned programs are, there's *no* chance of anybody doing anything without seeing those files, if only *some* files fail that way. As for bug 289513 (that seems you haven't filed upstream yet - at least your comment suggest so), it seems a local problem - perhaps a test file would help there too. An upstream report with a "suspicious file" attached is required. The software is already marked "unstable" on X86. Neither mplayer nor mpg123/321 read ID3 tags to the level of detail that Audacious does. If you are not willing to report bugs in applications, you should not be running ~arch software in Gentoo. |