Comment 52 for bug 1277589

Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

I have triggered it again on 216 upgrading to 217.

To be clear, I'm *not* upgrading, but starting the upgrade then pressing back, then going back in later, and then the error appears. Here's a video:-

https://www.youtube.com/watch?v=YmD6cGYvIAI