SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
A distro with no further updates is a dead one imo, unless the user do it himself
Not every Linux machine is a webserver in constant need of security patches. I still have an old box with Slackware 11.0 just for fun. It doesn't talk to the hostile Internet, it doesn't need any updates.
There is no need to be upset and get so aggressive.
They have every reason to be upset and as aggressive as you were in your response.
FYI the latest security update to Slackware 13.0 is from 3/27/2014 for OpenSSH, so it
can hardly be characterized as ancient. Also, Slackbuilds are simply shell scripts to build *.tgz packages from source, not the *.rpm nor *.deb package that you must be used to.
Anyway, you could easily have typed echo $DISPLAY in an xterm before posting. You would have obtained a :0.0 and you would have understood what is wrong with olwm/olvwm in that version of XView.
Now, to return to the original point of the thread, since you are not the person who wrote the script and tries to maintain the XView/OpenLook package you were not asked to reply.
[*]The problem describedhere is still present but the -Wfsdb trick works.
Given the nature of the bug, I think without delving pretty deep into the xview code, this workaround is as good as it's likely to get.
Originally Posted by edorig
[*]DISPLAY is set to :0.0.0 by olwm/olvwm so that applications cannot be launched from the menu.
I looked into the part of the code for both olwm and olvwm that opens the display. There are two ways that the DISPLAY environment variable will be set: either using a variable from rdb (Xresources/Xdefaults) or the defaults used by server. I suspect the possibility of a typo in either any possible system Xresources or a user one. If you confirm that you are sure it is neither of these, I would double check in your .xinitrc/.xsession that nothing that runs before the window manager is mangling DISPLAY env variable on you.
Last edited by j_v; 04-09-2014 at 06:38 PM.
13.0 isn't ancient and it's still supported for security patches but SlackBuilds.org scripts officially support only full installations of the latest Slackware stable (ATM 14.1).
I just tested xview on a slackware-14.1 virtual machine and was able to launch applications from the menu and have no need of the -Wfsdb command line option (just launched it with this xinitrc), so regarding directly edorig's question, I think there's a dedicated FAQ: I don't have a 32bit host with a 13.0 full install around to test OP's problem (and probably, who knows, neither Tomasz does).
@edorig: Ok, I've got a full 13.0 vm running with xview slackbuild installed. I am seeing the error you are talking about. The display environment variable is set properly in the shell environment, so I believe it is perhaps in the window manager's code for the menu. If it is, I should have something soon.
There is a fix in trunk: http://code.xenu.tk/repos.cgi/xview/info/1d21c3c976. I am working up a patch to the slackbuild that incorporates Tomasz's fix for this issue. These changes were made just yesterday, so perhaps he can be persuaded to incorperate this fix into his slackbuild.
I'm building the package now in the vm... I will post after I have tested.