landscape-common post script stuck

post-inst script killed by signal interrupt? Did you hit ctrl+C or anything by any chance while it was updating?

Yeah, that looks odd. Was it stuck perhaps and then you hit ctrl-c?

Logs:
Setting up landscape-common (1.0.23-0ubuntu0.8.10.1) ...

dpkg: error processing landscape-common (--configure):

 subprocess post-installation script killed by signal (Interrupt)

Setting up libsmbios2 (2.0.3-0ubuntu1) ...

Yeah, I was upgrading to 8.10 using apt-get. The console was static for about 5 minutes and no processor usage, so I hit Control-C.

I ended up just removing this package. I think it's for remote management which I do not need.

I'm marking this as invalid, since it was manually caused.

Is there an issue that is already tracking the installer hang then?

On Fri, Oct 31, 2008 at 11:38 AM, Mackenzie Morgan <email address hidden>wrote:

> I'm marking this as invalid, since it was manually caused.
>
> ** Changed in: landscape-client (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> package landscape-common 1.0.23-0ubuntu0.8.10.1 failed to install/upgrade:
> subprocess post-installation script killed by signal (Interrupt)
> https://bugs.launchpad.net/bugs/291282
> You received this bug notification because you are a direct subscriber
> of the bug.
>

You mean apt hang, right?

Do you remember if your root account was locked sometime ago using "passwd -l"?

By "installer" I meant the "post-installation script" run by
landscape-common.

As for the root account, it was set to the Ubuntu default setting. I just
installed 8.04.1 about 1 week before I upgraded to 8.10. I did not set a
root password at that time.

On Fri, Oct 31, 2008 at 1:24 PM, Andreas Hasenack <email address hidden>wrote:

> You mean apt hang, right?
>
> Do you remember if your root account was locked sometime ago using
> "passwd -l"?
>
> --
> package landscape-common 1.0.23-0ubuntu0.8.10.1 failed to install/upgrade:
> subprocess post-installation script killed by signal (Interrupt)
> https://bugs.launchpad.net/bugs/291282
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Not sure if this is related, but:
--------------------------------------------------
Could not install 'landscape-common'

The upgrade will continue but the 'landscape-common' package may be in a not working state. Please consider submitting a bugreport about it.

subprocess post-installation script returned error exit status 1

I don't think this is the PAM timeout issue. That would've shown in the log. It's not there.

On #ubuntu-bugs, Chris Coulson suggested it could be related to it trying to use update-motd in the postinst script without update-motd being a pre-depends so if it's configured after landscape, the landscape postinst script could do unexpected things.

Hmm, the logs show things being installed in apparently the right order:
- unpack update-motd
- unpack landscape-common
- setting up update-motd
- setting up landscape-common

This may be the same as bug #277038

Reinstalled it and it worked OK. (I think; there weren't any errors)

Thanks. I'll mark it as a duplicate, and we just got another similar report too.