googleearth-4.2: sub-process post-removal script outputs error code 128

Bug #290621 reported by Matthias Mailänder
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Medibuntu
Won't Fix
Undecided
Unassigned
Lucid
Won't Fix
Low
Unassigned
Maverick
Won't Fix
Undecided
Unassigned

Bug Description

Can't completely remove the package googleearth-4.2 version 4.2.205.5730-0medibuntu4 (hardy).

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Please provide more infos (/var/log/apt/term.log may be a good start).
Thanks.

Changed in medibuntu:
status: New → Incomplete
Revision history for this message
Matthias Mailänder (mailaender) wrote :
Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Thanks.

According to the log file, your MIME database seems to contain strange keys, such as 'chemical/x-alchemy'. Googleearth package removal script calls "update-mime-database /usr/share/mime", which probably fails because of these strange mimetypes.

This does not look like a bug in googleearth package though.

Revision history for this message
Matthias Mailänder (mailaender) wrote :

Okay, removing the package chemical-mime-data fixed the problem. So this is in fact Bug #217335

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

It is really hard to add a "set -ex" to the postrm script to check this claim:

+ exec /usr/share/debconf/frontend /var/lib/dpkg/info/googleearth-4.2.postrm purge
+ which update-mime-database
+ [ -x /usr/bin/update-mime-database ]
+ update-mime-database /usr/share/mime
+ which update-mime
+ update-mime
+ [ purge = purge ]
+ [ -e /usr/share/debconf/confmodule ]
+ . /usr/share/debconf/confmodule
+ [ ! 1 ]
+ [ -z ]
+ exec
+ [ ]
+ exec
+ DEBCONF_REDIR=1
+ export DEBCONF_REDIR
+ db_purge
+ _db_cmd PURGE
+ IFS= printf %s\n PURGE
+ IFS=
 read -r _db_internal_line
+ RET=20 Unsupported command "unknown" (full line was "Unknown media type in type 'chemical/x-alchemy'") received from confmodule.
+ return 20

This is clearly *not* failing during update-mime-database!

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Right, but this bug occurs because of chemical-mime-data (because the chemical/* mimetypes aren't registered to the IANA yet).

Changed in medibuntu:
status: Incomplete → Invalid
Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

I sent a mail to the debconf maintainers and debian-devel to discuss the issue.
http://lists.debian.org/debian-devel/2008/10/msg00790.html

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

It will fail with *every* output created by the postrm script and the commands it calls. You can reproduce it by simply adding

echo "Make me fail."

to the postrm script (and without c-m-d) and it will fail too. This is not fault of c-m-d.

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Daniel: What's the status of this? Has a bug been filed against debconf/shared-mime-info?

Changed in medibuntu:
importance: Undecided → Low
status: Invalid → Confirmed
Revision history for this message
Chris Jones (foxmulder881) wrote :

I am getting this error when attempting to completely-remove googleearth-4.2. It can't be anything to do with the chemical-mime-data package as I don't even have it installed on my system and never have.

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote : Re: [Bugs] [Bug 290621] Re: googleearth-4.2: sub-process post-removal script outputs error code 128

On Sat, Dec 13, 2008 at 06:47:36AM -0000, Chris Jones wrote:
> I am getting this error when attempting to completely-remove
> googleearth-4.2. It can't be anything to do with the chemical-mime-data
> package as I don't even have it installed on my system and never have.
>

Could you edit the postrm script
(/var/lib/dpkg/info/googleearth-4.2.postrm), and replace "set -e" by
"set -x" at the beginning? There is probably a command that outputs
something and triggers this issue as well.

--
Lionel Le Folgoc - https://launchpad.net/~mrpouit
EEBA 555E 0CDE 92BB 3AF4 4AB3 45A0 357B 5179 5910

Revision history for this message
Chris Jones (foxmulder881) wrote :

I tried to edit /var/lib/dpkg/info/googleearth-4.2.postrm and got the following output:
Note: I occasionally get this output when installing/removing applications yet I have no idea what is triggering it.

"chris@ubuntu:~$ sudo /var/lib/dpkg/info/googleearth-4.2.postrm
Unknown media type in type 'all/all'

Unknown media type in type 'all/allfiles'

Unknown media type in type 'uri/mms'

Unknown media type in type 'uri/mmst'

Unknown media type in type 'uri/mmsu'

Unknown media type in type 'uri/pnm'

Unknown media type in type 'uri/rtspt'

Unknown media type in type 'uri/rtspu'

Unknown media type in type 'fonts/package'

Unknown media type in type 'interface/x-winamp-skin'"

Revision history for this message
Chris Jones (foxmulder881) wrote :

Disregard my comment above as I had forgotten to add "gedit" after "sudo".

I tried again and edited the file and then tried to completely remove googleearth-4.2 again but still receive the same original error message.

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

It is still the same issue. update-mime-database throws some warnings to stdout, which makes debconf fail.

Revision history for this message
Sparky432 (sparky432) wrote :

I also had this issue in Intrepid after installing googleearth from the Medibuntu repository. I finally managed to purge the googleearth-4.2 package which was causing dpkg errors by making the changes below to
/var/lib/dpkg/info/googleearth-4.2.postrm

"
You can also try to replace:
        update-mime-database /usr/share/mime
with:
        update-mime-database /usr/share/mime >/dev/null 2>&1
 "
(as given by Lionel Le Folgoc in https://bugs.launchpad.net/medibuntu/+bug/299430/comments/5)

Attached is the terminal output showing the errors I was getting before.

Revision history for this message
Chris Jones (foxmulder881) wrote :

Thanks Sparky432. That worked. Cheers mate.

Revision history for this message
Gijs ter Beek (gijsterbeek) wrote :

Also works with Google Earth 4.3 ;)

Changed in medibuntu:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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