package squid 2.7.STABLE7-1ubuntu12.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

Due to 5 reports within 18 hours, this appears to be an issue that can be confirmed.

Relevant extract from an english dpkg log:
Setting up squid (2.7.STABLE7-1ubuntu12.1) ...
restart: Job failed to restart
dpkg: error processing squid (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up xkb-data (1.8-1ubuntu8.1~10.04.1) ...

postinst contains, meaning the current status should be well handled.
  if status squid | grep "start/running" > /dev/null; then
        restart squid
  fi

Oddly, on a lucid server with the recent update, I just tried manually restarting squid with hammering upstart commands and got unexpected resolve. :/

dave@vector:~$ sudo restart squid
restart: Job failed to restart
dave@vector:~$ sudo start squid
squid start/running, process 26242
dave@vector:~$ sudo restart squid
restart: Job failed to restart
dave@vector:~$ sudo start squid
squid start/running, process 26576
dave@vector:~$ sudo restart squid
squid start/running, process 26665
dave@vector:~$ sudo stop squid
squid stop/waiting
dave@vector:~$ sudo restart squid
restart: Unknown instance:
dave@vector:~$ sudo start squid
squid start/running, process 27039
dave@vector:~$ sudo restart squid
squid start/running, process 27085
dave@vector:~$ sudo restart squid
squid start/running, process 27131

I noticed that I managed to induce this behaviour by rm'ing the squid log files. Performing the commands in the proposed resolution to bug 717397, i found that the upstart pid for squid != pid squid is running as. Therefore it seems to be the same issue. The -proposed package, squid_2.7.STABLE7-1ubuntu12.1_2.7.STABLE7-1ubuntu12.2 should remedy this bug.

Dave thanks for confirming this one. This is indeed a duplicate of bug #717397, marking as such.