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.
I am wondering if this issue is addressed in the next Slackware / Audacious inclusion. I made a thread about this (which escapes me in trying to find it for more info), but the gist of it was when I would choose the OpenGL Spectrum Analyzer in Audacious - it would crash. It had something to do with NVIDIA drivers, and the solution was to recompile audacious with qt I think? Well anyways here is a clue - this is from Slackware64-14.2 , trying to use the OpenGL spectrum analyzer in Audacious:
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 10285 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:320 [main_cleanup]: exit() called unexpectedly; skipping normal cleanup.
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.
I was considering a test run with updating a 14.2 system to Current. Reviewing CHANGES_AND_HINTS.TXT, NEW USERS/GROUPS SINCE 14.2, I read "postdrop user and group, UID and GID 92." I noticed no such user in /etc/passwd in my Current VM. The postfix package doinst.sh only adds a postdrop group and no postdrop user.
Looks like either the doinst.sh script or CHANGES_AND_HINTS.TXT should be corrected.
Also, the UPGRADE.TXT file, step 4, has not yet been updated to reflect which old packages to remove:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.