metacity-common post-removal script returned error exit status 127

Bug #538360 reported by David Robert Lewis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Preparing to replace metacity-common 1:2.28.0-0ubuntu1 (using .../metacity-common_1%3a2.28.0-0ubuntu2_all.deb) ...
Unpacking replacement metacity-common ...
/var/lib/dpkg/info/metacity-common.postrm: 11: update-gconf-defaults: not found
dpkg: warning: old post-removal script returned error exit status 127
dpkg - trying script from the new package instead ...
/var/lib/dpkg/tmp.ci/postrm: 11: update-gconf-defaults: not found
dpkg: error processing /var/cache/apt/archives/metacity-common_1%3a2.28.0-0ubuntu2_all.deb (--unpack):
 subprocess new post-removal script returned error exit status 127
/var/lib/dpkg/tmp.ci/postrm: 11: update-gconf-defaults: not found
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 127
Preparing to replace python-libxml2 2.7.5.dfsg-1ubuntu1 (using .../python-libxml2_2.7.5.dfsg-1ubuntu1.1_i386.deb) ...
/var/lib/dpkg/info/python-libxml2.prerm: 6: update-python-modules: not found

Revision history for this message
Monkey (monkey-libre) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in metacity.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → metacity (Ubuntu)
Revision history for this message
David Robert Lewis (afrodeity) wrote :

I've solved the problem which comes down to interpretation of python on a system with python 2.5 AND python 2.6 installed.

http://ubuntuforums.org/showthread.php?p=8939571#post8939571

Revision history for this message
Monkey (monkey-libre) wrote :

Thank You for your answer, I´ve closed this bug, please if You have any problem with this, reopen it.

Thank You for making Ubuntu better.

Changed in metacity (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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