Mainboard: SolidRun HoneyComb LX2
Graphicscard: AMD Radeon RX580
Starting minetest itself always succeeds, attempting to join the world only succeeds if the Xorg server has been running for atleast 5 minutes. Trying to open a local world or switching to the "join game" tab freezes the game.
If the game will freeze when trying to join a world, a "buffsize too low?" error is put out.
Additional info: When frozen, minetest shows its lightblue/sky colors with a grey bugged texture in the middle. the minetest welcome message is also shown for a second time, but gets revoked after little time.
Minetest startup message:
`2021-10-14 18:24:22: [Main]: Automatically selecting world at [/home/user/.minetest/worlds/myworld]
[ALSOFT] (EE) Failed to set real-time priority for thread: The operation is not permitted (1)
Loaded texture: /usr/share/minetest/games/devtest/menu/background.png
Loaded texture: /usr/share/minetest/games/devtest/menu/header.png
Loaded texture: /usr/share/minetest/games/devtest/menu/icon.png
Loaded texture: /usr/share/minetest/textures/base/pack/plus.png`
Created attachment 745605 [details]
a link to glibc
Comment on attachment 745605 [details]
a link to glibc
>upon further extensive tests involving gentoo-glibc, void-glibc and void-musl, I found out that void-glibc shows similar symptoms as on gentoo-glibc. On void-glibc I set the developement-test option in minetest and restarted xorg.
>The very same symptom I'm having on Gentoo occured there.
>Minetest works fine on Void-musl.
>On void-glibc I deleted the ~/.minetest folder as that also deletes chosen settings, but the issue persists and is even worse then on gentoo: minetest is marked as broken when starting and freezes the xorg server at startup aswell, while on gentoo: minetest starts up just fine, but trying to join a world sometimes results in minetest freezing.
>Used Void glibc version: 2.32
>Used Gentoo glibc version: 2.33-r7
emerge --info: https://dpaste.org/OHO2
Please attach rather than linking for posterity if you can
Oh, my emerge --info was too long to fit in. But thanks for the advice.
(In reply to hano.yeetos from comment #5)
> Oh, my emerge --info was too long to fit in. But thanks for the advice.
You should definitely be able to attach it, but failing that, attach it compressed
Created attachment 746325 [details]
emerge -- info
Have you reported this problem upstream?
This REALLY is something for upstream to take care of.