All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 195321] nouveau?/DRI3?: dual monitors unusable without running compton --paint-on-overlay
Date: Sat, 10 Jun 2017 19:24:43 +0000	[thread overview]
Message-ID: <bug-195321-2300-Dbz3mmieAb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-195321-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=195321

--- Comment #6 from Jimi (JimiJames.Bove@gmail.com) ---
Well, that's some obscure yet vital information. Why does this site even have
the option to report bugs in a category that nobody pays attention to, rather
than directing a potential bug reporter to the right place? And before you say
that nouveau would've pointed me to the right spot, keep in mind I have no
reason yet to suspect this is even a bug with nouveau (though it is a
possibility), and have a lot of reason to suspect it's a bug with the kernel,
since upgrading and downgrading my kernel changes its behavior.

Here's the new bug report in the proper place:
https://bugs.freedesktop.org/show_bug.cgi?id=101372

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2017-06-10 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  7:22 [Bug 195321] New: nouveau?/DRI3?: dual monitors unusable without running compton --paint-on-overlay bugzilla-daemon
2017-04-11  8:04 ` [Bug 195321] " bugzilla-daemon
2017-04-11  8:09 ` bugzilla-daemon
2017-05-18 23:41 ` bugzilla-daemon
2017-06-08 16:37 ` bugzilla-daemon
2017-06-08 16:58 ` bugzilla-daemon
2017-06-10 19:24 ` bugzilla-daemon [this message]

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-195321-2300-Dbz3mmieAb@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.