Comment 13 for bug 294389

Hagyan - That's the answer I was hoping for.

Martin - DId your upgrade get interrupted? The reason I ask is that I looked at your log and there appears to be an interruption between the system-tools-backends package being unpacked and the package being configured. If it was interrupted for example by a crash, causing you to reboot, then it would fail when dpkg tried to configure the package later on. If that's the case, then this just backs up the theory.

The bit of your log that looks suspicious is this (notice the line beginning "Unpack" and then the "Log started" message, which suggests that the package upgrade got interrupted):

Preparing to replace system-tools-backends 2.6.0-1ubuntu1 (using .../system-tools-backends_2.6.0-1ubuntu1.1_i386.deb) ...

 * Stopping System Tools Backends system-tools-backends 
[ OK ]

Unpack
Log started: 2008-11-07 10:16:58
Selecting previously deselected package nmap.

(Reading database ... 125193 files and directories currently installed.)

Unpacking nmap (from .../nmap_4.62-1ubuntu1_i386.deb) ...

Processing triggers for man-db ...

Setting up system-tools-backends (2.6.0-1ubuntu1.1) ...

 * Starting System Tools Backends system-tools-backends  invoke-rc.d: initscript system-tools-backends, action "start" failed.

dpkg: error processing system-tools-backends (--configure):

 subprocess post-installation script returned error exit status 1