UPDATE: After further investigation, this problem (so far) has not happened with AwesomeWM. I suspect it might be a particular problem with SpectrWM.
Thank you, Lewis I. On Tue, Nov 16, 2021 at 6:27 AM Matthieu Herrb <matth...@herrb.eu> wrote: > On Mon, Nov 15, 2021 at 08:37:14PM +0000, Lewis ingraham wrote: > > > System Crashes and reboots on error. Currently on 7.0-current, I also > > wanted to note that this happens on 7.0 Release as well. Happens when > > browsing using firefox with smtube playing in the background as well as > > having htop running for system monitoring. System packages are upgraded > to > > the latest version as well as system base upgraded to latest snapshot. I > > use the spectrwm window manager with these applications and options: > > picom -CG --refresh-rate 60 --backend glx --glx-no-stencil > > --unredir-if-possible --unredir-if-possible-delay 4 --no-fading-openclose > > --xrender-sync-fence --vsync > > redshift > > feh --recursive --bg-fill --randomize /home/louie/Pictures/Wallpaper/ > > xfce4-terminal -e htop > > firefox > > smtube > > > > Thank you, > > Lewis I. > > Hi, in the Xorg.0.log and Xorg.0.log.old files you provided there is > no trace of an actual crash of the X server. It would be a line like > that: > > (EE) Caught signal 11 (Segmentation fault). Server aborting > > So this seems to indicate that its spectrwm that exited for some (bad) > reason. I've already got a report showing that jwm is causing this > kind of issue. > > Could you try with another window manager (fvwm, cwm, or one from > ports) and see if you can reproduce ? > > Or may be you just restarted the X server twice after a crash and lost > the Xorg.0.log.old with the actual error. > > Please tell me what you can find. > -- > Matthieu Herrb >
