Dan Espen wrote:
> Try this:
> exec fvwm2 2>/tmp/fvwm.out
Also try a 'failsafe' login (xterm, no WM), and run fvwm2 from the
command line there to see if there's a fundamental problem.
Another option is to copy the 'openwin' script, change the olwm ref. to
'fvwm2' in it, then run that after selecting 'command-line login (you may
need to <Ctrl-C> to stop that automatically running openwin or something).
You'll probably need to 'script errorfile' first; this option is a last
resort!
> > I compiled fvwm with xpm support ( I had to build and install the xpm
> > libs myself from xpm-3.4k-solaris.tgz )
You may well be hitting my favourite problem, which Dan has already
pointed out (not using -R fir libXpm).
I imagine from what you've said that almost certainly you're not finding
libXpm.so at startup.
See what 'ldd fvwm2' gives you. Then see if you've not LD_LIBRARY_PATH
set normally, and see if ldd 'loses' anything.
There's an option for the DT login (checks ... DTSOURCEPROFILE in
~/.dtprofile) that makes DT run your .login/whatever before [re]starting
X. If you need LD_LIBRARY_PATH/PATH/etc. set up for login, put 'em in
there and set that variable.
But it *is* cleaner to always try compiling stuff (like fvwm) with no
LD_LIBRARY_PATH.
--
=====================- http://www.racaldefence.com/ -===================
Neil Bird |
| If this .signature looks pants,
mailto:neil.bird_at_rdel.co.uk | then just stop using Outlook!
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Jul 13 2000 - 03:57:52 BST