package mono-apache-server 2.0-0ubuntu1 failed to install/upgrade: subprocess post-installation script killed by signal (Interrupt)

Okay, that bug merge fest was fun.

Firstly, sorry for this bug being such an ongoing issue. For those who thought it was caused by the hostname resolution thing, it's not - that's a normal enough message from Apache on non-webhost machines. I test exclusively on machines with that error.

Secondly, I've made a whole bunch of changes to mod-mono packages in general on Karmic, and am unable to reproduce your bug. That's not to say that it never happened, nor that it might not happen again to YOU if you have old (stale) config files lying about which are causing confusion. Frankly, I'm not too sure where it was getting lost in the post-install, but that script has been rewritten a bit.

I'd recommend that you remove the existing package, purge all related config files from /etc/mono-server*, and THEN try installing again, afresh, on Karmic. For now, I'm making this bug as "Invalid" since I can't reproduce it - and because I wouldn't be able to push back any of my (invasive) changes to an older release via a backport anyway.

This ( and other bugs ) seem to be a result of the console ( displaying output from the update script ) hanging. I wonder if this is simply the embedded console being made a zombie/orphan or the embedded console waiting for the ( now stopped ) Apache2 process to close it down in some way ) after the Apache2 process restarts. Something of a wild guess I admit, but perhaps someone who knows how that embedded console gets created can think about it. ( It appears in the Synaptic update progress dialog during the Apache2 module install and update - I was adding Mono modules when I saw it ).

There are several bug reports that seem related to this.

I think this is a serious issue. Anything that could ( even potentially ) break software updates in progress could be catastrophic. I would suggest giving this a higher importance.