[xorg-bugzilla-noise] [Bug 419] New: XF86VidModeGetModeLine reports wrong mode when laptop is in docking station

[bugzilla-daemon at pdx.freedesktop.org]

http://pdx.freedesktop.org/cgi-bin/bugzilla/show_bug.cgi?id=419

           Summary: XF86VidModeGetModeLine reports wrong mode when laptop is
                    in docking station
           Product: xorg
           Version: unspecified
          Platform: PC
               URL: http://plausible.org/andy/xvp.c
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Server/general
        AssignedTo: xorg-bugzilla-noise at freedesktop.org
        ReportedBy: andy at plausible.org


I reported this a while back to the XFree86 bugzilla.  It was closed
there without resolution, and is still present in the current xorg
server in the FC2 rawhide distribution, so I thought I'd ping you guys
again.  Comments in the original bugs
(http://bugs.xfree86.org/show_bug.cgi?id=838,
http://bugs.xfree86.org/show_bug.cgi?id=421) indicate that this is a
design issue that needs to be addressed.

===

The XServer properly (and surprisingly) understands the difference between the
1024x768 LCD display on my IBM T30 laptop and the monitor to which it is
attached via the port replicator.  Starting up the server while docked results
in a nice 1400x1050 desktop, while initialization without the monitor attached
ejects all the unsupported modes and drops down to 1024x768.

However, xscreensaver on the large monitor still displays itself into only a
1024x768 window; very strange indeed.

I tracked this down to the fact that xscreensaver uses XF86VidModeGetModeLine
and XF86VidModeGetViewPort to get the display size (so that it displays only one
"screen worth" of information in virtual desktop mode) instead of the more
pedestran DisplayWidth/DisplayHeight macros (which return the correct results) 
The current mode line reported while docked is, in fact, a 1024x768 mode.  This
has to be wrong.

The link points to a trivial C program I wrote to demonstrate the issue.  It
produces the following results, even while the screen is demonstrably set to a
higher resolution mode:

m.hdisplay = 1024
m.hsyncstart = 1040
m.hsyncend = 1176
m.htotal = 1344
m.hskew = 0
m.vdisplay = 768
m.vsyncstart = 770
m.vsyncend = 776
m.vtotal = 806
m.flags = 0x80000000
m.privsize = 0
dotClock = 65000
vpx = 74
vpy = 0
DisplayWidth(d, 0) = 1400
DisplayHeight(d, 0) = 1050



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.