wide-dhcpv6-client hangs on upgrade (gutsy->hardy)

Bug #248303 reported by Tanath
14
Affects Status Importance Assigned to Milestone
wide-dhcpv6 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: update-manager

Upgrading to 8.10.

ProblemType: Package
Architecture: i386
Date: Mon Jul 14 01:57:00 2008
DistroRelease: Ubuntu 8.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)

Package: update-manager 1:0.91.7
PackageArchitecture: all
SourcePackage: update-manager
Title: package update-manager 1:0.91.7 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1)
Uname: Linux 2.6.24-19-generic i686

Revision history for this message
Tanath (tanath) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Here is what caused the error:

Setting up wide-dhcpv6-client (20070507-5) ...
 * Starting WIDE DHCPv6 client dhcp6c
 * Starting WIDE DHCPv6 client dhcp6c [ OK ]
dpkg: error processing wide-dhcpv6-client (--configure):
 subprocess post-installation script killed by signal (Interrupt)

Did you press ctrl-c during the upgrade?

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Tanath (tanath) wrote :

After leaving it for quite some time (maybe an hour?), yes.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for this additional information.

This is a bug in the wide-dhcpv6 package then, that it hangs on upgrade.

Changed in wide-dhcpv6:
importance: Undecided → High
status: Incomplete → Triaged
Revision history for this message
Jérémie Corbier (jcorbier) wrote :

Bug fixed in wide-dhcpv6 20080615-2. This was due to debconf not being properly stopped in the postinst script. Thank you for your bug report. Feel free to report any other issue you may encounter.

Cheers,

--
Jérémie

Changed in wide-dhcpv6:
status: Triaged → Fix Committed
Revision history for this message
Jérémie Corbier (jcorbier) wrote :

Ok... Real fix is in wide-dhcpv6 20080615-4 in unstable.

Revision history for this message
Steve Langasek (vorlon) wrote :

wide-dhcpv6 has been synced from Debian unstable, fixing this bug. Changes:

wide-dhcpv6 (20080615-6) unstable; urgency=low

  * debian/patches/102_libc6-2.9-fixes.diff: fix build failures caused by
    headers modifications in the latest libc6 (Closes: #518879).
  * Removed the warning about configuring the client once the install has
    finished since it is not displayed anymore.

 -- Jeremie Corbier <email address hidden> Mon, 09 Mar 2009 11:16:58 +0100

wide-dhcpv6 (20080615-5) unstable; urgency=medium

  * debian/patches/101_close-fds.diff: make sure dhcp6c does not close already
    opened sockets (Closes: #513375).
  * Added Spanish debconf templates translation, thanks to Francisco Javier
    Cuadrado (Closes: #511920).

 -- Jeremie Corbier <email address hidden> Wed, 28 Jan 2009 14:42:49 +0100

wide-dhcpv6 (20080615-4) unstable; urgency=medium

  * debian/patches: added 200_close-fds.diff so wide-dhcpv6 binaries close
    inherited file descriptors, from debconf, for instance (Closes: #512397).
    Thanks to Colin Watson for noticing and providing a fix.
  * debian/wide-dhcpv6-client.config: don't show Debconf note saying that one
    should configure dhcp6c manually right after its installation. This should
    not be needed anymore thanks to profiles/default configuration.
  * debian/watch: use qa.debian.org SourceForge redirector.

 -- Jeremie Corbier <email address hidden> Tue, 20 Jan 2009 15:33:37 +0100

wide-dhcpv6 (20080615-3) unstable; urgency=low

  * debian/patches/200_dhcp6c-profiles.diff: fix a segfault introduced by this
    patch in the case dhcp6c is not given any profile on the command line and
    the interface being handled does not have any configuration statement in
    dhcp6c.conf.

 -- Jeremie Corbier <email address hidden> Mon, 29 Dec 2008 08:50:16 +0100

Changed in wide-dhcpv6:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.