Dan Espen <dan1es...@gmail.com> writes: > hw <h...@adminart.net> writes: > >> Dan Espen <dan1es...@gmail.com> writes: >> >>> hw <h...@adminart.net> writes: >>> >>>> Dominik Vogt <dominik.v...@gmx.de> writes: >>>>> No, in the output of the X server, wherever that goes. >>>> >>>> After trying to get systemd to create log files, it apparently goes into >>>> /var/log/Xorg.0.log (where it might have gone to before). Alas, no >>>> output is added to the log file when I use this option and create >>>> windows. >>> >>> It's pretty unlikely the window manager output would go there. >>> It's much more likely to be somewhere like: >>> >>> .xsession-errors >>> >>> in your home directory. >> >> Hm, I have this file --- last modified in 2014. Hm. .xsession is from >> 1996 (I better figure out what that does), .xsel.log from 2015, and I >> can remove .xsession-errors and .xsel-log. >> >> So where else might this output go? > > Maybe if you mentioned the distro you run and the run level you boot to.
Fedora 28, booting to console > I'd expect something in $HOME, /tmp, or perhaps /var/tmp. I expected Xorg.0.log in /tmp, but it is in /var/log. Nothing related is in /var/tmp, and I haven't found anything in $HOME. > If you use a .xinitrc you can have the WM output directed where ever > you like otherwise the distro will pick a place. I tried that by redirecting the output of fvwm into a file from within .xinitrc. The file was created buy remained empty. Hm, do I need to redirect fvwms stdderr, too? I think I only redirected stdout. Or does the module create its own output that needs to be redirected when the module is being started?
