LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Audacious segmentation fault (https://www.linuxquestions.org/questions/slackware-14/audacious-segmentation-fault-631699/)

neurotic_lancer 03-30-2008 10:57 AM
Audacious segmentation fault
 
When I execute audacious, it fails to launch. If I do from the terminal, I get a segmentation fault error.
Code:
philippe@zeus:~$ audacious
Segmentation fault
I checked all the dependencies and they all seem to be satisfied. Anybody else getting this error?

duryodhan 03-30-2008 11:33 AM
Is this the default slackware package?
Did you try and reinstall it ?

Did you try the package at http://slackbuilds.org/result/?search=Audacious ?

You could try the above package and compile it with debug support to see what the problem is exactly ... audacious is not really that big a program , so you can easily recompile it .


If you are a noob see below :

you can reinstall by reinstalling the package in the slackware DVD. See the Packages.txt in the root dir of the DVD/CD. Search for audacious in that.

The link is a slackbuild package. Read the reame on the same site( look at the bottom of the page) on a nice tutorial on slackbuild packages.

You can edit the options by adding a enable debug. See the slackbuilds help for more.

machines 03-30-2008 12:36 PM
did you change any program settings before this happened?

segmentation faults are sometimes caused by changes to the programs settings file.

i got a segmentation fault in my file manager, i had to delete the settings file, then the program worked.

neurotic_lancer 03-30-2008 01:00 PM
I upgraded to current so I'm using (or trying to use) version 1.5.0. I tried reinstalling it and it didn't do anything. I'll look into those slackbuild scripts to see if they are built with improved compatibility.

willysr 03-30-2008 06:46 PM
did you do partial upgrade or full upgrade to -Current?

it's better to stick with one tree and not mixing it up, since -Current and -Stable are using different toolchain to compile packages

neurotic_lancer 03-30-2008 06:55 PM
I did a full upgrade to -current. I needed the new radeonhd driver which wouldn't work on xorg 7.2 so I upgraded everything to -current to make sure I didn't miss anything.

duryodhan 03-30-2008 11:03 PM
Quote:
i got a segmentation fault in my file manager, i had to delete the settings file, then the program worked.
this is also pretty good advice. Try deleting

Quote:
rm ~/.local/share/audacious/ -rf

neurotic_lancer 04-01-2008 09:57 PM
Deleting that folder didn't help. I guess the next thing to try is to make a brand new package myself. Is there anyway to see how the slackware developers put them together so I can try to build a slackware compatible package which will integrate well?

rworkman 04-01-2008 11:01 PM
Quote:
Originally Posted by neurotic_lancer (Post 3107815)
Deleting that folder didn't help. I guess the next thing to try is to make a brand new package myself. Is there anyway to see how the slackware developers put them together so I can try to build a slackware compatible package which will integrate well?
You might try running it in gdb or get an strace when running it - that will likely yield some clues about what's happening.

As for how the package is put together, see the slackware-version/source/ directory on any Slackware mirror.

neurotic_lancer 04-04-2008 10:26 AM
Ok, I figured out the problem and fixed it. And I feel really stupid for not trying that out earlier. I simply ran slackpkg clean-system to remove obsolete packages and then about 10 or 12 packages were uninstalled. After I did that, audacious worked just fine. Apparently, a package from the 12.0 branch was conflicting with the 12.1 tree. Thanks for all the input though.

ananai 07-07-2008 10:01 AM
when i excute audacious from terminal under debian, i got
Code:
amidi-plug(amidi-plug.c:amidiplug_init:97): init,read configuration
amidi-plug(i_backend.c:i_backend_load:107):loading backend '/usr/lib/audacious/Input/amidi-plug/ap-alsa.so(name 'alsa') successfully loaded
segmentation fault

donnied 07-10-2008 01:29 PM
audacious segfault
 
I got the same thing in Debian.
Code:
mmap(NULL, 32832, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fbc34b4d000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 4333 detached
I tried deleting the prefs folder and that didn't work.
So, I just reinstalled the old version.
Code:
dpkg --install  /var/cache/apt/archives/audacious_1.5.0-2_amd64.deb

shadowsnipes 07-10-2008 10:51 PM
Quote:
Originally Posted by neurotic_lancer (Post 3110640)
Ok, I figured out the problem and fixed it. And I feel really stupid for not trying that out earlier. I simply ran slackpkg clean-system to remove obsolete packages and then about 10 or 12 packages were uninstalled. After I did that, audacious worked just fine. Apparently, a package from the 12.0 branch was conflicting with the 12.1 tree. Thanks for all the input though.
Ah, so your upgrade wasn't finished yet ;)


All times are GMT -5. The time now is 04:36 AM.