On Mon, Aug 14, 2017 at 09:31:43AM -0700, Ayaka Koshibe wrote: > > No one asked yet, but why is X dying ? Is there anything interesting > > in /var/log/Xorg.0.log ? > > As far as X is concerned, it's just exiting normally. In my Xorg.0.log: > > [ 12384.156] (II) UnloadModule: "ws" > [ 12384.156] (II) UnloadModule: "kbd" > [ 12384.515] (II) Server terminated successfully (0). Closing log > file.
It woud be the lines just above those three that show if the X server got a signal... If not, it means that it is the window manager that exited (probably because he got the signal...). If you're using xenodm, you may find some information in ~/.xsession-errors or /var/log/xenodm.log. Otherwise get the output of startx in a file like that: $ startx > x.log 2>&1 > > > I fail to see a connection with X there, so I'm wondering if you're > > running some strange window manager setup that gets killed by the > > signal sent to the application or if it's more weird. > > I've also made X exit on a fresh install with no custom setup. Strange, normally fvwm doesn't die if one of its clients crashes, and iircs runs them in separate process groups to avoid being killed by a signal sent to a process group. Using ktrace there would help, at the expense of gigantic ktrace.out files if run on fvwm, the X server or iperf. -- Matthieu Herrb
