[arch-general] SOLVED Re: Cannot chroot '/bin/bash': No such file or directory

[Martti Kühne]

On Tue, Mar 12, 2013 at 10:13 PM, David C. Rankin
<drankinatty at suddenlinkmail.com> wrote:
<snip>
> [2013-02-05 23:45] synchronizing package lists
> [2013-02-05 23:45] starting full system upgrade
> [2013-02-05 23:53] removed eject (2.1.5-7)
> [2013-02-05 23:53] userdel: user dbus is currently used by process 452
> [2013-02-05 23:53] groupdel: cannot remove the primary group of user 'dbus'
> [2013-02-05 23:53] removed dbus-core (1.6.4-1)
>
> <snip> (don't know if this is important -- repeated twice in log)
>
> [2013-02-05 23:53] /usr/bin/gconftool-2: error while loading shared libraries:
> libdbus-1.so.3: cannot open shared object file: No such file or directory
> [2013-02-05 23:53] /usr/bin/gconftool-2: error while loading shared libraries:
> libdbus-1.so.3: cannot open shared object file: No such file or directory
>
> <snip>

this is definitely related to the above "removed dbus-core (1.6.4-1)" entry.
All I can say that here on my work setup with KDB (the 'B' is for bloat) I have
only a dbus 1.6.8-6 package and no dbus-core.

>
> [2013-02-05 23:53] upgraded linux-api-headers (3.5.1-1 -> 3.7.4-1)
> [2013-02-05 23:53] upgraded tzdata (2012e-1 -> 2012j-1)
> [2013-02-05 23:53] warning: /etc/gshadow installed as /etc/gshadow.pacnew
> [2013-02-05 23:53] warning: /etc/passwd installed as /etc/passwd.pacnew
> [2013-02-05 23:53] warning: /etc/group installed as /etc/group.pacnew
> [2013-02-05 23:53] warning: /etc/fstab installed as /etc/fstab.pacnew
> [2013-02-05 23:53] warning: /etc/shadow installed as /etc/shadow.pacnew
> [2013-02-05 23:53] upgraded filesystem (2012.8-1 -> 2013.01-3)
> [2013-02-05 23:53] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
> [2013-02-05 23:53] call to execv failed (No such file or directory)
> [2013-02-05 23:53] upgraded glibc (2.16.0-4 -> 2.17-3)
> [2013-02-05 23:54] call to execv failed (No such file or directory)
> [2013-02-05 23:54] upgraded bash (4.2.037-1 -> 4.2.042-3)
> [2013-02-05 23:54] call to execv failed (No such file or directory)

as sysadmin of your archlinux system you should take care of pacnew files
in your filesystem. I myself run

# find / -xdev -regextype posix-egrep -regex '.*\.pac(new|old|save)' | less

in a terminal/tmux window from time to time to find these files.
In another window I then diff and add the local modifications to the
pacnew files or the new additions to the old files, depending on what looks
like more work. That way you also have a very good idea of what is actually
going on on your system, and, of course, in archlinux on another end.

That reminds me, I still have the initscripts pacsave files of which I don't
know if they will ever come in handy at some point, but I'll have them lying
around anyway.

chers!
mar77i