SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to run the OpenGL Spectrum Analyzer under Audacious, and it just crashes:
Code:
slackuser@slackmachine:~$ 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 4620 error_code 8 request_code 153 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.)
WARNING main.cc:319 [main_cleanup]: exit() called unexpectedly; skipping normal cleanup.
slackuser@slackmachine:~$
This is just stock Audacious with what is included(OpenGL Analyzer) - I am running the NVIDIA blob and I do have the 32-bit libraries and OpenGL installed - so what gives?
I've found there can be problems if the mesa package is updated/reinstalled over an earlier nvidia blob installation. Reinstalling the nvidia blob has always fixed that problem for me.
slackuser@slackmachine:~$ glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
2 frames in 6.0 seconds = 0.335 FPS
301 frames in 5.0 seconds = 60.094 FPS
300 frames in 5.0 seconds = 60.000 FPS
300 frames in 5.0 seconds = 60.000 FPS
slackuser@slackmachine:~$ ^C
slackuser@slackmachine:~$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
And I did not mess with any of the mesa packages. After doing a clean install of 14.2 , I installed the NVIDIA blob, THEN I did go multilib but if that were the case, other programs such as Google Earth would not be working, but I am able to run Google Earth and AFAIK it depends on mesa too right?
I just tried and found the same problem and its definitely not due to the similar mesa/nvidia thing I've seen previously. I also just tried 32bit & 64bit VM's (no nvidia blobs) and it works fine there.
I don't particularly want to switch to the Nouveau driver - I rather like the NVIDIA utilities provided with the blob, and everything works the way I like it - plus I don't know how it will affect my double monitor(reflected) setup that I have.
I downloaded & built the latest version (3.8) using the existing build scripts for xap/audacious & xap/audacious-plugins. At first the result was exactly the same when clicking the OpenGL Spectrum Analyzer checkbox - crashed audacious. However, I had noticed on their website that an optional Qt interface could be enabled by adding '--enable-qt' to the configure line of the build script. I rebuilt with --enable-qt and ran it as 'audacious --qt' and in that mode, the OpenGL Spectrum Analyzer checkbox worked as expected - no crash and nice looking opengl visualization.
I then went back to see if the existing version (3.7.2) would work the same way but the audacious-plugins-3.7.2 would not compile with --enable-qt.
So, short of fixing the actual bug, the workaround is to build version 3.8 with the --enable-qt option and always use the --qt option at runtime.
chris
Last edited by chris.willing; 11-03-2016 at 12:56 AM.
Reason: runtime switch is --qt (not -qt)
Its a solution - I could just recompile using slackbuilds for 3.7.2 - Just too lazy right now; then I have to figure out the shortcuts for my particular WM(LXDE) - since I don't feel like running audacious in a terminal, seems unnecessary to me. Overall I consider that a solution though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.