Hi, This was causing me problems too, and since I had a reproducible test case I attacked the problem with git bisect. The offending commit is http://git.fluxbox.org/?p=fluxbox.git;a=commitdiff;h=4a7a143713c7febe7d3a7df9c044ed767b8bd3c6
I worked with ak|ra from freenode/#fluxbox to dig into the problem further. The strace output I got was a little strange -- fluxbox was in a tight loop suffering SIGFPE, as can be seen from the strace output [1]. A debug log from the fluxbox binary at this commit didn't show much useful either [2], nor did a backtrace from the binary as it was running [3]. However, I created a "rollback" of the above commit, "fixed" a few problems by deleting code that referenced old variables, and rebuilt. This seemed to "fix" the problem, but I'm not sure that what I've done is going to be 100% correct. I've created a patch against fluxbox master as of commit df2f51b7 anyway [4], in the hopes that it will get things moving. Hope this helps! --alex [1]: http://www.pl0rt.org/~alex/fluxbox.trace.bz2 [2]: http://www.pl0rt.org/~alex/fluxbox.debug.log [3]: http://pastebin.ca/1936527 [4]: http://www.pl0rt.org/~alex/0001-Attempt-to-revert-4a7a1437.patch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
