Upgrade gutsy -> hardy, faled for packages: samba-common, smbclient, ubuntu-desktop, bash-completion

[deniv]

Binary package hint: samba

While upgrading from Gutsy 64x to Hardy, Distribution Upgrade hangs at packages samba-common and bash-completion. The "top" command indicates extensive CPU and swap usage by "ucf". After I press Ctrl-C the upgrade continues. Please see also screen-shots and system log files attached with this report.
This problem is reproduced each time I try to run an upgrade (from fresh installation of Gutsy). When I try to install Hardy 64x directly, rather than running an upgrade, the installation hangs as well but there's less possibilities to gather system information.

ProblemType: Package
Architecture: amd64
Date: Sun May 25 18:21:52 2008
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: subprocess post-installation script killed by signal (Interrupt)
Package: samba-common 3.0.28a-1ubuntu4
PackageArchitecture: amd64
SourcePackage: samba
Title: package samba-common 3.0.28a-1ubuntu4 failed to install/upgrade:
Uname: Linux 2.6.22-14-generic x86_64

[Rolf Leggewie (r0lf)]

dupe of bug 221963?

[J Posey (jpo)]

My attempt to upgrade hung at samba-common. After restarting the system boots, accepts user-name and password, but once desktop is up, keyboard is no longer decoded properly (some keys send nothing, others gibberish). Mouse still works.

This problem is critical in my opinion. If an upgrade can completely disable an end-users desktop, the OS is not ready for everyday users. I regret having recommended it based on experience prior to now.

[Steve Langasek (vorlon)]

Thank you for taking the time to report this bug and help to improve Ubuntu.

I sympathize with the concern that package upgrades should not be breaking the system, but this problem is not reproducible for me. Can someone who is seeing this behavior (ucf spinning) try to attach to the process with strace and send the resulting strace log?

[Jean-Baptiste Lallement (jibel)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!