From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100760] Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display
Date: Sun, 23 Apr 2017 02:31:54 +0000 [thread overview]
Message-ID: <bug-100760-8800-RfDLt62AGD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100760-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1018 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100760
--- Comment #2 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
While Zaphod is considered a legacy feature, that doesn't mean that things
should break. Just that it's unlikely to be extended to support new things.
There has recently been some bugs introduced into xserver which break
non-xrandr setups. There are also some issues in the nouveau driver. One of
those was fixed in xf86-video-nouveau 1.0.15. For the xserver issues, see bug
#100293.
I cannot comment on any bugs that happen in MATE/whatever other software as a
result of multi-screen displays. Note that these are not commonly tested. If
you can do 'DISPLAY=:0.1 xterm', then everything else is down to the X clients.
Please try the above fixes and see if they improve things. If they don't,
you're going to have to debug this, or provide sufficient info for others to
debug it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2017-04-23 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 22:39 [Bug 100760] New: Rapid flickering when an app is placed on the second Nouveau ZaphodHeads display bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-100760-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-04-22 23:45 ` [Bug 100760] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-23 2:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
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-RfDLt62AGD@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.