erlang and erlang-base break Dapper-Edgy upgrade

Both dialog boxes said "The upgrade aborts now", but it did not seem to do so; it went to the cleanup stage and then told me to reboot. However, I currently have broken fonts in all applications and some icons are displaying as the red-X "missing" icon, so I don't know whether my system may have been rendered unbootable by the broken upgrade. This is a highly confusing state to be in. See the broken-fonts.png screenshot attached; note particularly the fonts in the menus and in xchat, and the broken icons on the Gimp menu, in the bottom corner of xchat, and on the panel (which was Byzanz).

I have also tried removing the erlang and erlang-base packages with apt-get from the command line; it insisted I run apt-get -f install, which is now installing many packages. It's completely unclear what to do if an upgrade fails like this, and most people would not know about apt-get -f install; I am not at all sure that this will actually complete the upgrade successfully.

After apt-get -f install finally completed, I re-ran apt-get remove erlang erlang-base, and then re-ran the upgrade. It completed successfully and rebooted into a full Edgy install.

The error from the terminal log:

dpkg: error processing /var/cache/apt/archives/erlang-base_1%3a11.b.1-1_i386.deb (--unpack):
 subprocess pre-removal script returned error exit status 2

Thanks for your bugreport.

The fonts look/looked that bad because the upgrade couldn't be finished and so some packages from the system are missing that provide the better looking fonts.

Unable to comment other than to say wings 3D has always worked for me. I did a complete install of edgy from CD to a clean partition and Wings3D will not work erlang crashes.

Confirming on update-manager, as normal log files are there.

Is it still an issue when upgrading to newer release ? Thanks in advance.

We are closing this report because you reported this bug a while ago and there is no recent duplicate nor user mentioning having the issue on Intrepid. If this is still an issue, don't hesitate to reopen the report. Thanks again!