Comment 12 for bug 336721

Revision history for this message
TJ (tj) wrote :

I've not got a problem with languages - I'm on the kernel-team - so I have pretty much turn my hand to anything. I just didn't fancy having to figure out the X 'stuff' on top of everything else I'm currently doing :0

xwininfo doesn't show anything obvious. I ran it from both screens, and tried prefixing DISPLAY=:0.X in case it made a difference but each iteration reports the same results:

DISPLAY=:0.1 xwininfo -root -display :0.0

xwininfo: Window id: 0x32b (the root window) (has no name)

  Absolute upper-left X: 0
  Absolute upper-left Y: 0
  Relative upper-left X: 0
  Relative upper-left Y: 0
  Width: 1280
  Height: 800
  Depth: 24
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x20 (installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners: +0+0 -0+0 -0-0 +0-0
  -geometry 1280x800+0+0

DISPLAY=:0.1 xwininfo -root -display :0.1

xwininfo: Window id: 0x32d (the root window) (has no name)

  Absolute upper-left X: 0
  Absolute upper-left Y: 0
  Relative upper-left X: 0
  Relative upper-left Y: 0
  Width: 1280
  Height: 1024
  Depth: 24
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x1a3 (installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners: +0+0 -0+0 -0-0 +0-0
  -geometry 1280x1024+0+0