Version: (using KDE KDE 3.4.0) Installed from: SuSE RPMs When rotating the image 90 degrees does not resize the window. So if I rotatate the screen left, I get a black border. The desktop should be resized to fit the whole screen. Picture Normal screen with full screen _____ | | | | ----- Rotated screen ----- | || | || ----- The right part is black. This is with dual screen, I havent tried it with a single screen. I do have xinerama turned off. With xinerama on you cant rotate at all. But this apparently a limitation of the xserver.
I forgot to say that I tried rotation in fwmv and in windowmaker and it works correctly in those. So I am quite sure it is a KDE specific problem.
Created attachment 16150 [details] Configuration file for X-Server
Created attachment 16151 [details] My config
i can confirm this... I'm using kde 3.5.2 with ONE Syncmaster 960BF. Trying to change the rotation with "xrandr -o left" brings a black border at the vertical bottom. The Problem doesn't occure whe starting kde with 'Option "Rotate" "CCW"' in xorg.conf
Can also confirm this bug for 3.4.3 and 3.5.2. Here also, if I save the option and restart kde, it will not fail.
I have that problem too. I use KDE 3.5.5 When I use randr -o left (or krandrtray I have a missbehaviour of the kicker. You can see that in Attachment Id=19761 http://bugs.kde.org/attachment.cgi?id=19761&action=view When I add 'Option "Rotate" "CCW"' to my xorg.conf, it works but then the xrandr extension "is missing". Is someone working on that problem? Thanks
*** This bug has been confirmed by popular vote. ***
This works for me now with 3.5.5.
Not for me. Can you e-mail what else you have been changing? bugs-kde/at/creatu.de
Just want to say: this bug seems to be introduced again in 3.5.7. I'm using gentoo and RandR left orientation. At least one other gentoo user can reproduce this bug (https://bugs.gentoo.org/show_bug.cgi?id=183721). This bug does not occur in 3.5.6. Other WMs work as expected. Any thoughts, patches...?
Created attachment 21183 [details] randr fix For me, it looks like a xlib or qt problem. DisplayWidth and DisplayHeight reports wrong (old) values. The attached patch fixed (svn diff).
patch is against branches/qt/3.3/qt-copy.
Created attachment 21218 [details] screenshot with patched qt after rotating left I experience the same problem with KDE 3.5.7, didn't test previous versions, had CRT that time :) After applying the patch to qt-3.3.8, restarting X, and rotating left, I get this - background picture now stretches to the previously black space, but the panel is still not at the border. But if I hide it, the window will maximize fully, so panel seems the only problem so far...
Created attachment 21219 [details] screenshot with patched qt after rotating back to normal see how the panel stays too short... only change of resolution sets it correctly for that resolution... but then a change back to the original resolution won't update its position and size (so if you change to smaller resolution and then back, it's above the bottom and too short). Looks like once a resolution was rotated, it becomes and stays somehow "tainted"
can't reproduce your problem. are you sure kicker used the patched library?
Thanks Robert. I've tried your patch and it behaves now the right way. Also can't reproduce Vlastimil's kicker problem.
Created attachment 21244 [details] much simpler fix
reopen https://bugs.freedesktop.org/show_bug.cgi?id=2965
Does that mean your patch is just a workaround and won't be needed after libXrandr is fixed?
Yes, currently using a clean qt-copy and a libxrandr with reverted patch. Work fine. I think this bug can be closed as invalid.
Sorry, I messed up with my X-Servers. This issue is a result of an incorrect behavior of xserver 1.3 and is fixed in git since 03.04.2007. This patch is a workaround until new xserver released. https://bugs.freedesktop.org/show_bug.cgi?id=2965 closed as invalid.
I've not understand if this bug is valid or not. Please close it if is no more valid. Thanks!
I'm closing this: 1) no feedback since my last comment 2) from the previous comment it seems that the problem has been fixed. Please reopen if the bug is still valid. Thanks!