https://bugs.freedesktop.org/show_bug.cgi?id=90264
Furkan changed:
What|Removed |Added
CC||brianp at vmware.com
Component|Drivers
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #18 from Furkan ---
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" (s
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #17 from Matt Whitlock ---
(In reply to Furkan from comment #16)
> What do those revision numbers represent? Are they binary builds? They don't
> look like svn/git commits.
They're Subversion revisions, which is what Chromium's bisec
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #16 from Furkan ---
What do those revision numbers represent? Are they binary builds? They don't
look like svn/git commits. If we have a commit range, we can view the changelog
between them by plugging the revision numbers into one of
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #15 from Matt Whitlock ---
(In reply to Furkan from comment #14)
> For those of you who are using nouveau, does the problem go away after
> reverting the mesa commit that I bisected?
>
> http://cgit.freedesktop.org/mesa/mesa/commit/
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #14 from Furkan ---
For those of you who are using nouveau, does the problem go away after
reverting the mesa commit that I bisected?
http://cgit.freedesktop.org/mesa/mesa/commit/?id=95073a2dca03a48f4c77bc846a4a6d1f0eb81ae6
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #13 from Matt Whitlock ---
(In reply to Ilia Mirkin from comment #12)
> (In reply to Matt Whitlock from comment #10)
> > nouveau E[chrome[5932]] multiple instances of buffer 249 on validation list
> > nouveau E[chrome[5932]] validate_
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #12 from Ilia Mirkin ---
(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 mes
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #11 from Matt Whitlock ---
My bug may have a different cause, as downgrading to Chromium 43.0.2357.73
restored correct behavior.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #10 from Matt Whitlock ---
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 insta
https://bugs.freedesktop.org/show_bug.cgi?id=90264
Matt Whitlock changed:
What|Removed |Added
CC||freedesktop at mattwhitlock.na
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #8 from AP ---
I can confirm this issue. Running the latest Mesa built from Pali's 12.04
backports PPA (https://launchpad.net/~pali/+archive/ubuntu/graphics-drivers) I
am seeing the same kind of graphical corruption in tooltips: They
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #7 from falaca at gmail.com ---
FWIW, the corruption doesn't occur on my laptop with Intel graphics (w/
hardware accelerated compositing, just like on my desktop). Also, on my desktop
when I set LIBGL_ALWAYS_SOFTWARE=1 and the flag in
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #6 from Jose P. ---
I should add, I get "Hardware Accelerated" because I enabled "Override software
rendering list" ( chrome://flags/#ignore-gpu-blacklist ) in Chromium...
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #5 from Jose P. ---
I can confirm this bug, that I've seen text from other processes in the
corrupted tooltips, and that Chromium + LIBGL_ALWAYS_SOFTWARE=1 does not show
corruption.
With LIBGL_ALWAYS_SOFTWARE=1, in Chromium ( chrome:/
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #4 from falaca at gmail.com ---
When I set LIBGL_ALWAYS_SOFTWARE=1, chrome://gpu shows "Software only" for all
the features, and the GL_RENDERER string is "Gallium 0.4 on llvmpipe (LLVM 3.6,
128 bits)".
It does appear to be a bug some
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #3 from Michel Dänzer ---
(In reply to falaca from comment #2)
> Michel, I just tested it right now, and there is no corruption when I set
> LIBGL_ALWAYS_SOFTWARE=1.
Does Chrome enable GPU acceleration in that case as well? If yes,
https://bugs.freedesktop.org/show_bug.cgi?id=90264
--- Comment #2 from falaca at gmail.com ---
Michel, I just tested it right now, and there is no corruption when I set
LIBGL_ALWAYS_SOFTWARE=1.
The screenshot I linked to is from the glowing-bear web IRC client, and I just
need to mouse over 2 or
https://bugs.freedesktop.org/show_bug.cgi?id=90264
Michel Dänzer changed:
What|Removed |Added
Component|DRM/Radeon |Drivers/Gallium/radeonsi
Ver
https://bugs.freedesktop.org/show_bug.cgi?id=90264
Bug ID: 90264
Summary: [Regression, bisected] Tooltip corruption in Chrome
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
20 matches
Mail list logo
