Hi,
I just installed BSDi on a machine as of a few days ago, and compiled
fvwm2 for it last night, and it works fine... sorta.
I'm not sure if this is an X problem, or an fvwm problem, so please bear
with me...
Anyway... if I run xinit or startx or xdm, the window manager will spawn
items, and start to run, BUT, it's impossible to start an xterm window; my
xinits don't get run, and my menu won't execute them from fvwm2 itself.
(I think I have the syntax correct, too)
--- .xinitrc ---
dclock &
xload &
xterm &
xterm &
exec fvwm2
---- .xinitrc ---
As for starting apps from fvwm2, I can run
xman/xmag/xv/xpaint/xsnow/netscape/xyadda/xyadda/xyadda properly, but
trying to invoke an xterm fails silently. Initially, I had the line
written incorrectly, like so: xterm "`hostname -s`", which would spit out
an error message from xterm itself about an unknown option and then the
contents of `hostname -s` (as expected). But.... after fixing that syntax
error, restarting, and trying again, it spits out... nothing. No message,
no window, nada.
So the question I have is just what the hell *is* happening? Even xinit
without running a window manager refuses to spawn one measly xterm,
leaving me stuck looking at the desktop until i hit Ctrl-Alt-Backspace, or
being forced to hit 'reset' if I start xdm. (no networking configured yet)
My choice of X servers doesn't seem to alter anything, either, both
XFree86 and Xmetro produce the same baffling results.
So has anyone ever seen this behaviour before, or can anyone direct me to
the proper place to find out exactly what the hell is going on?
thanks,
Klaus
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
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 Fri Feb 19 1999 - 14:05:00 GMT