fluxbox compiled with USE truetype will die with the following when an xterm or mozilla is launched: fluxbox: Font.cc:410: unsigned int FbTk::Font::getTextWidth(Display *, const char *, unsigned int) const: Assertion `m_font.fontstruct' failed. USE="-truetype" seems to take care of this.
did you compile X with "truetype" -- that should give you anti-aliasing. that's all the fluxbox "truetype" patch gives you too, is antialiasing.
Yeah, I have the default 1.1a USE settings; truetype is usually on.
fluxbox -antialias does that work?
Same problem with -antialias though it is a bit prettier before it dies. Let me narrow it down a little bit: - rm -rf $HOME/.fluxbox - log in - switch style to "Outcomes" - log out - log in - start xterm That will do it with or without the -antialias flag in use. Again, USE="-truetype" when emerging fluxbox takes care of this bug.So, the interaction of (at least) the Outcomes style and the antialias patch causes the abort I spoke of. If you leave fluxbox in its default style you don't get the abort.
Can you test the newest release of fluxbox for this issue? though actually the AA stuff is out for temporary, some themes are know to have issues with AA though which will be added back soon. Mainly this is a vendor issue Please contact the flubox people though the AA is not offically supported by anyone at the moment.. Do you want me to keep this bug open tell it is fixed? Naz
Okay, I thought I took care of this. Apparently not. I did try the latest fluxbox and could no longer reproduce the problem. Thanks.
