Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 186872 - media-sound/audacious-1.3.2 regression in playlist handling: cannot open some files after audacious restarting
Summary: media-sound/audacious-1.3.2 regression in playlist handling: cannot open some...
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major
Assignee: Tony Vroon (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-28 10:12 UTC by DEMAINE Benoît-Pierre, aka DoubleHP
Modified: 2007-09-08 16:49 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-28 10:12:42 UTC
I store my music on this drive:

dhp@moon_gen_2:~$ mount |grep DHP
/dev/hdb1 on /mnt/DHP_400 type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)

mounted with this fstab line at boot:
dhp@moon_gen_2:~$ cat /etc/fstab |grep DHP
/dev/hdb1 /mnt/DHP_400 ntfs-3g defaults,uid=1000 0 0

I start audacious, clear the paylist, and add these two files:
/mnt/DHP_400/mp3/remix_and_bootlegs/tmp/essai.mp3
/mnt/DHP_400/mp3/remix_and_bootlegs/tmp/essai _.mp3

At this time, I can play both.

Then, I close audacious, and start it again. At this time, it plays them fine.

Then, I close audacious, and start it again. At this time, playlist shows this on screen:
esasi.mp3
essai .mp3?xspf

first file plays fine. Second produces bug #186868

Same problem when files are stored in /tmp (standard EXT3).

Always hapens after the second restart of audacious.

*** *** *** *** *** *** ***

root@moon_gen_2:~# emerge -DpeNuv world |grep -i audaci
[ebuild   R   ] x11-themes/audacious-themes-0.0.3  509 kB [?=>0]
[ebuild   R   ] media-sound/audacious-1.3.2  USE="nls -chardet" 0 kB [?=>0]
[ebuild   R   ] media-plugins/audacious-plugins-1.3.5  USE="aac alsa arts esd
flac jack lirc mad modplug musepack nls opengl oss sndfile vorbis wma -adplug
-chardet -pulseaudio -sid -timidity -tta -wavpack" 0 kB [?=>0]
[ebuild   R   ] media-plugins/audacious-xosd-0.5  0 kB [?=>0]
root@moon_gen_2:~#

*** *** *** *** *** *** ***

/tmp/emerge--info
here:
http://bugs.gentoo.org/attachment.cgi?id=126207&action=view
Comment 1 Tony Vroon (RETIRED) gentoo-dev 2007-07-28 17:10:46 UTC
Try with supported CFLAGS, you should not be specifying any of these three flags:
-mmmx -msse -m3dnow
Comment 2 DEMAINE Benoît-Pierre, aka DoubleHP 2007-07-28 17:27:02 UTC
(In reply to comment #1)
> Try with supported CFLAGS, you should not be specifying any of these three
> flags:
> -mmmx -msse -m3dnow
> 

CFLAGS is an array of arguments to pass to the compiler. I may pass any argument supported by the compiler ! and "man gcc" do mention support about the three ones you quote. Please, dont try to answer me back arguments of this style: fact these 3 options are not in the "recommended Gentoo options" has nothing to do with the fact audacious can break itself the way it handles the PL. This is compleetely offtopic:

http://www.gentoo.org/doc/en/gentoo-x86-quickinstall.xml
> you may want to alter the CFLAGS variable in your /etc/make.conf to optimise the code to your specific needs.

/etc/make.conf.example
> For optimal performance, enable a CFLAGS setting appropriate for your CPU.

The limitation on the use of CFLAGS in Gentoo is given by the list of supported features of GCC. If I remove these options as you ask me, it WILL break packages like mplayer or ffmpeg: I was forced to add them here because, without, my system does not work !!! (deps of mplayer complaining mplayer was not compiled properly, library loading problems ...).

Dont try to tell me CPU optimisation options can break playlist handling.
Comment 3 Hans Nieser 2007-09-08 16:49:04 UTC
I've been suffering from this bug for over a month now, and was too lazy to really try figure out what was going on, but today I got fed up with it. Anyway I simply recompiled it and removed my ~/.audacious and ~/.config/audacious directories and now it works fine. Oddly enough some googling on this bug did seem to indicate it had something to do with CFLAGS... as odd as that seems. But just to be sure, I have compiled it with these CFLAGS:

-O2 -march=prescott -pipe

It seems more likely to me though that there was a problem with the configuration, so try deleting those directories first.