I'm using Fluxbox (on Gentoo Linux) for many years, and 1.3.7 since 2015. But in few last months it start crashing xorg-server (I don't use wayland) on keypress which is supposed to change a Workspace.
It looks like a race - this happens once in several days, but unexpected crash on a whole X it really annoying.
It doesn't matter how workspace is changed: sometimes it happens on keypress with :Workspace <number> command, sometimes on :Exec wmctrl -s <number> command.
I've tried to run wmctrl in a loop in command line without keypresses but was unable to reproduce this issue.
I've tried to run :Exec <some other command> but also was unable to reproduce this issue.
Using None Menu :Exec wmctrl -s $(< /tmp/workspace-previous ); mv /tmp/workspace{,.old}; mv /tmp/workspace{-previous,}; mv /tmp/workspace{.old,-previous} (these two files should contain numbers like 0 and 1) and keeping Menu key pressed with auto-repeat rate 30/s it usually takes about 1-30 minutes to reproduce this issue.
I've also reproduced this issue on latest master from github repo.
When this issue happens there are nothing interesting in logs - neither kernel or syslog, nor fluxbox ones - just a normal Xorg exit flow triggered by unknown reason, e.g.:
...
[ 3219.885] (II) No input driver specified, ignoring this device.
[ 3219.885] (II) This device may have been added with another device file.
[ 3924.431] (II) event16 - Logitech G502 HERO Gaming Mouse: device removed
[ 3924.472] (II) evdev: Logitech G502 HERO Gaming Mouse Keyboard: Close
[ 3924.472] (II) UnloadModule: "evdev"
[ 3924.473] (II) UnloadModule: "libinput"
[ 3924.473] (II) evdev: Microsoft Natural® Ergonomic Keyboard 4000: Close
[ 3924.473] (II) UnloadModule: "evdev"
[ 3924.473] (II) evdev: Microsoft Natural® Ergonomic Keyboard 4000: Close
[ 3924.473] (II) UnloadModule: "evdev"
[ 3924.473] (II) evdev: Power Button: Close
[ 3924.473] (II) UnloadModule: "evdev"
[ 3924.473] (II) evdev: Power Button: Close
[ 3924.473] (II) UnloadModule: "evdev"
[ 3924.736] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 3924.738] (II) Server terminated successfully (0). Closing log file.
As fluxbox itself won't change I suspect some incompatible environment changes, and in last few months main changes on my Gentoo were:
I run out of ideas how to continue debugging this issue and probably will have to replace fluxbox with some other WM - what makes me really sad. :(
Hey Alex,
have you tried to build it with
--enable-debugand starting fluxbox with e.g.fluxbox -log "$HOME/.fluxbox/log"? And maybe something is logged in~/.xsession-errors.Can you reproduce the same problem with
None Menu :PrevWorkspace 0? I think this is what your "wm-file-shuffle" does right?Last edit: crpb 2023-04-11
Thanks for the
--enable-debughint.No,
:PrevWorkspace 0isn't the same as my command, at least in case of more than 2 workspaces used - I've 24 workspaces and my command switch to previous used one, e.g. from current workspace 7 to previous workspace 20 (and then workspace 7 became "previous").Anyway, I did what you asked for - recompiled with
--enable-debug, set key config to yours and keep Menu key pressed until X exits (18 minutes this time, huh).Contents of
~/.fluxbox-errors(file where fluxbox stdout & stderr were redirected) is same as usual. When X exits I always get something like this in the file:But
~/.fluxbox-logthis time is huge because of lots of debug info (27MB). But nothing interesting there too, at a glance. Here are last 60 lines:Anything else I can do?
Update: keypress is not related to this issue.
My setup includes starting a dozen of apps from
~/.fluxbox/startup, some of them has different[Workspace]defined in~/.fluxbox/appsand take focus (browser and messengers) on start, which result in auto-switching between 2-3 workspaces while starting X. And today I got X exit/crash while executing this startup process and auto-switching workspaces.