The libbloom package prior to version 1.6-2 was missing a soname link. This has been fixed in 1.6-2, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error
libbloom: /usr/lib/libbloom.so.1 exists in filesystem
The tensorflow packages prior to version 1.14.0-5 were missing some soname links. This has been fixed in 1.14.0-5, so the upgrade will need to overwrite the untracked soname links created by ldconfig. If you get an errors like so.
tensorflow: /usr/lib/libtensorflow.so.1 exists in filesystem
tensorflow: /usr/lib/libtensorflow_cc.so.1 exists in filesystem
tensorflow: /usr/lib/libtensorflow_framework.so.1 exists in filesystem
The astyle package prior to version 3.1-2 was missing a soname link. This has been fixed in 3.1-2, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error
astyle: /usr/lib/libastyle.so.3 exists in filesystem
I see that Nim has already been updated to v1.0, wow! (the release was yesterday evening)
If somebody on testing branch (I'm on stable) could just double-check something, it would be great. There was a last-minute fix, after v1.0 has been already tagged, so everything was re-tagged after the fix — just to make sure that the Manjaro has the correct updated version.
Can you please install Nim and check the printed git hash after you do nim -v? If you see git hash: f7a8fc46c0012033917582eb740dc0343c093e35 then everything is ok, that is the correct git hash.
Press Ctrl+Alt+F3 to access TTY3 and then Ctrl+Alt+F1 and see if that unlocks the screen. If not, then go back to TTY3, log in as your user and run systemctl reboot.
If all this persists, that means you have an extension that prevents GDM to start properly. Think what that might be and report back.
Thanks for the answer @bogdancovaciu, i just tried what you suggest but i can´t unlock the screen. I had just a feel extensions installed (ARC MENU, DASH TO PANEL and VITTALS). Is there a way to uninstall the gnome-extensions by the CLI ?
All my machines updated without issue except my haunted one (Absu).
Was running linux53 during the update. Something in the update nuked my internet.
No errors in Journal or dmesg. Would show link was up and connected but no internet. Turned off VPN to eliminate variables.
Confirmed with another computer I actually had internet, affirmative.
Deleted all Network-Manglers saved connections. No joy.
Changed to Linux52, Internet was back.
So you got me. Linux53 will not connect now for me using Linux53.