Thanks. I no longer get the error messages when running it from the terminal but I am getting the same issues i was getting earlier when I run it from the desktop

Did you add the packman repo to the repository list before running opi codecs¿?

Edit : Never mind that was a stupid question

https://lemmy.one/post/151466 - This post may help you with issues you face with launching steam.

I too have have an amd+amd laptop(MSI bravo 15 with 5600h+5500m) and I don’t have any issues with switching from integrated graphics to dedicated graphics. The kernel decides itself(with help from the program running I am guessing) whether the iGPU or dGPU needs to be used. I face absolutely no freezing issues or issues in general related to graphics switching.

What might be possibly causing your random freezes and stutters is the AMD fTPM. It’s random number generator function is known to cause stuttering and freezing on both windows and Linux. AMD made several futile attempts at solving the issue before Linus ranted about it and then AMD disabled the RNG functionality. But almost all these patches are part of kernel 6.x series so maybe they have not made it downstream to the lts kernel you are running on(not surprising considering how much of a burden it seems supporting old kernels is). If possible, you could disable fTPM from the bios and see if that fixes your general freezing issues. Though I have to warn you that TPM is needed for secure boot(I think) and is used by some password managers for secure password storage so you might lose functionality by turning off the fTPM. Moving to a more modern distro which uses a newer kernel(6.4.7 and above iirc) may also help.

Also out of curiosity, why is your GPU being shown as 5600 or 5600xt. I am assuming that you have a 5600m

How did you switch mesa version without using the --allow-vendor-change flag. Did you manually uninstall the mesa packages shipped by opensuse and then switch them with mesa packages from packman? Vendor change is the only method recommended everywhere and no other methods are discussed so I am curious as to how you manage without it. Also how do track that the repos are synced. I have to manually check the packman website to see if the packages have been updated to version that opensuse is shipping. Do you do the same?

Also sorry for the late reply

Actually i dont think ubuntu or their derivatives are to blame here. The issues started after the big new ui update to steam. Somebody did raise the issue with valve and there is a thread on the bug but it seems they arent particularly interested in fixing the issue(maybe because it does not affect that many users?). Also once the command has been added, the experience should be just as smooth as normal. Why do you characterise it as just tolerable?

Well there were/are attempts to make flatpak with flathub an universal app store on linux. If I remember correctly, there were some ideas mooted on adding paid apps in to flathub.

Wow this is something new that I found out just now. Lemmy-ui was able to show the video but none of my clients are showing a video or even hinting towards the fact that there is something to show

Am I the only seeing no description or photo of what the bug is as part of the main post? Is this some bug in lemmy?

Add DRI_PRIME=1 %command% to the game’s launch option in steam. That will make the game run using the dGPU.

Also dont run steam using the dGPU. There is some bug in some ubuntu or ubuntu based amd+amd systems where the steam client crashes when opened with the dGPU. Open the client with the iGPU and use the command mentioned earlier to make the game run using the dGPU

Especially when you also use a aur helper like yay. Also I have to do is type yay and enter my password and then everything is updated

So how did you replace the mesa version. Every documentation I see seems to tell of the --allow-vendor-change option

Do you also use the mesa pacakge from packman repos. Will zypper automatically use the packman package of mesa when updating if you do the vendor change for mesa from official repos to packman. I am asking because when I tried TW, different versions of packages in mesa were somehow simultaneously installed after a dist-upgrade and mesa was broken

But don’t you need the mesa version with the codecs inbuilt for hardware decoding with a AMD card¿?

Yeah no pressure. It was just bugging me as the issue was seeming very random and unreproducible. Thanks for all the work on the app

You seemed to have misunderstood. I am enquiring about the usage of packman repos in opensuse tumbleweed

I have tested with around 20 instances. The popular ones like lemmy.ml, lemmy.world, etc, a few of the feddit.country domains and a few random instances. Lemmy.one seems to be the only one suffering from the issue. Now i haven’t tested all the instances so maybe some obscure instance faces this problem but in my experience only lemmy.one suffers from the bug.

I sometimes use sync and other times voyager. In voyager and lemmy-ui, it is not a clickable link. In sync it is. I was looking for a way to have a clickable link in lemmy-ui

Weird. This works as a tag but doesn’t give a clickable link to the profile.

I use this but was unsure if people were actually getting tagged. Thanks kind stranger

The 5-6 other instances I tried out did not face this problem. Just to be sure, I cleared the app’s cache and user data, force stopped it and then viewed the post using lemmy.one as the base instance and was able to replicate the problem. @ljdawson@lemmy.world

I tried some things out and I have learnt a few things.

1. Changing the language settings(and including every language) did not solve the issue.
2. I reinstalled the app and before logging in, viewed this post and was able to load and view all comments.
3. After logging in, I was not able to view all the comments of this post. By switching to the anonymous lemmy.world feed I am able to see the comments again.
4. I also tried to view the comments before restoring my settings and after restoring my settings. The outcome in both cases was the same

Edit : I changed the instance that the anonymous feed uses from lemmy.world to lemmy.one and was able to replicate the issue. It seems the issue lies how sync is fetching comments from the lemmy.one instance. I will try out if other instances run into the same issue