Hy! I am on Manjaro ARM unstable branch and this update today: llvm-libs (13.0.1-6 → 14.0.6-1)
let LZ Doom from Aur dont start.
An downgrade to 13.0.1-6 solves the problem.
I have a Pinebook Pro with the RK3399 Kernel 5.18 and all up to date.
Greetings
Have you tried rebuilding that AUR package with the newer llvm-libs instead?
hi, “similar” problem with Rpi4 and mpv skipping a lot of frames, unstable branch, same downgrade:
libEGL warning: MESA-LOADER: failed to open vc4: libLLVM-13.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
libEGL warning: MESA-LOADER: failed to open swrast: libLLVM-13.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
sudo pacman -U llvm-libs-13.0.1-6-aarch64.pkg.tar.xz
for aur rebuild im a little scared:
yay -S llvm-libs-git
:: Checking for conflicts...
:: Checking for inner conflicts...
-> Package conflicts found:
-> Installing llvm-libs-git will remove: llvm-libs
-> Conflicting packages will have to be confirmed manually
[Repo:2] z3-4.8.17-1 lua53-5.3.6-1
[Repo Make:49] libuv-1.43.0-1 rhash-1.4.2-1 cmake-3.23.2-1 python-pytz-2022.1-1 python-babel-2.10.3-1 python-docutils-1:0.18.1-1 python-imagesize-1.4.1-1 python-snowballstemmer-2.2.0-3 python-sphinx-alabaster-theme-0.7.12-9 python-sphinxcontrib-applehelp-1.0.2-8 python-sphinxcontrib-devhelp-1.0.2-8 python-sphinxcontrib-htmlhelp-2.0.0-3 python-sphinxcontrib-jsmath-1.0.1-11 python-sphinxcontrib-qthelp-1.0.3-8 python-sphinxcontrib-serializinghtml-1.1.5-3 python-sphinx-5.0.2-1 python-typing_extensions-4.2.0-1 python-setuptools-scm-7.0.4-1 python-sphinx_rtd_theme-1.0.0-5 python-attrs-21.4.0-1 python-iniconfig-1.1.1-5 python-pluggy-1.0.0-1 python-apipkg-2.1.1-1 python-py-1.11.0-1 python-pytest-7.1.2-1 rav1e-0.4.1-2 libyuv-r2322+3aebf69d-1.1 libavif-0.10.1-2 gd-2.3.3-4 netpbm-10.73.37-1 gts-0.7.6.121130-2 gsfonts-20200910-2 graphviz-4.0.0-1 compiler-rt-14.0.6-1 clang-14.0.6-1 lldb-14.0.6-1 ocaml-4.13.1-3 ocaml-integers-0.5.1-2 ocaml-bigarray-compat-1.0.0-2 ocaml-ctypes-0.20.0-2 ocaml-compiler-libs-4.13.1-3 ocaml-findlib-1.9.1-4 python-future-0.18.2-7 python-commonmark-0.9.1-5 python-recommonmark-0.7.1-4 swig-4.0.2-5 ocl-icd-2.3.1-1 opencl-headers-2:2022.05.18-1 python-psutil-5.9.1-1
[Aur:1] llvm-git-14.0.0_r413047.c703d77a61ac-1 (llvm-libs-git)
[Aur Make:1] python-sphinx-automodapi-0.14.1-1
I dont know how i rebuild an Aur package
If you don’t know how to build an AUR package, then you shouldn’t be using any AUR packages…
I know how to build an AUR Package. But i dont know what is mean with “rebuild” an AUR Package.
Does this mean: install the package again or is this a special process?
sorry for my question. i am relativ new to linux and english is not my mother language
Don’t do this.
You need to (probably) rebuild lzdoom, but you are installing -git version of llvm-libs, which, if anything, is even newer than 14.0.6.
Yes and no. You need to build it again (like the first time), not just install existing binary you already have in cache.
Check pamac manual if you need any extra flags or is issuing pamac build ... again enough. (I suspect it isn’t)
Ok i rebuild lzdoom but it don’t start with llvm-libs 14.0.6-1.
with 13.0.1-6 its not a problem to start lzdoom
You rebuilt it with llvm-libs 14 installed, not 13, right?
Yes, right
What’s the output when running it from a terminal?
Well, it was worth a shot.
I tested it in a VM (x64) and it works, so maybe it’s something with aarch64. 
[patrick@patrick ~]$ lzdoom %F
LZDoom <unknown version> - - SDL version
Compiled on Jul 4 2022
LZDoom version <unknown version>
M_LoadDefaults: Load system defaults.
W_Init: Init WADfiles.
adding /usr/share/lzdoom/lzdoom.pk3, 713 lumps
adding /usr/share/lzdoom/game_support.pk3, 291 lumps
adding /home/patrick/.config/lzdoom/DOOM2.WAD, 2919 lumps
I_Init: Setting up machine state.
V_Init: allocate screen.
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
Opened device Internes Audio Headphones + Speaker
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 481.75 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
Using video driver x11
OpenGL load failed. No OpenGL acceleration will be used.
*** Fatal Error ***
!!! Failed to exec debug process
No idea what the “debug process is”. Maybe some of the developers know.
I don’t think last line has any meaning.
My output:
...
Using video driver x11
GL_VENDOR: Mesa/X.org
GL_RENDERER: llvmpipe (LLVM 14.0.6, 256 bits)
GL_VERSION: 4.5 (Core Profile) Mesa 22.1.3 (Core profile)
GL_SHADING_LANGUAGE_VERSION: 4.50
...
Well, it’s a fatal error, so it must have some meaning.
is the problem persistent? mpv seems to work properly after latest update.
Yes its persistent. i have flashed the manjaro os again to the emmc and made all updates.
same problem with llvm-libs 14.0.6-1
The debug process error has an issue report here: [BUG] Git crashes on Linux · Issue #1596 · coelckers/gzdoom · GitHub
Maybe you can let them know that it’s related to llvm-libs version?
Update:
i removed mesa-git 22.2.
and installed the non git version mesa 22.1.
Now lzdoom works with llvm-libs 14