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 100760] New: Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display
Date: Sat, 22 Apr 2017 22:39:02 +0000	[thread overview]
Message-ID: <bug-100760-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 100760
           Summary: Rapid flickering when an app is placed on the second
                    Nouveau ZaphodHeads display
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: mrj-ejQy8aU/RJumpXlQD71PVDSf8X3wrgjD@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

For many years I've configured my second monitor as a separate X display
because this allows the monitors to have an independent sets of virtual
desktops. With five virtual desktops on each monitor, I could select and
display 25 combinations instead of the five with Xinerama.

This worked fine with the "separate X displays" mode of the proprietary Nvidia
driver. But eventually the second display couldn't display a background image
(black only). Later, apps started from a panel or terminal on the second
display would come up on the first unless I set the DISPLAY variable to :0.1 on
the command lines of both launchers and terminal commands. I could live with
both of these problems.

When the proprietary Nvidia driver no longer supported my graphics card in the
latest X, I moved to Nouveau, using the ZaphodHeads option to get the
equivalent of the "separate X displays" mode. This worked, though I still had
the same problems with getting stuff to appear on the second display.

This was with Fedora 23. I've just upgraded to Fedora 25, and although the
second X monitor and display still comes up (black only, but a pointer can be
moved around it), nothing can be placed on it. If I run "DISPLAY=:0.1
mate-terminal" on the first display, the terminal does appear on the second,
but there is a rapid flickering of both displays, sometimes ending in a machine
crash, and the new terminal cannot be used. This happens with both Mate and
Gnome 3.

Xinerama mode (empty xorg.conf) works fine, though of course I've now got only
five instead of 25 virtual desktop combinations.

The current Fedora 25 Nouveau version is xorg-x11-drv-nouveau.x86_64
1:1.0.14-2.fc25, and the Kernel version is 4.10.10-200.fc25.x86_64.

* Is this a Nouveau problem?
* Is this a known problem?
* Is this unlikely to be fixed because "Zaphod mode is a legacy feature"
https://bugs.freedesktop.org/show_bug.cgi?id=99103#c6 ?
* Is there another way to get dedicated sets of virtual desktops for each
monitor?

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

[-- Attachment #1.2: Type: text/html, Size: 4324 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-22 22:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-22 22:39 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-100760-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-04-22 23:45   ` [Bug 100760] Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-23  2:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-23  5:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-23 12:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-01  2:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-01 13:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-01 13:45   ` 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-100760-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.