Comment 4 for bug 299393

Added link to upstream bug.

Bug #338785 is a dupe of this. I'd mark it as such, but apparently I don't have adequate privileges to do that, given that several other bugs are marked as duplicates of 338785.

To summarize the upstream ticket, the problem is a side effect of the version upgrade process. Restarting FF will work around the problem. I'd infer from that, that the problem lies in the packaging, and not with the upstream project.

One of the duplicate tickets here contains a developer comment stating that this isn't an easy problem to resolve.

Although the current upgrade process does include a user notification that a FF restart is required, maybe a stop-gap solution would be to make that notification more forceful and intrusive, prompting the user to restart FF immediately before continuing to use it.