Comment 2 for bug 1187579

I tried tons of upgrades from 202 to 204 yesterday during packaging, and I just re-tried it again on yesterday's daily with udev/logind 202. Do you still have the screen output of the update? (/var/log/dist-upgrade if you used update-manager, or maybe in scrollback?)

udev isn't concerned about /run/user, logind is not restarted during upgrades, and libpam-systemd should only get active if you create a new user session for the same user. The latter is most likely to have happened, can you remember having done something like that? If you still have that broken boot, could you please check the creation and modification dates of /run/user/1000 to see whether it was created before or after the update?

Finally, can you please attach /var/log/auth.log? It may have something interesting.

Thanks!