After yesterdays update openrc can not start Network Manager.
rc-status -a
shows " NetworkManager [ stopped ]"
My quick fix was to downgrade Network manager from the pacman cache to version 1.10.2-1
Hello,
I am using testing/gremlins and NetworkManager 1.10.6-2 works just fine.
If you want real help, please provide some logs and error messages.
Try running NetworkManager from a terminal. Do you get the below message? That's the problem I'm currently having with it.
NetworkManager: error while loading shared libraries: libpsl.so.6: cannot open shared object file: No such file or directory
I had the same problem and I tried this:
[roberto@Artixxx ~]$ ls -la /usr/lib/libpsl.*
lrwxrwxrwx 1 root root 15 14. Mär 14:55 /usr/lib/libpsl.so -> libpsl.so.5.3.0
lrwxrwxrwx 1 root root 15 14. Mär 14:55 /usr/lib/libpsl.so.5 -> libpsl.so.5.3.0
-rwxr-xr-x 1 root root 63088 14. Mär 14:55 /usr/lib/libpsl.so.5.3.0
From the user
virtual-dev in the German
systemdfree.de forum, I got the hint to upgrade the lib, because they are very old.
He said, that the libs are ancient, the new NM needs something new.
At a normal Arch they are already at 6.2.
After I've done the following:
sudo ln -s libpsl.so /usr/lib/libpsl.so.6
a new line was added:
lrwxrwxrwx 1 root root 9 15. Mär 20:06 /usr/lib/libpsl.so.6 -> libpsl.so
After that, I was able to start the NetworkManager with
sudo NetworkManager
Maybe the libs in Artix needs a refresh.
Do you guys have the "gremlins" repo enabled?
I also have this problem this morning. No, Gremlins not activated. Rebooted this morning after updating and same problem. Downgraded to networkmanager-1.10.5dev+3+g5159c34ea-1-x86_64.pkg.tar.xz and it's working again. I do not have anything in the logs however as to what is causing the updated version to fail. The only line from rc,log just states that it cannot start.
rc.log: * ERROR: NetworkManager failed to start
Followed by:
rc.log: * ERROR: cannot start netmount as NetworkManager would not start
I have gremlins activated but I'm not having issues with network manager
No, it's disabled.
Should we?
So without gremlins enabled, the latest NetworkManager is 1.10.6-2, which requires libpsl.so.6, but the latest available is libpsl-0.20.1-1, which provides libpsl.so.5.
To me, that inconsistency is a bug. The newer NetworkManager should not have been released without the newer libpsl. Where should such bugs be reported?
Doh! Of course. It's the old "enable the gremlins repo trick," 99. EVERYBODY knows the gremlins repo must be enabled anytime a system upgrade goes face down on some package or another. Or everybody SHOULD know that, right? I mean, there are only how many possible reasons a package doesn't update correctly, so obviously it must be this one of the many.
I've had problems over the years with other distros along these lines also. And why I no longer use them. It is just possible that not everyone seeking relief from cysticd based distros is necessarily a hobbyist and enjoys the ever ongoing buzz of low level technical jargon. They might have actual work to do, who knows. It is they I worry about... I have time to inspect and wait for solutions, but not everyone is in this same situation.
Artix is very new in it's inception and I feel that to expect a "sheer stable" system for doing "actual work" to be already achieved an unrealistic expectation. The "less adventurous " looking for that stability have other options at this time.
Artix is progressing thanks to the efforts of a dedicated few. :)
Best regards.
It's been pretty stable thus far, and I use it to run my business. Isn't that the aim to attract users by offering a stable system? This seems to be something that could have easily been avoided?
Anyway, a bit embrarassing this morning - showing a mate how good Linux is and no network ??? ::)
All sorted now with the suggested downgrade so I'm happy again.
I really appreciate Artix and what the team is doing, between some upgrades it works like a charm and it's stable. I don't know any other non systemd distro that works as smooth as Artix.
It's true that upgrades don't go that smoothly but Artix is a new project so let's give it a chance to improve. I think some issues were avoidable and were irritating but we all learn by mistakes.
If Artix want to attract more users it has to improve this and make sure there are not such problems during upgrades especially mistakes that result in networking issues. Because what future distro has if there is no-one using it?
I use Artix on my computers. I don't feel enough confidence to run it on computers of my family members and friends. But I would definitely like to.
We are still human, and humans make mistakes.
In the case of libpsl, NM and depending packages, the mistake had some bad consequences.
Please have some patience, its all fixed in the gremlins repo, but I don't want to break the sync with arch more, so NM comes to stable when arch move it.
Although in generalities your analysis is correct, your reaction to the particular problem is a bit off the charts.
I actually use artix less and less these days as it is not so challenging as it was promised. Too damn boring stable for being a beta of a system. Remember, we were all warned that this is not for running a business server yet or for newbies. Still there is no Artix 1, it is a beta system of Artix.
This particular problem came down to stable artix a couple weeks after the libpsl problem appeared on testing as a bi-product of that was patched in gremlins, I think. When something breaks on update the immidiate solution is look for the previous version in var/cache/pacman/pkg and pacman -U that one. Then wait for a solution. A 5' chore maybe? If you don't have a second backup installation you should always have an artix live to "artools-chroot" in case can't boot. That is common sense. On Arch or Debian forums they would just shut down your account if their networkmanager broke and you had this attitude. It takes months to fix a break or a bug in some of "those" distros, here you got an apology!
Come on, lighten up. Look at void and antix, they break and fix things all day and all night. They think they are running the best systems ever :) When OpenRC 35.0 came out there was a warning it might cause breaks. I run and installed it, then I kept a log of the break, went back to last good 34. reported it and before anyone else woke up it was all fixed. That was the most fun I have had with artix since the day I converted from Manjaro-OpenRC.
I am so bored with Artix I think I am going to run Goblins
Luckily we are all human :D
Is it still correct that
gremlins in pacman.conf should always be disabled?
Gremlins is testing
If you want to be running testing you should enable the gremlins repositorIES (it is not just one, galaxy and 32bit also).
On this particular incident enabling gremlins would fix the problem if one didn't want to revert to an earlier netowrk-manager
This is what I thought and remembered.
Thanks
I just want to share here a three lines that help me so much with NewtworkManager not started (from ManjaroOpenRC days :) ), I put them in a script which become a time saver for me (especially when upgrde)
#!/bin/bash
sudo rc-service NetworkManager restart
sudo nmcli dev set wlp4s0 managed yes
sudo nmcli dev set enp3s0 managed yes
Any idea when the Gremlins version will make it into the stable repo?
Went into world 4 days ago.
Thank you sir I will now stop ignoring that update 8)