AJ> This is documented behaviour and thus not RC, please see the release notes:
AJ> "You should not upgrade using telnet, rlogin, rsh, or from an X AJ> session managed by xdm, gdm or kdm etc. on the machine you are AJ> upgrading. That is because each of those services may well be terminated AJ> during the upgrade, which can result in an inaccessible system that is AJ> only half-upgraded." Well I was using nodm at the time, not any of those. AJ> The package has logic to not restart nodm if the user is logged in (I AJ> think this was copied from gdm3): AJ> if [ "$1" = "remove" ]; then AJ> if [ -x /etc/init.d/nodm ]; then AJ> nostop= AJ> for hostname in "" "localhost" "$(hostname)" "$(hostname -f)"; do AJ> if echo $DISPLAY | grep -q "^$hostname:0.*"; then AJ> nostop=yes AJ> fi AJ> done AJ> if [ -z $nostop ]; then AJ> invoke-rc.d nodm stop AJ> fi AJ> fi AJ> fi AJ> It seems that this didn't work for you for one reason or the other. I'll AJ> look into this. I'm not sure why that failed either. Wouldn't it be best just to let the user start and stop it by himself? Just like when upgrading linux-image, xorg, etc. No reason to halt the running version right now. _______________________________________________ pkg-fso-maint mailing list pkg-fso-maint@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-fso-maint