Re: Running from XTerm Crashes X
On Sat, Sep 18, 2004 at 05:36:59PM -0700, Terry wrote:
> On Sat, 18 Sep 2004, Stefan O'Rear wrote:
>
> >>Sorry for not including it.
> >>
> >>>From .xsession-errors :
> >>
> >>xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> >>xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> >
> >That's normal for a server crash...
> >
> >What about /var/log/XFree86.0.log?
>
> Fatal server error:
> Caught signal 11. Server aborting
>
> >Also, apt-get install xmon and:
> >
> >nohup bash -c 'xmonui | xmond > xmond.log' &
> ># click full for the first four choosers
> >DISPLAY=:1 app
>
> This wouldn't run the app because it couldn't open the display.
*slaps head very hard*
I tested it, it didn't work. I remembered xmond does TCP/IP only (no
AF_LOCAL), so I changed it to:
nohup bash -c 'xmonui | xmond > xmond.log' &
# click full for the first four choosers
DISPLAY=127.0.0.1:1 app
It worked. I somehow forgot that change while typing.
> >then send xmond.log...
>
> It was created but was empty.
--
The world's most effective spam filter:
ln -sf /dev/full /var/mail/$USER
Reply to: