On a sidenote. There is an ongoing effort between Debian maintainers and AMD of packaging opensource AMD compute drivers under the name ROCm for Debian. ROCm and particularly HIP replaces OpenCL as a compute stack in modern AMD GPUS.

Look for it on this mailing list:
https://lists.debian.org/debian-ai/2021 … html#00054

The goal is the ability to install compute driver stack for AMD gpu with sudo apt install rocm or something similar.

I followed the link you provided and voila I have working OpenCL and no problem described in the first post!

Ah, excellent, that is good news. Perhaps consider informing the author of the linked guide so that they can declare Devuan as a working configuration.

Please include *all* relevant information in future threads.

Sorry about that. Won't happen again.

I know they are shit, but you can't compute 3d rendering on a AMD GPU in Blender without them. That's why I have installed only OpenCL parts of proprietary driver. OpenGL and display is handled by mesa.

I do it that way because there is no better alternative to have both smooth display and compute stack for 3d rendering.

ED:
Wait. I was wrong. I thought that installing PRO drivers with --headless installs only compute part of the driver. But I followed the link you provided and voila I have working OpenCL and no problem described in the first post! Did I ran this machine for so long only THINKING that I'm using mesa as a display driver? LOL if true.

So the problem seems to be a conflict between mesa and PRO display drivers when they are both installed.
Marking as solved.

And most importantly: why didn't you mention the PRO drivers in your OP? Are we supposed to be psychic? Please include *all* relevant information in future threads.

glxinfo -B

No, that is not supported.

You would be better switching to ceres IMO — the mandatory 10-14 day transition delay to testing means that breakage is fairly common (hence the name "testing") and also that if things are broken they can stay broken for a while. If you can't troubleshoot this sort of thing yourself then you probably shouldn't be running testing.

I'm running two screens and there is a lot of issues after this update:

- certain windows on main display are giga-sluggish and leave that funny trace of itself, but only for a brief moment
- navigation in some app is broken, menus are closing after moving cursor inside them (Firefox), clicks are not registered (Mullvad)
- the only title bars that are visible are fat, Gnome ones, rest are not rendered
- can't maximize/minimize windows
- system don't recognize shortcuts like Alt+F4 (but Ctrl+Q works)
- Alt+RMB windows resize don't work
- mouse cursor is displayed as 'x' symbol/icon
- can't switch between workspaces
- in xfce panel there are no application bars although apps are opened
... plus a lot more

Running Blender from CLI reveals:

libGL error: MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
libGL error: failed to load driver: swrast
Error! Unsupported graphics card or driver.
A graphics card and driver with support for OpenGL 3.3 or higher is required.

Is rolling back an option here? INB4 - yes, to Chimaera :^)
Thanks for any advice.

ED: I reinstalled all mesa packages including libgl1-mesa-glx and mesa-utils, but no effect.
ED2: glxgears gives identical output as Blender plus: Error: glCreateContext failed
ED3: After checking there is no /usr/lib64 directory, but in /usr/lib/x86_64-linux-gnu/dri there is swrast_dri.so