Segmentation fault when launching audacious

[demigaucher]

Hi everybody

I usually listen music with xmms, because it is relatively immune to high load
on the system (others, like VLC, give a chopped sound when the CPU is loaded).
My computer is an old machine from the last century !

Unfortunately, xmms cannot read .flac format (or I do not know how to make it
able to read it). So I tried audacious: I installed it, along with audacious-plugins,
using gslapt; the installation ran without problem.

When I tried to run audacious (menu > multimedia > audacious) nothing happens.
I then opened a console and typed "audacious": I obtained the error message
"segmentation fault".

Am I the only poor fellow in the world with this problem ? Does someone know the
cure ? By the way, does someone know how to make xmms able to read .flac format ?

Demigaucher
happily    running VL6.0 gold on an old P3@700 MHz w/384 Mb ram

[nightflier]

Don't know about Audacious, but I upgraded my flac package using this one:
http://slackware.osuosl.org/slackware-12.2/slackware/ap/flac-1.2.1-i486-2.tgz

and now XMMS plays flac files. 

[demigaucher]

Thanks, nightflier, I try now.

Demigaucher

[demigaucher]

Great, Nightflier, it works ! 

It was a bit messy to copy all these files in all the directories one by one, but
apparently I did forget none of them.   

Thanks & bye

Demigaucher

[nightflier]

It was a bit messy to copy all these files in all the directories one by one

Glad that worked for you. However, for future reference you can save a lot of work by using a terminal, as root, and use the command:

Code:

upgradepkg /path/to/name-of-pkg.tgz

It will remove the old package and install the new one.

In case of a brand new package, the command is:

Code:

installpkg /path/to/name-of-pkg.tlz

- the extension can be .tgz or .tlz, or .txz for SOHO.

[demigaucher]

Well, I prefer the cumbersome and stupid method : for each new file, rename the
old one with a _BAK extension, and copy the new aside: In case of problem, it is
always possible to remove the newly copied one and recover the good old one.
Of course, with hundreds of files this becomes ridiculous; moreover, there is always
the risk of human error.

I could perhaps be considered as a paranoiac, but I am very cautious with all these
automated tools: before installing the package you spoke about, I removed flac with
gslap, and... I saw gslapt remove k3b and Xine too !   I had to reinstall them, and I
don't know wether I reinstalled all that was eliminated by gslapt: I can have overpassed
some package that gslapt removed too quickly for me to have noted it.

"installpkg" being a console tool, it is perhaps safer ? I use now gslapt only for installs,
never more for removals.

Anyway, I enjoy my flac music now with xmms. Great. 

Thanks and bye

Demigaucher
happily running VL6.0 gold on a old P3@700 MHz with 382 MB ram.

[nightflier]

I wholeheartedly agree with you with respect to gslapt and package removals. Additionally, I don't fully trust it for installation, as it some times includes a lot more than I want. It's an unfortunate side effect of the built in dependency checking. Always review the list of packages to be installed or removed before clicking that final "OK" button.

The program "installpkg" is much simpler. It only installs the specified package. But it also registers the package in the database, so it can be removed using "removepkg". Again, it only works on one package at the time, "removepkg" will not touch any other programs. So yes, it is safer to use these command line tools.