My problem is that I can't login. If I try to loggin with correct username and password it doesn't do anything. I have error message on boot failed to create static device Nodes in /dev
. This happened after sudo pacman -Sy xterm
and restart of the system. My kernel version is 4.1.6-1-ARCH
This is not my image but by this I mean loggin session..
2 Answers
Libncurses was recently updated from /usr/lib32/libncursesw.so.5
to /usr/lib32/libncursesw.so.6
. There would have been a matching bash update, but you don't have it.
In fact, I just found this in my own pacman.log
:
[2015-09-19 23:45] [ALPM] upgraded ncurses (5.9-7 -> 6.0-3)
[2015-09-19 23:45] [ALPM] upgraded readline (6.3.008-1 -> 6.3.008-3)
[2015-09-19 23:45] [ALPM-SCRIPTLET] /usr/bin/bash: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory
[2015-09-19 23:45] [ALPM] upgraded bash (4.3.042-1 -> 4.3.042-3)
This is why you should update everything or nothing.
You should get a LiveCD, mount the drive, and do the updates like this:
pacman --root=/path/to/mounted/root -Suy
I had this exact same issue after doing a full system upgrade.
Installing the updates with pacman --root=/mnt -Syu as described by "ams" did not resolve the problem for me; instead I had to symlink the library, i.e.
cd /usr/lib
ln -s libncursesw.so.6 libncursesw.so.5
However, after doing this, I can't run gnome-terminal (I have this issue: gnome-terminal stopped working). That's probably not related to the ncurses issue, though.
-
1Linking the two together is unlikely to work properly because the two libraries have different binary interfaces. Nov 14, 2015 at 12:11
-
1
-
Ignore what I previously wrote about xterm input being messed up. I had recompiled xterm ages ago with some... let's just say experimental modifications, left it in /usr/local/bin, and forgot about it. Upon moving that binary elsewhere, xterm is absolutely fine.– KeijiNov 14, 2015 at 20:38
-
s
(single user mode) runlevel, or even without a genuine init (init=/bin/bash
). Then examine the root file system for damage.