Hi, it seems that I cannot run xlock at all on sun's from within fvwm2. I
don't understand why I'm having this problem. I don't have it under IRIX,
Linux/XFree86 or Linux/AccelX. I also checked and seem to have the same
problem under fvwm 1.24r. I probably never noticed it before cuz I try not
to use the suns on campus.
The suns are SS5's running Solaris 2.5.1 (SunOS 5.5.1) without
CDE. They've each got 32 meg ram.
What perplexes me is that xlock will work whenever I run it,
except from within fvwm2 or fvwm. I've tried several things. I tried
writing a shell script that exec'd xlock, I tried the full path, I tried
without the &, with the &... and nothing. Even stranger, is that if I
login to X in safe mode (type in passwd and press F1, get only an xterm
and nothing else, no WM), and if I then run my .xsession manually, I don't
get the problem. If I do that, I can run xlock as I normally would from
within fvwm2. My sysadmin claims he debugged a similar problem a while
back and said that if the USER env isn't properly set in the .xsession
(which I figured was a system thing, but what the hell... suns are
screwy), that things like that wouldn't work properly. I tried setting
both USER and user in my .xsession but neither worked... I'm just curious
as to whether anyone else has noticed this problem as well.
I figure that xlock is standard all over the place, but I don't
know what sun did to their version in order to make it all nice and
stuff... Does anyone know where I can find xlock so I can try compiling it
myself? I figure maybe that will help... In any case, here are a few lines
from my .fvwm2rc in case anyone thinks it may be important. The following
is what I use by default in fvwm2rc:
+ "Random" exec xlock -mode random -remote -allowaccess &
This is what I eventually ended up with
+ "Lock n' stuff" exec /usr/openwin/bin/xlock &
Again... neither of these worked... And I seem to also have the same
problem under vtwm, so I guess it's not just an fvwm thing.
As for the fellow having problems swallowing xclock, I am assuming
it may be part of the same problem I am having. My suggestion for a
freeware clock would be to grab the afterstep distribution and install the
asclock binary in the modules directory. It's probably the best,
non-obstructive, informing, ATTRACTIVE clock that I've seen. If you'd like
to see how I set mine up in a button bar, check out:
http://www.fiu.edu/~kvarga01/computing/linux/Prod-fvwm2.html
This one is the predecessor to my CD-fvwm2 and I think it sports a rather
productive environment... Thats for any help...
-peace
-----BEGIN GEEK CODE BLOCK-----
GAT d- s:+ !a C+(+++) UI/L/S/B++(+++) P>+ L+(++) E---- W+++ N+ o? K?
w++++ O--- M-- V PS+++_at_ PE Y-- PGP+ t++ 5 X++ R- tv+ b DI++ D+ G e>*
h*(!) r- y*(+)
------END GEEK CODE BLOCK------
"Life is when you shake it" -- me
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Mar 20 1997 - 10:23:19 GMT