Manoj Srivastava wrote:
> look into ~/.xsession-errors if you use xdm, or, if you use
> startx, look for errors in the log file (assuming you start startx
> like startx >& //tmp/startx.log).
>
> Sounds like your window manager is dying. I got that when I
> messed up the configu
Hi,
look into ~/.xsession-errors if you use xdm, or, if you use
startx, look for errors in the log file (assuming you start startx
like startx >& //tmp/startx.log).
Sounds like your window manager is dying. I got that when I
messed up the configuration for fvwm2 once.
Joey Hess wrote:
> Sudhakar Chandrasekharan wrote:
> > I recently upgraded my hamm installation to the latest set of software under
> > frozen. Suddenly I find that X windows have lost their "chrome". I tried
> > kde, fvwm2 and olwm. Smae problem in all the cases. Why is this
> > happening? Ho
Sudhakar Chandrasekharan wrote:
> I recently upgraded my hamm installation to the latest set of software under
> frozen. Suddenly I find that X windows have lost their "chrome". I tried
> kde, fvwm2 and olwm. Smae problem in all the cases. Why is this
> happening? Hoe can I get around it?
I r
Hi,
I recently upgraded my hamm installation to the latest set of software under
frozen. Suddenly I find that X windows have lost their "chrome". I tried
kde, fvwm2 and olwm. Smae problem in all the cases. Why is this
happening? Hoe can I get around it?
S.
--
"The human race never solves an
5 matches
Mail list logo
