Comment 7 for bug 1889080

Hi Alexander, in your tweet you mentioned it was "most likely a user mistake though". Can we deduce that this is a genuine issue on upgrade or was because of changes you made that caused this issue?