Bug#494267: xscreensaver forgot how to grok xrandr -o left

2009-10-07 Thread Edward Welbourne
Yay ! I did an update (on squeeze) yesterday and finally got a version of xscreensaver with this issue fixed :-) Eddy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-14 Thread Edward Welbourne
Well, for you maybe, but not for others I'm afraid. indeed - last thing before going home at the end of the day, I'm not at my brightest ! One way or another, the randr code is clearly getting it wrong. I'll see if I can help work out why. Can you send the output of the test-xinerama and

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-14 Thread Edward Welbourne
When I previously 0'd out the rotate code, else if (0 rot (RR_Rotate_90|RR_Rotate_270)) I failed to notice a matching piece of code in the HAVE_RANDR_12 stanza further down; a few judicious fputs revealed to me that the latter is the one being executed. When I 0 *it* out,

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-14 Thread Edward Welbourne
Sorry, last mail's output from test-randr and test-xinerama was bogus; I'd forgotten to go into dieplay/ and re-make them. quote src=driver/test-randr test-randr: 10:28:56: XRRQueryExtension(dpy, ...) == 115, 186 test-randr: 10:28:56: XRRQueryVersion(dpy, ...) == 1, 2 test-randr: 10:28:56:

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-14 Thread Jamie Zawinski
Ok, let me make sure I understand this: - your monitor is currently rotated 90 degrees - in that configuration, it is 1200 pixels horizontally and 1600 pixels vertically - you have RANDR 1.2 So, in that state, test-randr shows: test-randr: 10:03:45: Current Rotation:90

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-14 Thread Edward Welbourne
Does that sound right? To the extent of my limited grasp of the matter, yes ;-) Thanks for making and maintaining xscreensaver, Eddy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-13 Thread Jamie Zawinski
Well, I had someone else report that to get the right sizes, I had to do that swap width and height is RR_Rotate_* is set nonsense. But if you're still seeing it mis-rotated, then that means that on your system, it will probably work if you comment those lines out. Which means -- I have

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-13 Thread Edward Welbourne
I'm afraid that someone who actually has access to a system with RANDR and a rotatey monitor is gonna have to debug this and send me a patch... OK, that'd be me then, since I can definitely reproduce the bug. (If you try to debug this, please start with 5.07, not a multiply- patched

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-13 Thread Tormod Volden
On Wed, Aug 13, 2008 at 12:37 PM, Edward Welbourne [EMAIL PROTECTED] wrote: /quote and I can't see anything listing which development packages I need to install - any clues or hints would be welcome, apt-get build-dep xscreensaver should help you. You can also pull the Debian source from our

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-13 Thread Tormod Volden
On Wed, Aug 13, 2008 at 1:10 PM, Tormod Volden [EMAIL PROTECTED] wrote: apt-get build-dep xscreensaver should help you. You can also pull the Debian source from our git, which you can easily build using: DEB_BUILD_OPTIONS=noopt debug nostrip debuild -b -us uc Sorry, I missed the hyphen before

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-13 Thread Edward Welbourne
apt-get build-dep xscreensaver should help you. after that ./configure; make worked nicely, thank you. I exited my existing xscreensaver and fired up the one built in driver/; it promptly said: xscreensaver: WARNING: RANDR and Xinerama report different xscreensaver: screen layouts!

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-13 Thread Jamie Zawinski
On Aug 13, 2008, at 11:45 AM, Edward Welbourne wrote: The error's coming from randr_versus_xinerama_fight(), so I've changed the code to trust Xinerama instead of RANDR - and the problem's fixed :-) Well, for you maybe, but not for others I'm afraid. People who use nvidia twinview need to

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-12 Thread Edward Welbourne
Please find a 5.07-1 prelease (i386 binaries) at http://alioth.debian.org/~tormod-guest/xscreensaver/ Thank you - I've fetched and installed all five packages. Restarted xscreensaver, opened config panel to confirm it's now 5.07: but my wrong-orientation variant of the bug is still there. I

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-11 Thread Edward Welbourne
Package: xscreensaver Version: 5.05-3 Followup-For: Bug #494267 A month or three ago I turned my flat Dell screen on its side, from landscape mode to portrait mode; the last two lines of my .xsession are now: xrandr -o left exec fvwm This initially worked very nicely. Notably, xscreensaver

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-11 Thread Jamie Zawinski
Please try 5.07. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-11 Thread Edward Welbourne
Please try 5.07. Marvelously terse and imperative ;-) I've looked at the change-logs and, indeed, find: quote src=http://www.jwz.org/xscreensaver/changelog.html; 5.0710-Aug-2008 Xinerama/RANDR tweaks for old-style multi-screen. ... 5.0616-Jul-2008 Xinerama/RANDR fixes: this time for

Bug#494267: xscreensaver forgot how to grok xrandr -o left

2008-08-11 Thread Tormod Volden
On Mon, Aug 11, 2008 at 9:02 PM, Edward Welbourne [EMAIL PROTECTED] wrote: unequivocal about how difficult it is to build from source. So I may give it a blast if I can find the time, but debian maintainers are probably more experienced at this than am I ;-) At your service :) Please find a