Arch Linux

"it works for me (tm)"

More information ? cpu ? gpu ?

signal-desktop is broken after Mesa update, firefox and chromium however still work under Wayland:
firefox: native Wayland
chromium: under xwayland
signal-desktop: under xwayland, log: https://bpa.st/QJZA
mesa-21.0.1-1, signal-desktop-1.40.1-1, firefox-87.0-1, chromium-89.0.4389.90-1

Can we have the output of 'glxinfo' ?

CPU: intel i7-6700k
GPU : nvidia gtx 970

And the output of 'LIBGL_DEBUG=verbose glxgears' ?

So, I ran LIBGL_DEBUG with the updates done and this was the output(also a blackscreen).
When I ran the command with the outdated package the output was fine(animation rendering at about 200-300fps)

Hi

Discord and Firefox work fine for me, but Chromium, Signal desktop, and Kodi display only a white or black window. Kodi work even if just display a black window, using shortcut 's' followed by 'enter' close Kodi normally.
glxgears produce the same output as Radu Caprarin (150-400 fps with old pkg, more than 2000 fps on new pkg and black window).
Retrograding only mesa package from 21.0.1-1 to 20.3.4-3 solve the problem.

CPU: intel core i5-3570K
GPU: nvidia gtx 760
Driver: nvidia version 460.67-4

glxinfo show different device names and info depending on package version, I give glxinfo output for both.

I hope these informations can be useful.

@radu.mihai10

Does it work with 'MESA_LOADER_DRIVER_OVERRIDE=i915 glxgears' ?

No, its still just a black screen, no output in the terminal except for framerate

I can confirm, this is happening to me as well. I fixed it by following instructions in https://bbs.archlinux.org/viewtopic.php?id=265026 and downgrading mesa. Surprisingly, I did not need to reboot after the downgrade - pkilling and restarting Chrome was sufficient.

I was seeing the blank screen in both Chrome and VS Code. Fortunately, Firefox worked for me.

My glxinfo is attached.

@liftm

What is the output of 'LIBGL_DEBUG=verbose glxinfo' with mesa-21 ?

Attached is `LIBGL_DEBUG=verbose glxinfo > 21-glxinfo`. Also, from STDERR:

```
libGL: screen 0 does not appear to be DRI2 capable
libGL: MESA-LOADER: dlopen(/usr/lib/dri/swrast_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/leo/.drirc: No such file or directory.
```

Same happened to me. I am so happy I found this bug report, I was about to throw away my graphic card :)

CPU: Intel core i7-2600
GPU: Nvidia GTX 970
Driver: nvidia-dkms 460.67-1
Kernel: linux-zen
Window manager: i3-wm 4.19.2-1

Same things as reported above, except the only browser I can use now is Firefox, since it does not default to hardware accelerated rendering. Once I set the browser to use hardware acceleration it does not start same as chrome and opera. But I can use it if I delete ~/.mozilla profile folder.

glxgears - black screen.
chrome and opera - starts with blank-gray screen. Can not be used nor closed.
All games do not start or black screen
Vulkan game Serious Sam - works fine. However Proton emulated games do not start, even tho it uses Vulkan.
glmark2 - black screen, but glmark2-ec2 works without any problems.
vkmark - passes without any issues.

So looks like it is only OpenGL related issue.

Looks like for me everything got back to normal after update to: linux-zen 5.11.11.zen1-1

Not for me, still the same after linux 5.11.11 update

OK, so it went back to being broken again, after computer restart. I have tried reinstalling kernel, nvidia-dkms and mesa packages also performed multiple restarts, but could not get it back working again :(

thank you,
sudo pacman -U /var/cache/pacman/pkg/mesa-20.3.4-3-x86_64.pkg.tar.zst

fixed it.
Is there a way to blacklist that update?

@angelettif You can prevent updates to this package by adding this to your IgnorePkg in pacman.conf. See https://wiki.archlinux.org/index.php/pacman#Skip_package_from_being_upgraded for details.

There's no way to say "only skip this _version_" as opposed to "don't upgrade this package at all", but pacman does show a warning that shows the latest version of the package, so you can manually keep tabs on whether a new version of mesa is out. For example, my `pacman -Syu` says:

```
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
sublime-text is up to date
:: Starting full system upgrade...
warning: mesa: ignoring package upgrade (20.3.4-3 => 21.0.1-1)
there is nothing to do
```

I'm planning to try out the next version after the warning tells me that there's something available after 21.0.1-1.

This bug doesn't occur on my Arch laptop. I wonder if it's specific to NVidia GTX cards? My tower (which is what I posted my glxinfo above from) uses:

CPU: Intel Core i7-6700
GPU: NVidia GTX 1080
Driver: nvidia 460.67-1
Kernel: linux 5.11.11.arch-1
Window manager: xmonad 0.15

My laptop (where the bug does _not_ occur) is a Thinkpad X1 Carbon (5th generation).

I got
CPU: Ryzen 3900
GPU: NVidia GTX 1080
Driver: nvidia 460.67-1
Kernel: linux 5.11.11.arch-1
Window manager: awesomewm

Thank you for the IgnorePkg

Can confirm.

Ryzen 9 3900X
nVidia Titan RTX
nvidia 460.67-5
linux 5.11.11-arch1-1
xorg-server 1.20.10-3
mesa 21.0.1-1

Firefox works, chromium and signal-desktop seem broken. Blackscreen on the mesa demos. Attached is `LIBGL_DEBUG=verbose glxinfo > glxinfo 2>&1` running on the above mentioned machine.

@zacmar nvidia is not listed in the glxinfo. What if you make changes to xorg.conf as in  FS#70287 ?

@loqs I just quick and dirty copied the fix, updated the system and everything seems to work.

I'm happy to report that upgrading to mesa 21.0.2-1 appears to have resolved this issue.

Upgrading to 21.0.2-1 fixed issue for me too.