Issue #17!!
Well, I managed to scp the files off my other PC and then ran: sudo pacman -U file:///var/cache/pacman/pkg/libnma-common-1.8.40-1-x86_64.pkg.tar.zst file://var/cache/pacman/pkg/libnma-1.8.40-1-x86_64.pkg.tar.zst which solved the issue!
I learnt quite a bit from this.
Thanks to all you friendly people for making my first post such a happy experience =D
you can … if it bother +use nm-connection-editor lot , pkg will get update if no + to pacman.conf ( just no forget about it if you do ) 
small problem that i sure get fix next update ( now bug highlighted) so i will leave as is … ( no use much )
Yeah, EOS is the best community! 
By the way, I think the @pebcak’s post (#13) is the one that should be marked as solution, because he pointed the culprit.
Done. (Initially thought you could tag multiple solutions).
Very honorable of you good sir!
just was hitting the same issue on testing a new ISO
It seems to be fixed on libnma-1.10.2:
We just need to wait to come to arch repositories:
$: checkupdates
libnma 1.8.40-1 -> 1.10.0-1
libnma-common 1.8.40-1 -> 1.10.0-1
let’s see if i can build it …
validated building them with this commit does remove the issue
It’s on repositories now:
$: checkupdates
libnma 1.8.40-1 -> 1.10.2-1
libnma-common 1.8.40-1 -> 1.10.2-1
This is why I love EOS! 
Well, some little love to Arch as well.
so fast 
Not sure if heftig was not already into it before reporting it…
But i think it is a good idea to help by reporting BUGs. A lot of these issues never get reported and if the maintainer may do not get the issue it takes longer to get the fix in these cases.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.