package powernowd 1.00-1ubuntu5 failed to install/upgrade:

[Thomas Boyda]

Binary package hint: powernowd

I was upgrading from 8.04 to 10.4 on my Toshiba laptop with AMD Athelon X2 64-bit processor with 4GB of RAM.

The install script was stuck waiting for powernowd to start. It appeared that powenowd was running:

tboyda@tboyda-laptop:~$ ps -ef | grep -i power
root 5626 27523 0 12:35 pts/1 00:00:00 /bin/sh /var/lib/dpkg/info/powernowd.postinst configure 0.97-2ubuntu4
root 5711 5626 0 12:35 pts/1 00:00:00 /bin/sh /tmp/tmphlQd7e/imported/invoke-rc.d powernowd start
root 5727 5711 0 12:35 pts/1 00:00:00 /bin/sh /etc/init.d/powernowd start
tboyda 5858 5833 0 13:45 pts/2 00:00:00 grep -i power
tboyda 6101 1 0 08:44 ? 00:00:04 gnome-power-manager
tboyda@tboyda-laptop:~$

It had saw waiting for powernowd for about 45 minutes before I killed the process to get the install to continue.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: powernowd 1.00-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.24-28.71-generic
Uname: Linux 2.6.24-28-generic x86_64
NonfreeKernelModules: fglrx ath_hal
Architecture: amd64
Date: Mon Aug 2 13:45:42 2010
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script killed by signal (Terminated)
SourcePackage: powernowd
Title: package powernowd 1.00-1ubuntu5 failed to install/upgrade:

[Thomas Boyda (thomas-boyda)]

tboyda@tboyda-laptop:~$ lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
tboyda@tboyda-laptop:~$ apt-cache policy powernowd
powernowd:
  Installed: 1.00-1ubuntu5
  Candidate: 1.00-1ubuntu5
  Version table:
 *** 1.00-1ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status
tboyda@tboyda-laptop:~$

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 442065, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.