package sysfsutils 2.1.0-4 failed to install/upgrade:

[Antoine Pairet]

Binary package hint: sysfsutils

while trying to upgrade my system, the package sysfutils failed to install. The install script didn't finished and this automatic bug report was launched.

regards,

The info below is out of date; The system is up to date (26 06 2008) hardy-proposed and hardy-backports enabled.

ProblemType: Package
Architecture: i386
Date: Thu Apr 10 21:50:11 2008
Dependencies:
 libgcc1 1:4.2.3-2ubuntu7
 libsysfs2 2.1.0-4
 gcc-4.2-base 4.2.3-2ubuntu7
 libc6 2.7-10ubuntu3
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: le sous-processus post-installation script a retourné une erreur de sortie d'état 1
NonfreeKernelModules: fglrx
Package: sysfsutils 2.1.0-4
PackageArchitecture: i386
SourcePackage: sysfsutils
Title: package sysfsutils 2.1.0-4 failed to install/upgrade:
Uname: Linux 2.6.24-12-generic i686

[Martin Pitt (pitti)]

Can you please copy&paste the output of the following command (in a terminal):

  sudo apt-get -f install

Thank you!

[Martin Pitt (pitti)]

I guess the reason is that the init script failed. Can you please also copy&paste

  sudo sh -ex /etc/init.d/sysfsutils start

Thank you!

[Antoine Pairet (b-ly)]

After the upgrade failed using "Update Manager", I used "Aptitude" to upgrade my system. So I think the resutls will not be useful.

sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The result of the other command is in attachment.

Should this bug be closed?

Thank you for your great work,

[Martin Pitt (pitti)]

Thanks for the logs. Indeed they are all successful, so I cannot see what went wrong the first time. I close this report now.

If you ever see that happening again, can you please immediately try the "sudo sh -ex /etc/init.d/sysfsutils start" thing? Thank you!

[Antoine Pairet (b-ly)]

Today I upgraded the system and the error happened again. I'll attach the logs asked above.
note: no other update was done between this one and the one when I first reported the bug.

Since I don't experience this bug on my other system, I guess it is specific to that configuration.