Sometimes newly opened windows (in case of Krusader almost always) don't have window decoration buttons rendered at all, not even their background, instead there is transparent rectangle (until window becomes active again, for example after minimizing and activating it, resizing doesn't help). This happens only with Oxygen so far (Plastic works fine), this is new issue in 4.11. Reproducible: Sometimes Steps to Reproduce: 1. Open Krusader window. Actual Results: Usually window decoration buttons are missing. Expected Results: Decoration should be rendered correctly.
Created attachment 82078 [details] Correct and incorrect rendering in case of Krusader.
Cannot reproduce. Most likely a kwin issue. Will investigate. Hugo
... adding kwin crew in case they have further insight
iirc from the other bug, you're on fglrx, right? *** This bug has been marked as a duplicate of bug 323065 ***
(In reply to comment #4) > iirc from the other bug, you're on fglrx, right? Yeah, but I only get (sometimes) missing buttons and once (just few minutes ago) kind of inset shadow on window decoration.
Check the attached screenshots and comments about the issue progression with driver releases and th relation to chaning the maximization state. Also the breaking commit was determined (just not *why* it breaks) - in case you can roll back git to it (it can not be reverted individually, unfortunately)
For sure this is the same issue, and yes, it seems to be somehow related to maximization state as for example Opera or Firefox show that issue only if restored from maximized state, missing only close, icon and show on all desktops. Also I've just noticed that indeed shadow is sometimes missing too... I'm using Catalyst 13.8 beta2. It's not big deal, since it is easy to "fix" it (hover over buttons or deactivate window) but would be nice to get it fixed somehow. ;-)
###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago: file /builds/slave/rel-m-rel-xr_l64_bld-000000000/build/toolkit/xre/nsX11ErrorHandler.cpp, line 157 ###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago: file /builds/slave/rel-m-rel-xr_l64_bld-000000000/build/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Most likely, the application must be tagged as an XUL application. (which it is) Will give it a shot.
(In reply to comment #8) > ###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for > operation); 4 requests ago: file wrong bug?
yes ! sorry !(In reply to comment #9) > (In reply to comment #8) > > ###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for > > operation); 4 requests ago: file > > wrong bug? yes ! sorry !
(In reply to comment #10) > yes ! sorry ! Why? I recently fixed an amarok bug from 2003 by messing up review and bug ticket - shit happens ;-)