[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#770448: Setting up libpam-modules-bin (1.1.8-3.1) hangs forever

Hi Steve,

thanks for your feedback on this!

On Freitag, 21. November 2014, Steve Langasek wrote:
> The libpam-modules-bin package ships no maintainer scripts.  Therefore
> there is nothing at the "setting up" stage which is under control of this
> package. Your ps output also shows that the package currently being
> installed is libpam-modules, *not* libpam-modules-bin.  libpam-modules
> does have maintainer scripts, but your output doesn't show the line that
> would be expected, "Preparing to unpack", which should be emitted before
> the (debconf-using) preinst script is called.

actually it is, I just ommited quoting it.

Selecting previously unselected package init.
(Reading database ... 222703 files and directories currently installed.)
Preparing to unpack .../archives/init_1.21_amd64.deb ...
Unpacking init (1.21) ...
Setting up init (1.21) ...
(Reading database ... 222706 files and directories currently installed.)
Preparing to unpack .../libpam-modules-bin_1.1.8-3.1_amd64.deb ...
Unpacking libpam-modules-bin (1.1.8-3.1) over (1.1.3-7.1) ...
Replacing files in old package libpam-modules:amd64 (1.1.3-7.1) ...
Setting up libpam-modules-bin (1.1.8-3.1) ...

full quote at https://jenkins.debian.net/view/d-i_manual/job/chroot-

> So this doesn't look to me like a bug in the pam package.  It would be
> interesting to know what 'pidof xscreensaver xlockmore' returns on the
> affected system, in case there is some interaction with the preinst script.

it returns nothing, there is no X running on the jenkins server...

So I'm still in the dark as to what causes this...


Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: