[BUG] <Session Appimage Version 1.12.3 unusable due to graphical glitches on Garuda Linux>

[qunYp3dZSyLjoEoEg]

Code of conduct

• I have read and agree to adhere to the Code of Conduct

Self-training on how to write a bug report

• I have learned how to write a bug report

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When I updated to Sesion 1.12.3 and restarted for the first time, it completely bugged out and due to graphical glitches I am unable to use the application (image provided). It does let me log in, but the log in Screen is similarly bugged out. I don't know how I might be able to provide logs or where to find them, but if those are necessary please tell me how I might be able to get them. I am only now writing this report, even though I updated pretty much immediately when 1.12.3 came out, since it didn't come to my mind to search for the github repo.
I am on Garuda Linux, running on X11. I have a 7800X3d and a Radeon 6950XT and am running it via Appimagelauncher. If anything else is necessary for debugging, please ask.
Edit: Without Appimagelauncher, 1.12.2, 1.12.1 and 1.11.5 is also affected, after downloading it from github, so maybe an issue with my system? My current glibc version is glibc 2.39+r52+gf8e4623421-1

Expected Behavior

Sesssion should not have graphical glitches preventing me from using the app

Steps To Reproduce

I wouldn't know how?

Desktop Version

1.12.3

Anything else?

No response

[KeeJef]

Could you start the app from the command line, and see if there are any relevant errors being logged? Also is it possible that this issue could this be linked to this one #3112 ?

[qunYp3dZSyLjoEoEg]

Sorry for not replying in the last week, had a rough patch in my life. Anyway, after around 1.5 months the püroblem has cleared itself so ig we can ignore it until it pops up again? Have a nice day and thanks for your reply!

[qunYp3dZSyLjoEoEg]

(As for why I know the time it is because I can now see that the last message I sent was on April 23rd and today I could see it again)

[KeeJef]

OK great, thanks for the update, ill close this for now, we can reopen if this issue presents itself again