Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Graphical Corruption on Chromium Apps with Mesa 19.0.5
Date: Thu, 06 Jun 2019 13:06:02 +0200	[thread overview]
Message-ID: <20190606110602.PZybtCCxTsUqqB1_VCZn-jSQZxeWlgdq_KmSm_EC2vg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]

Closed issue by HadetTheUndying on void-packages repository

https://github.com/void-linux/void-packages/issues/11907
Description: ### System

* xuname: Void 4.19.45_1 x86_64 AuthenticAMD uptodate rrrmFFFFFF

* package: 
[*] libGL-19.0.5_1          Graphics library similar to SGI's OpenGL
[*] libGL-32bit-19.0.5_1    Graphics library similar to SGI's OpenGL (32bit)
[*] libGLES-19.0.5_1        Free implementation of the OpenGL|ES 1.x and 2.x API
[*] libGLES-32bit-19.0.5_1  Free implementation of the OpenGL|ES 1.x and 2.x API (32bit)
[*] libglapi-19.0.5_1       Free implementation of the GL API - shared library
[*] libglapi-32bit-19.0.5_1 Free implementation of the GL API - shared library (32bit)
[*] libOSMesa-32bit-19.0.5_1    Mesa Off-Screen interface library (32bit)
[*] libgbm-19.0.5_1             Mesa Generic buffer management API - runtime
[*] libtxc_dxtn-32bit-1.0.1_2   S3 Texture Compression (S3TC) library for Mesa (32bit)
[*] libxatracker-19.0.5_1       Mesa XA tracker interface library
[*] mesa-ati-dri-19.0.5_1       Mesa DRI drivers for ATI GPUs
[*] mesa-ati-dri-32bit-19.0.5_1 Mesa DRI drivers for ATI GPUs (32bit)
[*] mesa-intel-dri-19.0.5_1     Mesa DRI drivers for Intel GPUs
[*] mesa-nouveau-dri-19.0.5_1   Mesa DRI drivers for NVIDIA GPUs (nouveau dri)
[*] mesa-opencl-19.0.5_1        Mesa implementation of OpenCL (r600+ only)
[*] mesa-vmwgfx-dri-19.0.5_1    Mesa DRI drivers for VMware
  *affected package(s) including the version*

### Expected behavior
Proper Rendering in videos and some web Content
### Actual behavior
Weird Graphical corruption with Certain content and Videos, maybe related to hardware acceleration.
https://i.imgur.com/ueM5iOY.png

### Steps to reproduce the behavior
Happens to me with the latest Mesa on most Chromium apps with an RX Vega 56



      parent reply	other threads:[~2019-06-06 11:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>
2019-05-30 22:15 ` voidlinux-github
2019-06-01 12:10 ` voidlinux-github
2019-06-01 18:56 ` voidlinux-github
2019-06-01 19:20 ` voidlinux-github
2019-06-01 22:00 ` voidlinux-github
2019-06-02  0:23 ` voidlinux-github
2019-06-02  0:26 ` voidlinux-github
2019-06-02  0:29 ` voidlinux-github
2019-06-02  4:11 ` voidlinux-github
2019-06-02 15:32 ` voidlinux-github
2019-06-02 20:55 ` voidlinux-github
2019-06-03  0:21 ` voidlinux-github
2019-06-03  1:36 ` voidlinux-github
2019-06-03  1:42 ` voidlinux-github
2019-06-03  1:44 ` voidlinux-github
2019-06-04  9:05 ` voidlinux-github
2019-06-04  9:11 ` voidlinux-github
2019-06-04 11:30 ` voidlinux-github
2019-06-04 22:10 ` voidlinux-github
2019-06-04 23:02 ` voidlinux-github
2019-06-06 11:06 ` voidlinux-github [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=20190606110602.PZybtCCxTsUqqB1_VCZn-jSQZxeWlgdq_KmSm_EC2vg@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).