So, the situation has changed a bit with Karmic as update-motd is gone, replaced by pam-motd. landscape-sysinfo is not run by cron anymore, apparently on login directly. But the problem is basically the same: if you login during an upgrade, an apport bug will be fired. Note that the motd won't be broken, probably because it detects the error code and thus don't copy the new motd.
Anyway, the way to fix it is to catch the error in landscape-sysinfo, so that the exception doesn't bubble up, but still exit with an error status, so that the motd is not updated. This is what I've done in the branch.
So, the situation has changed a bit with Karmic as update-motd is gone, replaced by pam-motd. landscape-sysinfo is not run by cron anymore, apparently on login directly. But the problem is basically the same: if you login during an upgrade, an apport bug will be fired. Note that the motd won't be broken, probably because it detects the error code and thus don't copy the new motd.
Anyway, the way to fix it is to catch the error in landscape-sysinfo, so that the exception doesn't bubble up, but still exit with an error status, so that the motd is not updated. This is what I've done in the branch.