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 21:36:31 +0000	[thread overview]
Message-ID: <bug-90264-502-24MoitWoDZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90264-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from Furkan <falaca@gmail.com> ---
I'm using Chrome 43.0.2357.124 (latest stable version).

I installed the latest Chromium build from the Ubuntu repo, which is
43.0.2357.81. However, going to chrome://gpu shows that everything is "software
only" (so the tooltips work fine).

Might be worth taking a look if maybe going from one version to the other
caused you to switch from software only to hardware-accelerated?

You mentioned the issue happened when you upgraded from 43.0.2357.73 to
44.0.2403.18. So I checked out this URL:

https://chromium.googlesource.com/chromium/src/+log/43.0.2357.73..44.0.2403.18?pretty=fuller&n=10000

And surely enough:
https://chromium.googlesource.com/chromium/src/+/4c9c8b2238012338a6395f7101d036e3634ed687

"Enable hardware acceleration for Nouveau and Stage3D".

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

[-- Attachment #1.2: Type: text/html, Size: 1951 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 21:36 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
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 [this message]
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-24MoitWoDZ@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.