Comment 66 for bug 807306

Martin,

> No, it's set up in an upstart job, so you need to reboot after
> the upgrade.

Now that is strange, I rebooted already several times, but the situation did not change. Maybe there is a chicken-and-egg problem of upstart not triggering the symlink creation because there are still old (pid, ...) files in the directory?

> But still, you shouldn't do that with half of the
> packages being unconfigured due to the aborted update.

I'll do the update/dist-upgrade this evening and report success/failure.

Thanks,
Eduard