Perhaps this is fixed as it appears this is related with xrandr bug or malfunctions.
Perhaps this is fixed as it appears this is related with xrandr bug or malfunctions.