Bug#771971: dpkg hangs installing "init" during upgrade from wheezy to jessie
- To: Niels Thykier <niels@thykier.net>, 771971@bugs.debian.org, Steve McIntyre <steve@einval.com>, Dpkg-Maintainers <debian-dpkg@lists.debian.org>, Dominik Schäfer <schaedpq@gmail.com>, bnewbold@robocracy.org
- Subject: Bug#771971: dpkg hangs installing "init" during upgrade from wheezy to jessie
- From: Guillem Jover <guillem@debian.org>
- Date: Sun, 25 Jan 2015 21:11:57 +0100
- Message-id: <[🔎] 20150125201157.GA18806@gaara.hadrons.org>
- Mail-followup-to: Niels Thykier <niels@thykier.net>, 771971@bugs.debian.org, Steve McIntyre <steve@einval.com>, Dpkg-Maintainers <debian-dpkg@lists.debian.org>, Dominik Schäfer <schaedpq@gmail.com>, bnewbold@robocracy.org
- Reply-to: Guillem Jover <guillem@debian.org>, 771971@bugs.debian.org
- In-reply-to: <[🔎] 20150125131802.GA12514@gaara.hadrons.org>
- References: <20141203232449.31525.62183.reportbug@tack.local> <handler.771971.B.141764911925407.ack@bugs.debian.org> <20141204005648.GA16200@einval.com> <20141204005648.GA16200@einval.com> <[🔎] 54C4D3EB.6000305@thykier.net> <[🔎] 20150125131802.GA12514@gaara.hadrons.org>
On Sun, 2015-01-25 at 14:18:03 +0100, Guillem Jover wrote:
> On Sun, 2015-01-25 at 12:30:51 +0100, Niels Thykier wrote:
> > Just to confirm, is this correctly understood?
> >
> > * If you purge "x11-common libx11-6 libx11-data" before upgrading, the
> > upgrade hangs.
> > * If you keep "x11-common libx11-6 libx11-data" as-is, the upgrade
> > succeeds.
> >
> > What state are the above packages before the upgrade?
> >
> > Can you try to reproduce this again and attach strace or/and gdb to the
> > dpkg process when it hangs to figure out what it does/where it is stuck.
> > Based on Dominik's remark (100% cpu usage) in comment #15, I suspect
> > it is in an infinite loop. Though I would appreciate it, if we can
> > confirm or disprove that.
>
> Adding -D77777 to the dpkg call through apt's DPkg::options would be
> helpful. It would also be helpful to know which process hangs, and if
> it's dpkg itself an easy recipe to reproduce this?
I just noticed this was a bug report from December, so I assume this
was possibly one of the dpkg bugs where it was busy looing (#766242
or #766322), which is now fixed?
Although those fixes migrated to testing on 2014-11-03, so I'm not
sure. It would be nice to get more information of the environment at
the time. But if it does not happen anymore then it might indeed be
fixed already. :/
Thanks,
Guillem
Reply to: