XFCe audacious crash

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

XFCe audacious crash

Post#1 by Rava » 12 Jun 2015, 07:08

Code: Select all

Jun 12 09:05:28 porteus kernel: [102096.312024] traps: audacious[17524] general
protection ip:7f291387516b sp:7f28ed5abbe0 error:0 in libaudcore.so.3.0.0[7f2913
85e000+3a000]
Most recent XFCe x86-64 version.

It always crashed when trying to use the visualization "Open GL Spectrum Analyser"
It was the most neat one, and I used it most often. But in the most recent version of port it's sadly the one and only visualization that crashes audacious. (The other two work okay)

Code: Select all

rava@porteus:/mnt/live/memory/images$ file /usr/lib64/libaudcore.so.3.0.0#/usr/lib64/libaudcore.so.3.0.0: ELF 64-bit LSB  shared object, x86-64, version 1 (SYSV), dynamically linked, stripped
Cheers!
Yours Rava

beny
Full of knowledge
Full of knowledge
Posts: 729
Joined: 02 Jan 2011, 11:33
Location: italy

Re: XFCe audacious crash

Post#2 by beny » 12 Jun 2015, 17:27

hi rava, you are right,with opengl visualizazion the program crash this is the initial log:
bash-4.3# audacious
The program 'audacious' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 9557 error_code 8 request_code 154 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
so remain the other plugin

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#3 by Rava » 12 Jun 2015, 18:18

Maybe a new version is the solution.

From http://audacious-media-player.org/ :
Audacious 3.6.2 released
May 30, 2015
We have 3.6-devel in 3.1 XFCe Porteus.
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#4 by Rava » 24 Dec 2015, 11:36

I tried the newest version, audacious-3.3.4-x86_64-1 but it seems some dependencies have changed since it's not running:

Code: Select all

rava@porteus:/mnt$ audacious 
audacious: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory
:(

I had issues with missing darn libgtk-3.so.0 in the past. For some weird reason there is no pure 64 bit binaries to be found, the x86-64 binaries all have 32bit in its name, and true to that they not run in a pure 64bit system without 32 bit support. :( :evil: =@ :bad:
Cheers!
Yours Rava

qnarkill
Ronin
Ronin
Posts: 1
Joined: 26 Mar 2016, 13:06
Distribution: ZorinOS, Arch, Antergos, Lubun
Location: HELLsinki

Re: XFCe audacious crash

Post#5 by qnarkill » 26 Mar 2016, 13:13

if you want to have audacious working again

sudo nano ~/.config/audacious/plugin-registry

replace

vis /usr/lib/x86_64-linux-gnu/audacious/Visualization/gl-spectrum.so
stamp 1439738105
name OpenGL Spectrum Analyzer
domain audacious-plugins
priority 0
about 1
config 0
enabled 1

with
enabled 0

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#6 by Rava » 26 Mar 2016, 19:56

^

Code: Select all

root@porteus:/mnt/live/memory/images# find .|grep audacious|grep plugin-registry
root@porteus:/mnt/live/memory/images# find .|grep audacious.plugin-registry
root@porteus:/mnt/live/memory/images# ls  /root/.config/audacious/plugin-registry
ls: cannot access /root/.config/audacious/plugin-registry: No such file or directory
No such file, not as non-root, and also not in /root ...
Cheers!
Yours Rava

donald
Full of knowledge
Full of knowledge
Posts: 1175
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: XFCe audacious crash

Post#7 by donald » 27 Mar 2016, 03:50

^....weird...

Code: Select all

guest@localhost:~$ ls ~/.config/audacious/
config  playlist-state  playlists/  plugin-registry

root@localhost:~# ls ./.config/audacious/
config  playlist-state  playlists/  plugin-registry

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#8 by Rava » 27 Mar 2016, 05:55

Okay, seems the folder gets created as soon as audacious is started:

Code: Select all

rava@porteus:/mnt/DL$ ls ~/.config/audacious/
ls: cannot access /home/rava/.config/audacious/: No such file or directory
[starting audacious for the first time]
rava@porteus:/mnt/DL$ ls ~/.config/audacious/
playlists
Still, config playlist-state and plugin-registry are missing...

Did you make some changes or added plugins, so that config and plugin-registry got created?

And remember, I do have to manually save any changes anyway, so I need to know which files there are new, and probably to be put in mylocalsettings.xzm ...

Okay, the above was after starting audacious.
This is after playing a file:

Code: Select all

rava@porteus:/mnt/DL$ ls ~/.config/audacious/
config  playlist-state  playlists
Still, plugin-registry is missing.

I quit audacious and restart it.
...

Yep, now plugin-registry also got created. Who would have guessed that audacious creates it after it shuts down. :P


...

Oh,and looking into that file:

Code: Select all

vis /usr/lib64/audacious/Visualization/gl-spectrum.so
stamp 1406566298
name OpenGL Spectrum Analyzer
domain audacious-plugins
priority 0
about 1
config 0
enabled 0
Seems, OpenGL Spectrum Analyzer is set to enabled 0, same as the others.

Or did you not mean just replace
enabled 1
with
enabled 0
but remove all the other lines?

Me thought not... But that still would just be the standard settings, and one could enable it via menu, getting it to crash once more.

I also tried removing the whole entry as quoted in your post, but that won't remove it from the menu, just from the plugin settings file, it is still in the menu, and sure audacious still crashes after enabling it...


So, what did your suggested change did do for you? Did OpenGL Spectrum Analyzer vanish from the menu?

Edit2
Seems your version differs, or is the
stamp 1439738105
line one not a stamp by the compiled version, but some kind of time stamp when the settings file got created?
Cause in my file all stamp lines read

Code: Select all

 grep stamp ~/.config/audacious/plugin-registry |uniq
stamp 1406566298
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#9 by Rava » 27 Mar 2016, 06:20

Finally, found as very mundane solution: renaming /usr/lib64/audacious/Visualization/gl-spectrum.so into /usr/lib64/audacious/Visualization/gl-spectrum.so.disabled and removing the executable mode bit did remove it from the menu. Yay.

Sure, that cannot be done so easily, when I put the renamed file into my settings module, the original file will still be there after the next reboot, so there is no other way but
1) renaming it via the /etc/rc.d/rc.local .... or
2) remove the file from 003-xfce.xzm


And I did a bit of duckduckgo'ing for "/usr/lib64/audacious/Visualization/gl-spectrum.so", and according to this http://redmine.audacious-media-player.o ... 777?r=1782 there is now also a plugin named /usr/lib64/audacious/Visualization/gl-spectrum-qt.so

Maybe that runs with our version, and not crashes? The version mentioned there is:

Code: Select all

Repository: Packman Repository
Name: audacious
Version: 3.7-5.1
Arch: x86_64
and ours is 3.6-devel, and a devel in not meant as a finished stable version anyway...
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#10 by Rava » 27 Mar 2016, 07:08

tried compiling with ./audacious.SlackBuild with audacious-3.7.1.tar.xz, (from https://slackbuilds.org/mirror/slackwar ... audacious/ ) but sadly it failed:

Code: Select all

[....]
Configuration:

  Install path:                           /usr

  D-Bus support:                          yes
  GTK+ support:                           yes
  Qt support:                             no
  Valgrind analysis support:              no

Entering directory man.
Entering directory src.
Entering directory images.
Entering directory po.
Entering directory libguess.
Entering directory dbus.
Leaving directory man.
Leaving directory images.
make[5]: gdbus-codegen: Command not found
make[5]: *** [aud-dbus.h] Error 127
make[4]: *** [all] Error 2
make[3]: *** [dbus] Error 2
make[3]: *** Waiting for unfinished jobs....
[....]
Successfully compiled de.po.
[....]
Successfully generated dependencies.
[....]
Leaving directory po.
Successfully compiled guess_impl.c.
Successfully linked libguess.a.
Leaving directory libguess.
make[2]: *** [all] Error 2
make[1]: *** [src] Error 2
make: *** [all] Error 2
Entering directory src.
Entering directory dbus.
make[5]: gdbus-codegen: Command not found
make[5]: *** [aud-dbus.h] Error 127
make[4]: *** [all] Error 2
make[3]: *** [dbus] Error 2
make[2]: *** [all] Error 2
make[1]: *** [src] Error 2
make: *** [all] Error 2
I know, current is 14.2 and we run 14.1, still, I hoped it would work, cause there is only the way outdated audacious-3.3.4
Why is there no newer version for Slackware, Suse has the current 3.7.1, but Slackware only for Slack-current... :x

Or do I need more than just 05-devel activated to run slackbuild?


//edit
Seems, I need python:

Code: Select all

bash: /usr/bin/gdbus-codegen: /usr/bin/python: bad interpreter: No such file or directory
Who would have guessed? :)
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#11 by Rava » 27 Mar 2016, 07:35

So, finally I was able to compile the audacious, creating /tmp/audacious-3.7.1-x86_64-1.txz

But compiling the plugins failed, it wants audacious-3.7.1-x86_64 installed, so I did

Code: Select all

upgradepkg /tmp/audacious-3.7.1-x86_64-1.txz
but compiling the plugins failed due to

Code: Select all

checking for NEON... no
configure: error: Package requirements (neon >= 0.27) were not met:

No package 'neon' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables NEON_CFLAGS
and NEON_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Makefile:5: buildsys.mk: No such file or directory
make: *** No rule to make target `buildsys.mk'.  Stop.
Makefile:5: buildsys.mk: No such file or directory
make: *** No rule to make target `buildsys.mk'.  Stop.
This suggests neon is libneon, but searching for neon in all Slackware versions via https://slackbuilds.org/result/?search=neon&sv=14.1 gives me no results!

Any ideas?


Some info on neon:
http://www.webdav.org/neon/
neon is an HTTP and WebDAV client library, with a C interface. Features:

High-level wrappers for common HTTP and WebDAV operations (GET, MOVE, DELETE, etc)
Low-level interface to the HTTP request/response engine, allowing the use of arbitrary HTTP methods, headers, etc.
Authentication support including Basic and Digest support, along with GSSAPI-based Negotiate on Unix, and SSPI-based Negotiate/NTLM on Win32
SSL/TLS support using OpenSSL or GnuTLS; exposing an abstraction layer for verifying server certificates, handling client certificates, and examining certificate properties. Smartcard-based client certificates are also supported via a PKCS#11 wrapper interface.
Abstract interface to parsing XML using libxml2 or expat, and wrappers for simplifying handling XML HTTP response bodies
WebDAV metadata support; wrappers for PROPFIND and PROPPATCH to simplify property manipulation.
Me thinks audacious uses neon for online sound streaming, why else would it need http get ?
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: XFCe audacious crash

Post#12 by Rava » 27 Mar 2016, 08:30

Okay, it seemed that I managed to compile neon (V 0.30.1), but ./configure for audacious-plugins is not able to find it... And libneon differs from all other libs I had to find for getting a program to run:

Code: Select all

root@porteus:/mnt/DL/a# file /usr/local/lib/libneon.*
/usr/local/lib/libneon.a:  current ar archive
/usr/local/lib/libneon.la: libtool library file, 
root@porteus:/mnt/DL/a# file /usr/local/lib/*
/usr/local/lib/libneon.a:  current ar archive
/usr/local/lib/libneon.la: libtool library file, 
/usr/local/lib/pkgconfig:  directory 
root@porteus:/mnt/DL/a# file /usr/local/lib/pkgconfig/neon.pc 
/usr/local/lib/pkgconfig/neon.pc: ASCII text
pkg-config doesn't like this, as it seems:

Code: Select all

root@porteus:/mnt/DL/a# pkg-config neon
root@porteus:/mnt/DL/a# echo $?
1
And so, I get the same error from ./configure for audacious-plugins

Code: Select all

configure: error: Package requirements (neon >= 0.27) were not met:

No package 'neon' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables NEON_CFLAGS
and NEON_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Makefile:5: buildsys.mk: No such file or directory
make: *** No rule to make target `buildsys.mk'.  Stop.
Makefile:5: buildsys.mk: No such file or directory
make: *** No rule to make target `buildsys.mk'.  Stop.
Any ideas? Me thinks I let it rest for now...
Cheers!
Yours Rava

Post Reply