Worked like a charm. Thanks, Phil!
1 Like
Steam games are working now. Thanks!
1 Like
I was planning do the update tomorrow.
I’m getting the updated adwaita-icon-theme when using sudo pacman -Syu tomorrow?
If you read the thread, you’re getting the fix if you update now.
Unless you use some veeery bad mirror (like Chinese), all should be synced by now.
pacman-mirrors
Look for the green OK.
1 Like
This threat is why I love Linux and Manjaro.
I understand very little about computers, but you guys do. I have a problem and I can always find a solution or a helping hand. I even learn a thing or two while reading the forums.
Thanks!
3 Likes
Maybe you are a GNOME user and use Adwaita theme by default. Then you weren’t affected at all. However, when I test steam in gamescope session the whole gamemode session crashed and I landed in the desktop, if the gaming edition had provided one. Either GNOME or Plasma.
Other users don’t use GNOME or don’t use the Adwaita theme. The loop then was not working and crashed eventually. However, since we are on a rolling system you had more updates. Soon we figured out that Mesa was not the problem. Well, if some graphical might not work you might point your finger first on complex drivers and not on some simple one-line mistake in an icon theme.
You would also point your finger more to the lower toolchain, since it was slightly different with some snapshots we had in other branches. Since unstable and testing was working I was switching between stable and testing and actually installed all packages I thought which were not the issue until I finally found the icon packages I never looked at.
So when I had installed 3 adwaita theme packages and launched the steam session it magically launched. Then I dropped the 47 icons and just installed the repackaged 46 legacy one - and it still worked. Then I checked what the Arch maintainer did and found the issue which never was pushed upstream in the end.
In kernel development you take all the patches upstream provides. So the kernel 6.11.2 had about 685 patches if you compare it against 6.11.1. There you use some called git-bisect, which suggest you a version of the kernel to compile and test. If it passes your test you can say good and it gives you another state you should test. Then you may say bad and it continues like that until you find the one commit out of those 600+ which caused your issue. You report that and the author or another kernel expert might work with you to fix that issue. When done the next kernel version will work again for you.
7 Likes
Seems to work for me too.
Thank you for fixing the error.
I would like to ask you (and this is not an offense) how this could slip to the testing process.
Normally I would think, the most used things should be the highest priority in the testing process and gaming on steam is surely very important for a lot of manjaro users.
A few months ago I remember that spotify would not launch anymore because of a manjaro update.
Perhaps you could add things like steam (including starting a few sample games) and things like spotify which are used by millions of people as high priority to the testing phase before rolling out updates.
In case of Spotify there is no package of it in the official Manjaro repos. You can get it as a Flatpak or AUR package and as such they have nothing to do with the Manjaro distro in the first place.
Usage of AUR or other package formats is at your own risk.
There is kind-of, but it still extracts a deb and is currently broken. So it does not really matter.
The case was that no snaps worked anymore. And that would have been discovered with a test of the Spotify snap, which is widely used.
And if you really think it has nothing to do with the OS, if snaps do not run anymore on the OS because of a bug, than yeah - what shall I say?
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.