All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100860] New: Dual Monitor display problem, after switching screen positions, with 4.10 Kernels
Date: Thu, 27 Apr 2017 21:56:37 +0000	[thread overview]
Message-ID: <bug-100860-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1949 bytes --]

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

            Bug ID: 100860
           Summary: Dual Monitor display problem, after switching screen
                    positions, with 4.10 Kernels
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: tobias.muhlhofer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 131105
  --> https://bugs.freedesktop.org/attachment.cgi?id=131105&action=edit
Kernel log

When switching screen positions of dual monitors, there is a display issue.
Steps to reproduce:

- Boot the system.

- Log into an Xterm session (to make things as clean as possible).

--> Screens are displayed by default as 1 left, 2 right. The xterm window is on
screen 1.

- Use xrandr --right-of to switch the screens to put 1 right of 2 (i.e. 2 left,
1 right).

--> The xterm window remains displayed on screen 1, but the system acts as if
the window were now displayed on screen 2. Through this, the mouse pointer
position is displayed accurately. That means, in order for a click to register
in the Xterm window, I have to click on the top left of screen 2, which looks
blank.

Checking xev, all mouse pointer coordinates are displayed as if screen 2 were
on the left.

Suspending the system and waking it back up fixes the problem.


Setup is FC24, 4.10 kernels (4.10.8,4.10.9,4.10.10 tried so far), video card is
Nvidia Quadro K620.

This problem did not occur with the 4.9.13 kernel (which was the last one I
used before the 4.10s).

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

[-- Attachment #1.2: Type: text/html, Size: 3366 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2017-04-27 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 21:56 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-100860-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-04-27 21:57   ` [Bug 100860] Dual Monitor display problem, after switching screen positions, with 4.10 Kernels bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-01  7:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-04  1:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100860-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.