> kls wrote: > > Package: xscreensaver > > Version: 5.03-3.1 > > Severity: normal > > > > > > +-----+-+ +----+-+ > > |both |1| |both| | > > +-----+-+ +----+ | > > | 2 | | a | > > +-----| +------+ > > > > (e.g. > > 1 - 1440x900 - widescreen display > > 2 - 1280x1024 - conventional display > > a - 1024x768 - laptop > > b - 800x600 - external projector) > > > > Xrandr 1.2 supports overlapping displays (e.g. the ascii art above); > > causing xscreensaver to not chose a correct (completely obscuring) set > > of windows, so we have the same reveal issue as in #428797. This may > > actually be the same thing, since I was able to switch my xrandr > > resolution right now and have xscreensaver choose a (different) wrong > > window to blank. > > Hi kls, I read your email but since I do not have any dual display > environment to test it I can confirm or denied that this bug exists, any > help will be well received.
Ok. For example, if I run xscreensaver with "Verobse: True" in the configuration file, and then play with xrandr, I get the following log: xscreensaver: 11:30:45: 0: xscreensaver-gl-helper: GL visual is 0x25. xscreensaver: 11:30:45: 1: xscreensaver-gl-helper: GL visual is 0x25. xscreensaver: 11:30:45: running on display ":0.0" (2 Xinerama screens). xscreensaver: 11:30:45: vendor is The X.Org Foundation, 10400000. xscreensaver: 11:30:45: useful extensions: xscreensaver: 11:30:45: MIT Screen-Saver <-- not supported at compile time! xscreensaver: 11:30:45: Shared Memory xscreensaver: 11:30:45: Double-Buffering xscreensaver: 11:30:45: Power Management xscreensaver: 11:30:45: GLX xscreensaver: 11:30:45: XF86 Video-Mode xscreensaver: 11:30:45: Xinerama xscreensaver: 11:30:45: Resize-and-Rotate xscreensaver: 11:30:45: screen 0 non-colormapped depths: 16. xscreensaver: 11:30:45: Xinerama layout: xscreensaver: 11:30:45: + 0/0: 2048x900+0+0 xscreensaver: 11:30:45: 1/0: 1152x900+0+0 xscreensaver: 11:30:45: selecting RANDR events xscreensaver: 11:30:45: consulting /proc/interrupts for keyboard activity. xscreensaver: 11:30:45: 1: xinerama vp: 1152x900+0+0. xscreensaver: 11:30:45: 0: visual 0x23 (TrueColor, depth: 16, cmap: default) xscreensaver: 11:30:45: 0: saver window is 0x600001. xscreensaver: 11:30:45: 1: xinerama vp: 1152x900+0+0. xscreensaver: 11:30:45: 1: saver window is 0x600005. xscreensaver: 11:30:45: selecting events on extant windows... done. xscreensaver: 11:30:45: awaiting idleness. Then I run xrandr --output VGA2 --mode 1024x768 xscreensaver: 11:31:50: 0: no-op screen size change event (2048x900) xscreensaver: 11:31:50: 1: resize xinerama from 1152x900+0+0 to 1024x768+0+0 xscreensaver: 11:31:50: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:31:50: 0: resize 0x600001 from 1152x900+0+0 to 1024x768+0+0 xscreensaver: 11:31:50: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:31:50: 1: resize 0x600005 from 1152x900+0+0 to 1024x768+0+0 The 4th line (0: resize 0x600001 from 1152x900+0+0 to 1024x768+0+0) is wrong. screen 0 is still 2048x900 (as the line at the top shows). Then I run xrandr --output VGA1 --mode 1152x864 xscreensaver: 11:40:52: 0: no-op screen size change event (2048x900) xscreensaver: 11:40:52: bad craziness: xinerama screen count changed from 2 to 1! xscreensaver: 11:40:52: 0: resize xinerama from 2048x900+0+0 to 1024x768+0+0 xscreensaver: 11:40:52: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:40:52: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:40:52: 0: screen size changed from 1024x768 to 1152x900 xscreensaver: 11:40:52: 0: resize xinerama from 1024x768+0+0 to 1152x900+0+0 xscreensaver: 11:40:52: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:40:52: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:40:52: 0: no-op screen size change event (1152x900) xscreensaver: 11:40:52: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:40:52: 1: xinerama vp: 1024x768+0+0. The 3rd line (0: resize xinerama from 2048x900+0+0 to 1024x768+0+0) is wrong, although the 6th and 7th lines might make up for it. Then I run xscreensaver-command -activate xscreensaver: 11:43:30: ACTIVATE ClientMessage received. xscreensaver: 11:43:30: blanking screen at Sun Dec 2 11:43:30 2007. xscreensaver: 11:43:30: mouse is on screen 0 of 2 xscreensaver: 11:43:30: 0: grabbing keyboard on 0x5e... GrabSuccess. xscreensaver: 11:43:30: 0: grabbing mouse on 0x5e... GrabSuccess. xscreensaver: 11:43:30: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:43:30: 1: xinerama vp: 1024x768+0+0. xscreensaver: 11:43:30: 0: visual 0x23 (TrueColor, depth: 16, cmap: 64) xscreensaver: 11:43:30: 0: saver window is 0x60000a. xscreensaver: 11:43:30: 0: destroyed old saver window 0x600001. xscreensaver: 11:43:30: 0: spawning "rotor -root -count 15 -cycles 2 -delay 40000 -ncolors 1 -size 4" in pid 32739. xscreensaver: 11:43:30: 1: visual 0x23 (TrueColor, depth: 16, cmap: 64) xscreensaver: 11:43:30: 1: saver window is 0x60000c. xscreensaver: 11:43:30: 1: destroyed old saver window 0x600005. xscreensaver: 11:43:30: 1: spawning "rotor -root -count 15 -cycles 2 -delay 40000 -ncolors 1 -size 4" in pid 32740. xscreensaver: 11:43:32: unblanking screen at Sun Dec 2 11:43:32 2007. xscreensaver: 11:43:32: 0: killing pid 32739 (rotor) xscreensaver: 11:43:32: 1: killing pid 32740 (rotor) xscreensaver: 11:43:32: 0: ungrabbing mouse (was 0x5e). xscreensaver: 11:43:32: 0: ungrabbing keyboard (was 0x5e). xscreensaver: 11:43:32: starting de-race timer (10 seconds.) xscreensaver: 11:43:32: awaiting idleness. xscreensaver: 11:43:32: 0: child pid 2739 (rotor) terminated with signal 15. xscreensaver: 11:43:32: 1: child pid 2740 (rotor) terminated with signal 15. xscreensaver: 11:43:42: de-race completed. It's not clear to me why line 6 and 7 are identical. In any case, I only see one 1024x768 window containing the rotor xscreensaver, so I guess the two are on top of each other, both at 1024x768+0+0 (instead of 1152x900+0+0 and 1024x768+0+0) Is this useful? - kls -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
