Switch to `--no-argb` flag by default in the next (major?) release?
actionless opened this issue · comments
argb mode (default now):
- not often used by other window managers, so due to low level of testing - it often bugs on certain combination of hardware, driver version, X version etc
no-argb mode:
- can't use compositor in this mode
idk, mb for such sort of stuff we could employ user surveys, to figure out which of two configurations is more popular - as it might help to reduce often bug reports caused by aforementioned driver issues
my personal idea for the solution is to have multiple /usr/share/xsession (with --no-argb flag and without), and so i recommend to populate default awesome session with --no-argb flag, but add second session without it (and name it "AwesomeWM (ARGB mode)"