package gnome-power-manager 2.24.0-0ubuntu8.1 failed to install/upgrade: subprocess new post-removal script returned error exit status 1

Asked by Sitarane

Binary package hint: gnome-power-manager

Crash occured during automatic update and while the battery was removed (laptop on AC). My system partition is close to full but still has 200 Mb free. All other update installed fine.

I restarted and replugged the battery in. The uptade icon showed up with only that one update that had failed. I ran it and it worked flawlessly.

Ubuntu Intrepid

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess new post-removal script returned error exit status 1
Package: gnome-power-manager 2.24.0-0ubuntu8.1
SourcePackage: gnome-power-manager
Title: package gnome-power-manager 2.24.0-0ubuntu8.1 failed to install/upgrade: subprocess new post-removal script returned error exit status 1
Uname: Linux 2.6.27-9-generic i686

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-power-manager Edit question
Assignee:
No assignee Edit question
Solved by:
Sitarane
Solved:
Last query:
Last reply:
Revision history for this message
Sitarane (sitarane) said :
#1
Revision history for this message
Chris Coulson (chrisccoulson) said :
#2

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .

Revision history for this message
Chris Coulson (chrisccoulson) said :
#3

Hi,

I converted this to a question as you ran out of disk space, and that is not a bug. As the upgrade failed and the package hasn't configured properly yet, you'll need to finish off the upgrade. To do this, please run "sudo dpkg --configure -a", but only after you have freed up some disk space. Also, could you please post the output of "df -h"?

Revision history for this message
marcobra (Marco Braida) (marcobra) said :
#4

The "dpkg --configure -a" is asked by the system when a previous update/upgrade process have not completely performed good, and it must run with "root" privileged administrative user.
Using the "sudo" command we can do a command as "root" user, and "dpkg --configure -a" need be run from root user.
After the "dpkg --configure -a" command i add all the usual commands (see below) you can run to be sure your system became fully upgraded.

Please also subcribe this bug https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/108601/

Typing the commands as sudo the system will ask you for a password, please give your user password when requested, you don't see nothing when you type it, then press enter.

So please be sure your system is fully updated/upgraded with no pending packages or errors:

Open a Terminal from the menu Applications → Accessories → Terminal and type:
(if the system ask you a password give your user password, you will not see nothing when you type it, then press enter)

sudo dpkg --clear-avail

sudo dpkg --configure --pending
sudo dpkg --configure -a
sudo apt-get -f install
sudo apt-get --fix-missing install
sudo apt-get clean
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt-get clean
sudo apt-get autoremove

Hope this helps

Revision history for this message
Sitarane (sitarane) said :
#5

Thanks. Actually what I did was to "sudo apt-get clean". That freed about
enough space. Then ran the update again and it completed fine.

I'll rearrange my partitions a bit now :)

2009/1/29 marcobra <email address hidden>

> Your question #58987 on gnome-power-manager in ubuntu changed:
>
> https://answers.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+question/58987
>
> marcobra proposed the following answer:
> The "dpkg --configure -a" is asked by the system when a previous
> update/upgrade process have not completely performed good, and it must run
> with "root" privileged administrative user.
> Using the "sudo" command we can do a command as "root" user, and "dpkg
> --configure -a" need be run from root user.
> After the "dpkg --configure -a" command i add all the usual commands (see
> below) you can run to be sure your system became fully upgraded.
>
> Please also subcribe this bug https://bugs.launchpad.net/ubuntu/+source
> /update-manager/+bug/108601/<https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/108601/>
>
> Typing the commands as sudo the system will ask you for a password,
> please give your user password when requested, you don't see nothing
> when you type it, then press enter.
>
> So please be sure your system is fully updated/upgraded with no pending
> packages or errors:
>
> Open a Terminal from the menu Applications → Accessories → Terminal and
> type:
> (if the system ask you a password give your user password, you will not see
> nothing when you type it, then press enter)
>
> sudo dpkg --clear-avail
>
> sudo dpkg --configure --pending
> sudo dpkg --configure -a
> sudo apt-get -f install
> sudo apt-get --fix-missing install
> sudo apt-get clean
> sudo apt-get update
> sudo apt-get upgrade
> sudo apt-get dist-upgrade
> sudo apt-get clean
> sudo apt-get autoremove
>
> Hope this helps
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+question/58987/+confirm?answer_id=3
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
>
> https://answers.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+question/58987
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Sitarane (sitarane) said :
#6

Problem solved