I just got an answer in there: "This is a limitation due to the way xrandr works. It uses a single surface for all enabled displays rather than one surface per display. The display hardware has alignment requirements that can cause this situation since we align the start address down. The per-crtc pixmaps work should fix the issue when it finally goes into the xserver."
Now I have a doubt on what's the best procedure to deal with this. Should we leave this bug report open until xrandx 1.4 is in ubuntu and the problem is actually fixed, or it's declared as closed? In my opinion, the bug should be kept open until the moment it's actually fixed, even if waiting for upstream. ** Bug watch added: freedesktop.org Bugzilla #58652 https://bugs.freedesktop.org/show_bug.cgi?id=58652 ** Also affects: xserver-xorg-driver-ati via https://bugs.freedesktop.org/show_bug.cgi?id=58652 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085338 Title: One pixel column that belongs in one monitor shows up in the other instead To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/1085338/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
