All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
Date: Wed, 10 Jun 2015 17:37:40 +0000	[thread overview]
Message-ID: <bug-90264-502-ncQIVgKW0F@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90264-502@http.bugs.freedesktop.org/>


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

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

--- Comment #12 from Ilia Mirkin <imirkin@alum.mit.edu> ---
(In reply to Matt Whitlock from comment #10)
> Whenever a context menu in Chromium fails to display correctly (shows as
> solid black instead), the following lines (or similar) are appended to the
> kernel message log:
> 
> nouveau E[chrome[5932]] multiple instances of buffer 249 on validation list
> nouveau E[chrome[5932]] validate_init
> nouveau E[chrome[5932]] validate: -22
> 
> Does not happen upon display of corrupted tooltips, only context menus.

I suspect you were using libdrm 2.4.60. Use either .59 or .61 and that
particular error will go away. That said, I also see the tooltip fail in chrome
on a GF108 (nvc0 driver) for a few versions of chrome now.

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-06-10 17:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01  3:08 [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome bugzilla-daemon
2015-05-01  3:12 ` bugzilla-daemon
2015-05-01  3:26 ` bugzilla-daemon
2015-05-01  3:37 ` bugzilla-daemon
2015-05-01  3:55 ` bugzilla-daemon
2015-05-01  4:01 ` bugzilla-daemon
2015-05-01 19:08 ` bugzilla-daemon
2015-05-01 22:16 ` bugzilla-daemon
2015-05-25 18:45 ` bugzilla-daemon
2015-06-10 12:34 ` bugzilla-daemon
2015-06-10 12:58 ` bugzilla-daemon
2015-06-10 17:33 ` bugzilla-daemon
2015-06-10 17:37 ` bugzilla-daemon [this message]
2015-06-10 19:09 ` bugzilla-daemon
2015-06-10 19:44 ` bugzilla-daemon
2015-06-10 19:57 ` bugzilla-daemon
2015-06-10 20:58 ` bugzilla-daemon
2015-06-10 21:12 ` bugzilla-daemon
2015-06-10 21:36 ` bugzilla-daemon
2015-06-10 23:34 ` bugzilla-daemon

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-90264-502-ncQIVgKW0F@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.