https://bugs.freedesktop.org/show_bug.cgi?id=110721
Michel Dänzer changed:
What|Removed |Added
CC||freedesk...@trummer.xyz
--- Comment #22
https://bugs.freedesktop.org/show_bug.cgi?id=110721
diplosa...@gmail.com changed:
What|Removed |Added
CC||diplosa...@gmail.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=110721
alvarex changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110721
Alex Deucher changed:
What|Removed |Added
CC||deve...@manuel-voegele.de
--- Comment #1
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #18 from Doug Ty ---
*** Bug 110759 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #17 from Doug Ty ---
19.0.5 also completely broke Blender 2.8 for me, which now crashes whenever I
select any geometry in edit more. 19.0.4 was fine.
Can confirm that building master & reverting "mesa: unreference current winsys
buf
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #16 from Jan Ziak (http://atom-symbol.net)
<0xe2.0x9a.0...@gmail.com> ---
I confirm that reverting "mesa: unreference current winsys buffers when
unbinding winsys buffers" fixes the rendering issues in Spotify and Visual
Studio Code.
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #15 from alvarex ---
>
> Using master + this commit reverted: no more corruption in chromium.
I reverted the commit on 19.1.0 rc3 and it works as well.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=110721
Mathieu Belanger changed:
What|Removed |Added
CC||0xe2.0x9a.0...@gmail.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #13 from Mathieu Belanger ---
That bug was affecting Discord, Brave and Chromium.
Fixed by reverting : 811fa9a79cf
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=110721
alvarex changed:
What|Removed |Added
Status|VERIFIED|REOPENED
Resolution|FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=110721
alvarex changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--
You are receiving this mail beca
https://bugs.freedesktop.org/show_bug.cgi?id=110721
alvarex changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #11 from alvarex ---
> The second one is 811fa9a79cf ("mesa: unreference current winsys buffers
> when unbinding winsys buffers").
>
I'm going to try reverting that commit and building anyway.(In reply to alvarex
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #10 from alvarex ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #9)
> > (In reply to Ropid from comment #6)
> > @alvarex:
> >
> > Try starting chromium with this command line here, it makes it show
> > corruption everywher
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #9 from Pierre-Eric Pelloux-Prayer ---
> (In reply to Ropid from comment #6)
> @alvarex:
>
> Try starting chromium with this command line here, it makes it show
> corruption everywhere for me here:
>
> chromium --ignore-gpu-blackli
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #8 from Ropid ---
$ chromium --version
Chromium 74.0.3729.157 Arch Linux
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@list
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #7 from alvarex ---
(In reply to Ropid from comment #6)
> @alvarex:
>
> Try starting chromium with this command line here, it makes it show
> corruption everywhere for me here:
>
> chromium --ignore-gpu-blacklist --enable-gpu-raste
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #6 from Ropid ---
@alvarex:
Try starting chromium with this command line here, it makes it show corruption
everywhere for me here:
chromium --ignore-gpu-blacklist --enable-gpu-rasterization
--enable-native-gpu-memory-buffers --enab
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #5 from alvarex ---
I need help, I build up mesa and set the git bisect good and bad commits, but
steam does not start because it needs 32bits libs and I can't seem to build
them. What option should I pass to meson or ninja to compil
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #4 from alvarex ---
yes the bug was not present on 19.0.4.
I'll give it a shot, I don't compile mesa from git in a standard way, I compile
it on opensuse build service.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #3 from Eric Engestrom ---
(In reply to alvarex from comment #2)
> now the bug has hit 19.0.5.
Are you saying the bug was not present in 19.0.4, but is now present in 19.0.5?
If so, that's only 22 new commits, 10 if you exclude obv
https://bugs.freedesktop.org/show_bug.cgi?id=110721
alvarex changed:
What|Removed |Added
Version|unspecified |19.0
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #2 from alvarex ---
now the bug has hit 19.0.5. There is a fix for steam if you uncheck "Enable Gpu
accelarated rendering in web views"
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=110721
--- Comment #1 from rro...@gmail.com ---
I get similar corruption in Chromium and Visual Studio Code with Mesa
19.1.0-rc3. There was no problem with 19.1.0-rc2.
This is on Archlinux, kernel 5.1.3, the card is an RX480. I tried compiling
Mesa wit
https://bugs.freedesktop.org/show_bug.cgi?id=110721
Bug ID: 110721
Summary: graphics corruption on steam client with mesa 19.1.0
rc3 on polaris
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
26 matches
Mail list logo
