Comment 7 for bug 1703358

According to my history.log, I upgraded from ubuntu-session 3.24.1-0ubuntu8 to 3.24.1-0ubuntu9 on 2017-07-03. Then from 3.24.1-0ubuntu9 to 3.24.1-0ubuntu11 on 2017-07-10 (today). I think you're looking at an older part of my log?

I only had the display manager prompt on upgrade today, defaulting to lightdm.

So it seems that I did have the migration script on upgrade today, but it didn't do the right thing (today). It could be that stepping through 3.24.1-0ubuntu8 and 3.24.1-0ubuntu9 on the way to 3.24.1-0ubuntu11 triggers the issue, though I have no particular reason to believe that. But if that is what triggers it, it's still a bug as other users might step through the same way too.