I think we are missing a piece of the puzzle here. The upgrade from 66 to 67 works for me as well on Ubuntu 16.04 and ubuntu 18.04, both with canonical and Mozilla builds. I can't really wrap my head what could generate this kind of behavior from the profiles point of view. Maybe Dave could get more info out of poc file. What would probably would be helpful is if trittweiler@gmail could assist a bit more into building up a scenario that we can use reproduce this behavior reliably: 1. Can you clarify if the profile used after update is the same profile than the one before the update. (about:profiles) 2. Confirm that the symlink is the default one. If there's anything custom about the symlink is done, it would probably be good to know. 3. Can the same scenario be confirmed with the Firefox updater or just with package updating? 4. Can the same scenario be confirmed using a Mozilla tar.gz ?
Bug 1553951 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think we are missing a piece of the puzzle here. The upgrade from 66 to 67 works for me as well on Ubuntu 16.04 and ubuntu 18.04, both with canonical and Mozilla builds. I can't really wrap my head what could generate this kind of behavior from the profiles point of view. Maybe Dave could get more info out of poc file. What would probably would be helpful is if trittweiler@gmail could assist a bit more into building up a scenario that we can use reproduce this behavior reliably: 1. Can you clarify if the profile used after update is the same profile than the one before the update. (about:profiles) 2. Confirm that the symlink is the default one. If there's anything custom about the symlink done, it would probably be good to know. 3. Can the same scenario be confirmed with the Firefox updater or just with package updating? 4. Can the same scenario be confirmed using a Mozilla tar.gz ?