Comment # 6
on bug 97796
from Uli Schlachter
By default awesome uses a visual with depth=32 for all of its windows. AFAIK (someone who can reproduce this, please test), starting awesome with the --no-argb argument (= use the root window's visual) makes these problems go away. Also, AFAIK all kinds of screenshots show the correct data. Oh and once upon a time (but couldn't reproduce) I saw Xephyr having this problem, but moving the mouse pointer across the affected area of the tasklist made the expected/real content visible (at least for the part that the mouse pointer touched). I have no clue about the server, but this sounds like software cursor "fixing" things? Also, I could be mixing several different bugs which just have similar results. At least the depth=32 might be a useful hint. Paul, do you know if --no-argb works around these problems for you?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
