<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - X crashes when using ARandR to rotate screen or change resolutions" href="https://bugs.freedesktop.org/show_bug.cgi?id=94258#c21">Comment # 21</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - X crashes when using ARandR to rotate screen or change resolutions" href="https://bugs.freedesktop.org/show_bug.cgi?id=94258">bug 94258</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to Eric from <a href="show_bug.cgi?id=94258#c18">comment #18</a>) Hi Eric, > Current setup: WYSE Vx0LE, Lubuntu 12.04 > Dual HP LP2065 4:3 monitors, one DVI mode, one VGA mode (DVI/VGA "Y" > adapter) 1600x1200 60hz. > > OpenChrome 0.4.158 > > I can now change resolutions using ARandR with no problems or crashes. > Thanks. > > If I try to rotate to "right" or "left", X no longer crashes, but now gives > the error that "inverted" originally gave (and still does): > XRandR failed:XRandR returned error code 1: xrandr: Configure crtc 0 failed > > So, although rotate is not working, X no longer "crashes using ARandR to > rotate screen or change resolutions", so you can technically close this bug, > unless you want to keep it as a placeholder for further rotate work. > > Thanks, > Eric. I am glad the runtime screen resize is now working. It is embarrassing that this significant of a bug went into the repository code probably due to lack of testing. As I have promised back in late February, it took time to figure out why this was happening, and to be honest, it took me a lot of time to identify the area of the code that was directly contributing to this crash. As for rotation support, I will add it to the wishlist, but I will going to have to give it a low priority since OpenChrome still has too many problems as a graphics device driver, and fixing those other problems will likely take precedence. Personally, it is my view that features not implemented should be disabled since it leads to a crash anyway, and rotation feature should be handled this way. If I read it correctly, most VIA IGPs since UniChrome Pro have hardware rotation support. If there is going to be rotation support, it will have to be via the rotation hardware. Since you think I can close the bug, I will close the bug shortly.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>