Hi all,
Since my last system update this morning with
sudo pacman -Syu, the Steam client doesn't appear (? if it's the right word ... I'm not English native speaker, sorry) on my desktop. The process
steam exist (listed with
ps -A) but still in background. So, the client itself is never launched.
I've found this subject in the forum who discribe exactly the problem and his cause (so, I keep the same title ;) ) : https://forum.artixlinux.org/index.php/topic,4594.msg29478.html#msg29478
I check on my system and it's the same :
- nvidia-dmks and nvidia-utils was both updated to version 525.60.11-1 with this last system update ;
- lib32-nvidia-utils was still in his previous version 520.56.06-1. And that seems the cause of the issue.
But, unlike in the other subject, the new version isn't yet available and I still have no access to the Steam client.
So, could someone tell me when
lib32-nvidia-utils will be update to the 525.60.11-1 ? Hope not too late : I have a multiplayer game who need some actions from me ... :P
Thank you for your answer.
Best regards,
Paseyk ---
In the meantime you should be able to to downgrade nvidia-dkms and nvidia-utils to match lib32-nvidia-utils.
Unless you've changed default settings or deleted the files you'll find them in /var/cache/pacman/pkg/
You can install with
sudo pacman -U filename.tar.zst
Thanks, @gripped.
I'll do that if it's take too long time too upadte the last package. But I prefere keep this solution as the "last one". ;) Doesn't change that your information and this command is very helpfull. :)
I understand your hesitation. But you really can't do any harm (if you do it right :) ). Even if it doesn't work pacman -Syu will return you to the latest versions.
If you want to jump straight back into the game you need to downgrade temporarily.
I imagine it won't be too long before lib32-nvidia-utils is updated.
Can not have too much bad impact on other packages (like dependencies) ?
I would say no but my first advice is never trust anyone !
I've done exactly what I describe before myself when I've encountered what you have.
Maybe the two packages need installing at the same time, on the same line. IE one package straight after the the other. I can't remember.
But if your nervous just wait maybe.
I know if I break my install I can fix it again.
On the other hand we learn by trying things and stepping out of our comfort zone......
You'r right on all the points. :)
The question was just : "Have I time and enrgy to fix it if the downgrade turn very bad ?"
But, good news, this question doesn't exist enymore : the new version is now in the depository and updated on my system. And Steam works fine again ! 8)
This for your suport. It was very appreciate. :)
PS: I don't find how to change the tittle to add [Solved] at the beginning. Sorry ...
If you don't want to be doing downgrades what may help is always check the list of packages being updated when doing system upgrades. If you see any of the three nvidia packages mentioned check that all three are being updated. If not just cancel the update and try again later. Do also check the versions of them all in case any slipped through unnoticed.
Then hopefully your gaming won't be interrupted.
That's an other good advise. :) Thanks for all. 8)
#NoUpgrade =
#NoExtract =
NoExtract = etc/mysql/my.cnf
NoExtract = usr/bin/mysqld_safe
NoExtract = etc/init.d/mariadb
NoExtract = etc/runlevels/default/mariadb
NoExtract = usr/lib/sysusers.d/mariadb.conf
NoExtract = usr/lib/tmpfiles.d/mariadb.conf
NoExtract = usr/share/vim/vim80/defaults.vim
Can't you just exclude them from /etc/pacman.conf ?
It's not too "extreme" ?
The probleme is just because the new version of all the three packages are not available in the sime time in the depository. So, the issue comes only if you made the update during the ime in between. It'll be not so often. ;)
So, I think the last advice from gripped is more appropriate than a "permanent" exclusion in /etc/pacman.conf. Except perheaps if the other updates can't wait ...
I'm not sure what that means. The problem is that updates make the package unstable when otherwise it would be sable. The config file is the for you to edit and control and you have a vi editor. If you want to control it so it is not automatically tampered with without your explicit intervention, it gives you the means. Nothing is permanent.
I understand better now. :) Thanks for this. :)
Oooh, that's so true. :) 8)