Control: severity -1 important
積丹尼 Dan Jacobson <jida...@jidanni.org> writes:
> severity 853016 grave
> thanks
> In fact, you terminate the window the aptitude upgrade was running.
> The next time the user runs apt/aptitude, he will be met with
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
> correct the problem.
> W: Could not lock the cache file; this usually means that dpkg or another apt
> tool is already installing packages. Opening in read-only mode; any changes
> you make to the states of packages will NOT be preserved!
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
> correct the problem.
This is documented behaviour and thus not RC, please see the release notes:
"You should not upgrade using telnet, rlogin, rsh, or from an X
session managed by xdm, gdm or kdm etc. on the machine you are
upgrading. That is because each of those services may well be terminated
during the upgrade, which can result in an inaccessible system that is
only half-upgraded."
The package has logic to not restart nodm if the user is logged in (I
think this was copied from gdm3):
if [ "$1" = "remove" ]; then
if [ -x /etc/init.d/nodm ]; then
nostop=
for hostname in "" "localhost" "$(hostname)" "$(hostname -f)"; do
if echo $DISPLAY | grep -q "^$hostname:0.*"; then
nostop=yes
fi
done
if [ -z $nostop ]; then
invoke-rc.d nodm stop
fi
fi
fi
It seems that this didn't work for you for one reason or the other. I'll
look into this.
--
Arto Jantunen
