Fluxbox crashes on restart when too many windows are open

[GJones]

Or at least that seems to be the condition that causes it. Passing Fluxbox the restart signal with VLC, Dolphin, Firefox, and the KDE control center open caused it to crash, losing unsaved data.

I've not seen this on other distributions; but then, most of my experience with Fluxbox has been with 1.1.x, so I don't know if this is a problem with the current build, or an upstream bug.

[ax]

I use fluxbox for many years but I never talk about this problem for leader.
Of course, as is clear fluxbox has not been developed for a long time, thankfully now things seem to change with the release of new releases.
Honestly I do not depend on wm but since yesterday, the new release of fluxbox 1.3.2 will be available as an upgrade as soon as possible.
The changelog talks about many changes and bug fixes that make the wm very stable.

Given everything I hope you solve.
Note: Very often the crashes are caused directly by the X server and not to de and wm running on it. It would be appropriate in every case for your problem and have the debug log from Xorg to understand what is due to the problem in question.

[GJones]

Ah good point, I'd forgotten entirely about .xsession-errors. This issue doesn't occur with any WM other than Fluxbox though, so I do think it's a Fluxbox bug...Still, let's see if I can reproduce it and get an error log.

Edit: can't reproduce it any more, even with several heavy applications open. I think this was a side effect of the dreaded Intel cursor lag bug that I solved here.

[ax]

As expected was due to something else, it seemed quite impossible from my experience.

NOTE: I just compiled the new release 1.3.2 of fluxbox ... in the coming hours / days will be available for download from the official repositories.

greetings

[jayseye]

There's a logging option specific to Fluxbox, at the end of ~/.fluxbox/startup

Code: Select all

# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ''exec'' before it.
#
exec fluxbox
# or if you want to keep a log:
#exec fluxbox -log "~/.fluxbox/log"

However, un-commenting that final line caused an error for me, due either to the shorthand for home "~/" and/or to the use of double quotes. Instead, this line works, though it needs to be customized for each user:

Code: Select all

exec fluxbox -log /home/jayseye/.fluxbox/log

[ax]

that comment is just an example configuration of the config file. The symbol ~ stands for precisely the location of the home user. It should be modified for specific user regardless of not being recognized by the command fluxbox-log "."
I do not see what can hit with the problem that you are complaining. In any case was resolved. Thanks for reporting anyway.

[jayseye]

Hello, ax -

Actually I was offering a solution re generating a Fluxbox-specific logfile as mentioned by GJones, rather than filing a complaint. Instead, was pointing out what really needs to be done, rather than blindly following the suggestion in the startup file.

Ah good point, I'd forgotten entirely about .xsession-errors. This issue doesn't occur with any WM other than Fluxbox though, so I do think it's a Fluxbox bug...Still, let's see if I can reproduce it and get an error log.

Also looking forward to testing the updated Fluxbox package -- thanks!