I think it's fair to say that the "lightbulb" notification is not working well enough. It's good for people who notice this sort of thing, but it's not something that's immediately obvious, and it doesn't scream for attention if it's initially ignored.
IMHO there are two options for making this experience more user friendly: 1) Running firefox instances notice that they have been upgraded (either by monitoring their chrome directory, or being fed some signal. The former seems more robust in a multi-user world) and display very stern warnings to the user that they really really should click a button which causes firefox to restart itself as it would have if it had been upgraded via its own internal mechanism. Obviously the chrome for this would need to be made resistant somehow, so it wasn't wiped out when the upgrade happens. This is either an upstream issue, or something we would have to do. Do they ever have to care about this instance in Windows? If firefox can be deployed as a system-wide app rather than per-user, they must do. 2) Firefox updates should only be applied while restarting the computer (obviously the infrastructure for doing this does not yet exist, but I think I've seen some talk about doing more updates in this way, when they are fundamentally incompatible with being performed while people are logged in). This would require no effort from upstream, but would require a pretty large change in the way Ubuntu updates work. -- MASTER Misbehaves in all sorts of ways when upgraded while running https://bugs.launchpad.net/bugs/36739 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
