landscape-client 1.0.18-0ubuntu1 install stopped at useradd/chfn

I'm experiencing almost the same error.
Additionally, apt-get complains my disabled root account, so I even don't get a prompt for a password.
apt-get -f install - output:

Setting up landscape-client (1.0.18-0ubuntu1) ...
ln: creating symbolic link `/etc/update-motd.d/50-landscape-sysinfo': File exists
dpkg: error processing landscape-client (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 landscape-client
E: Sub-process /usr/bin/dpkg returned an error code (1

We are currently making some changes to the packaging layout of landscape-client and its dependencies. We will retest this bug once those changes land in Intrepid (which should happen really soon now).

The symlink error from comment #2 is fixed in 1.0.18-0ubuntu4.

The original error, though, looks different. From the logs, it looks like it was hung in the adduser part (chfn), so I'm wondering if there is perhaps some nis/ldap/winbind setup here. Landscape-client does add a system user as part of the installation. Michael, do you have some setup like that involving network users?

Andreas,

no network users of any type were on that system. Also no nis, ldap or winbind setup, unless some package sneaked something in behind my back.

I did use smb shares on the network though as a client, but only with my regular local user account.

So, I don't know why it was hung in the adduser part. If you upgrade to the latest release of the package (ubuntu4 as of now, but I'm not sure if it's already in the mirrors), does it at least upgrade or does it hang again?

Unfortunately I had to remove Intrepid from the notebook a few days ago because it was a loaner and had to be returned. Sorry I can't help any longer with the original problem. I did test with the new notebook I got in exchange. There the ubuntu4 version upgraded just fine.

Hello all,

did any of you by any chance had a locked root account? Like what happens when issuing "passwd -l root".
If yes, then this whole ticket may actually be about bug #238755.

no, no locked root. Had that one on beta HH ;-) Iwas just updating, and
installed Nvidia driver (173 i think) after reboot it all went south.

On Mon, Oct 6, 2008 at 9:37 PM, Andreas Hasenack <email address hidden>wrote:

> Hello all,
>
> did any of you by any chance had a locked root account? Like what happens
> when issuing "passwd -l root".
> If yes, then this whole ticket may actually be about bug #238755.
>
> --
> landscape-client 1.0.18-0ubuntu1 install stopped at useradd/chfn
> https://bugs.launchpad.net/bugs/268039
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I never unlocked the root account. So, yes, the root account should have been locked at the time the error ocurred.

Michael, in this case, by "locked", I mean explicitly running the "passwd -l root" command as root.

Andreas, I definitely never ran "passwd -l root" on the system.

Michael, can you run this command as root, please:

chfn <your-login-name>

You don't need to finish the command if it starts prompting you. Here is an example of it failing, and I would actually like to know if it fails like this for you:

root@nsn2:~# chfn andreas
Your account has expired; please contact your system administrator
chfn: PAM authentication failed
root@nsn2:~#

Andreas, since I don't have the original notebook anymore (see comment 7) does this test still apply? When running chfn on the current subnotebook there is no error:

root@littleangel:~# chfn mhuettemann
Ändere Benutzerinformationen für mhuettemann
Geben Sie einen neuen Wert an oder drücken Sie ENTER für den Standardwert
 Vollständiger Name [Mike]: