Re: Running from XTerm Crashes X

2004-09-19 Thread Terry Carney
It worked. I somehow forgot that change while typing. This did a little better but xmond.log was still empty. However, it didn't crash but returned the following to the console instead: Gdk-ERROR **: X connection to 127.0.0.1:1 broken (explicit kill or server shutdown). The following from

Running from XTerm Crashes X

2004-09-18 Thread Terry
Hi. I am running the current Testing and am using WindowMaker as my window manager. For some time now (a year?) trying to run an X program from the command line in an XTerm often causes the X server to unceremoniously crash and cycle to the login screen and it happens to many but not all.

Re: Running from XTerm Crashes X

2004-09-18 Thread Shaul Karl
On Fri, Sep 17, 2004 at 10:50:20PM -0700, Terry wrote: Hi. I am running the current Testing and am using WindowMaker as my window manager. For some time now (a year?) trying to run an X program from the command line in an XTerm often causes the X server to unceremoniously crash and

Re: Running from XTerm Crashes X

2004-09-18 Thread Terry
On Sat, 18 Sep 2004, Shaul Karl wrote: A brief, but by no means exhaustive, list: Runs from Windowmaker: ALL Runs from command line:mozilla, gimp2, gnomesword2, xchat Crashes from command line: dillo, alsaplayer, acroread, xmms Does ~/.xsession-errors have something more? Sorry for not

Re: Running from XTerm Crashes X

2004-09-18 Thread Stefan O'Rear
On Sat, Sep 18, 2004 at 03:22:09PM -0700, Terry wrote: On Sat, 18 Sep 2004, Shaul Karl wrote: A brief, but by no means exhaustive, list: Runs from Windowmaker: ALL Runs from command line:mozilla, gimp2, gnomesword2, xchat Crashes from command line: dillo, alsaplayer, acroread,

Re: Running from XTerm Crashes X

2004-09-18 Thread Terry
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

Re: Running from XTerm Crashes X

2004-09-18 Thread Stefan O'Rear
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

Re: Running from XTerm Crashes X

2004-09-18 Thread Terry
On Sat, 18 Sep 2004, Stefan O'Rear wrote: 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. This did a little better but xmond.log was still empty. However, it didn't crash but returned