Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Network Manager Broken (Read 4688 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Network Manager Broken

Reply #15
  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.
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

Re: Network Manager Broken

Reply #16
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.
Luckily we are all human  :D
Is it still correct that gremlins in pacman.conf should always be disabled?

Re: Network Manager Broken

Reply #17
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


Re: Network Manager Broken

Reply #18
This is what I thought and remembered.
Thanks

Re: Network Manager Broken

Reply #19
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)

Code: [Select]
 #!/bin/bash 
sudo rc-service NetworkManager restart
sudo nmcli dev set wlp4s0 managed yes 
sudo nmcli dev set enp3s0 managed yes
Keep it Simple. Simple is Secure, Simple is Beautiful.

Re: Network Manager Broken

Reply #20
Any idea when the Gremlins version will make it into the stable repo?
OS: Artix x86_64
Host: Predator PH517-61 V1.07
CPU: AMD Ryzen 7 2700 (16) @ 3.2GHz [112.4°F]
GPU: AMD ATI Radeon RX Vega 56/64
Memory: 1129MiB / 64390MiB


 

Re: Network Manager Broken

Reply #22
Thank you sir I will now stop ignoring that update  8)
OS: Artix x86_64
Host: Predator PH517-61 V1.07
CPU: AMD Ryzen 7 2700 (16) @ 3.2GHz [112.4°F]
GPU: AMD ATI Radeon RX Vega 56/64
Memory: 1129MiB / 64390MiB