I'm using Debian Unstable and last night I tried to do a distribution upgrade with synaptic. It returned an error message that errors were generated and couldn't finish, so as a result mozilla and several other mozilla-related packages are 'broken'. Dpkg-reconfigure says the same thing. I think the problem package is mozilla-xft. When I try to uninstall the broken ones I get a message telling me to try installing them first. Trying to install either mozilla or mozilla-xft gives me this:

Preparing to replace mozilla-xft 2:1.6-2 (using .../mozilla-xft_2%3a1.6-2_i386.deb) ...
Leaving `diversion of /usr/lib/mozilla/components/libgfx_gtk.so to /usr/lib/mozilla/components/libgfx_gtk.so.pure by mozilla-xft'
Unpacking replacement mozilla-xft ...
Updating mozilla chrome registry.../usr/sbin/update-mozilla-chrome: line 68: unexpected EOF while looking for matching `}'
dpkg: warning - old post-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
Updating mozilla chrome registry.../usr/sbin/update-mozilla-chrome: line 68: unexpected EOF while looking for matching `}'
dpkg: error processing /var/cache/apt/archives/mozilla-xft_2%3a1.6-2_i386.deb (--unpack):
subprocess new post-removal script returned error exit status 2
Updating mozilla chrome registry.../usr/sbin/update-mozilla-chrome: line 68: unexpected EOF while looking for matching `}'
dpkg: error while cleaning up:
subprocess post-removal script returned error exit status 2
Errors were encountered while processing:
/var/cache/apt/archives/mozilla-xft_2%3a1.6-2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any ideas on how to fix mozilla?

have u tried running apt-get -f install
that should install stuff for you.else what you can do is an apt-get clean and then apt-get update.
i think this way apt forgets that it was trying to install mozilla.well...worth a shot anyways.
the same kind of thing happened to me...well it did not break anything but all my bookamrks were lost which was too bad since i did have a couple of marks which i cant find now.

yup, tried it, still same errors. It seems to do exactly the same steps, and I think the error occurs when trying to configure mozilla, but I can't even run mozilla (the command doesn't exist).

so did u clean the apt repository where it has all its debs?/var/apt
ummm...i dont really know what more i can say...i mean apt-get -f install always worked for me.
you can probably download a .deb for mozilla and install that.maybe that will help.

Yeah, I cleaned out the deb files, I don't think thats the problem. Do the deb files affect the removal of a package? This is getting stranger and stranger...I managed to remove most of the mozilla packages including mozilla-xft (which i thought was causing all the problems) when I tried to downgrade mozilla to testing (I had to downgrade lbsnpr4 too). Now I'm still stuck with mozilla-psm and mozilla-mailnews marked for removal and I get the same error message from the 'updating chrome registry' part when I try to get rid of them.

It tells you in the output what is wrong there is an EOF while it is still looking for a } bracket in the /usr/sbin/update-mozilla-chrome file I would suggest going to http://bugs.debian.org and searching the BTS to see if you can find a report there is usually a solution or patch posted in the reports somewhere. Have you heard of apt-listbugs and you may want to check out apt-listchanges as well, I do not know if they work with synaptic but it is worth checking to see if they will.

I looked again and turns out someone just submitted a bug report today http://bugs.debian.org/cgi-bin/bugre...gi?bug=237647. Thanks for your help guys!

interesting.umm....could u tell me how to apply the patch given in the mail(it is a patch right?).
Thanks

I'm pretty what it says is the lines marked - are the old working lines and the ones marked + are the new messed up ones. So the end result is you have to edit the script /usr/sbin/update-mozilla-chrome and change a few } to ].

hmm, I think he mislabeled his examples now that I look at it, I'm pretty sure those lines show up as {something] in the buggy file and you have to make them { }.