Perhaps I am just doing something wrong but with xrandr both of my screen always have the same position either 0x0 or 1280x0. They are both DVI TFTs at 1280x1024 made by HP. I tried xrandr --auto and xrandr --output DVI-I_2/digital --left-of DVI-I_1/digital and finally just trying to set the position of one screen with xrandr --output DVI-I_2/digital --pos 0x0. As mentioned both screens always had the same position even when I explicitly set one of them to a different position then both would change. Here are the logs associated with it.
Created attachment 12788 [details] x just started
Created attachment 12789 [details] xrandr -q
Created attachment 12790 [details] xrandr --output DVI-I_2/digital --left-of DVI-I_1/digital
Created attachment 12791 [details] xrandr --output DVI-I_2/digital --right-of DVI-I_1/digital
Created attachment 12792 [details] xrandr --output DVI-I_2/digital --pos 0x0 the command lines I entered as Decription are similar but not verbatim to what I actually did (might have switched the output name's order)
Created attachment 12793 [details] the config file
Created attachment 12801 [details] logverbose_after_right_of
Created attachment 12802 [details] logverbose_after_DVI1_pos_0_0
Created attachment 12803 [details] logverbose_after_DVI2_pos_1280
You didn't print the output of 'xrandr -q' after each invocation (of which you were obviously talking, because that's these offsets are actually printed). But I assume that you are using a standard xrandr application - not the latest git version. It has several bugs fixed, and is easy to compile. I have just verified that my patched version is able to unclone when the same resolution, but a different offset is given. This is actually a good test for the test case I'm writing. I have *no* idea why no other driver was running into these problems - maybe no other driver allows crtc cloning, which happened in this case. Both outputs were driven by the same crtc (because they accepted exactly the same mode), and xrandr wasn't able to unclone them. Closing as FIXED, unless you're hitting something else here, then please reopen.
I tested git version of xrandr and the problem went away as Matthias said. The version of xrandr with openSUSE 10.3 was broken so maybe you want to fix that in 10.3 or not.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.