[Bug 67846] New: Using 2 screens impossible again with gen3

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Aug 6 15:02:50 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=67846

          Priority: medium
            Bug ID: 67846
          Assignee: chris at chris-wilson.co.uk
           Summary: Using 2 screens impossible again with gen3
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: sergio.callegari at gmail.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: Driver/intel
           Product: xorg

Hi,

using the latest intel drivers and mesa from git, with kernel 3.10.5, it looks
like gen 3 in two screen configurations is broken again.  But maybe, also unity
has to do with it.

In the past it was perfectly possible to use gen3 with two screens and unity,
provided that the overall size taken by the two screen was within 2048x2048
pixels.  In practice, this could often be achieved by putting the second screen
above or below the main screen, since putting it on the side caused the virtual
size to exceed the limits.

Now, when the second screen is connected, unity happily puts it to the side of
the main one, the graphics card limits are exceeded and the compositor and
window manager dies. Weird enough, the applications survive and you can still
see their windows, but obviously without decoration.

Interestingly, using xrandr from command line to put the screens one above the
other and restarting the compositor often works.

Now I wonder where is the problem?

Is it xrandr that fails to communicate the max overall size? (can it do so,
btw?). Is it unity who ignores some information and puts the windows side to
side?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20130806/af3cd90a/attachment-0001.html>


More information about the intel-gfx-bugs mailing list