Hi all,
After my description and with the logs I joined earlier, can we still blame "xorg" for this bug ?
I very much suggest this be (upstream) "linux" at fault instead.
Another idea ?
Sincerely, Vécu
Hi all,
After my description and with the logs I joined earlier, can we still blame "xorg" for this bug ?
I very much suggest this be (upstream) "linux" at fault instead.
Another idea ?
Sincerely,
Vécu