With Firefox 4 (natty), Firefox now handles much better the deletion of
all its files out from under it, so this is much less of an issue. This
can probably be closed now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree that this is not a duplicate of #270303.
** This bug is no longer a duplicate of bug 270303
MASTER - firefox (intrepid/jaunty): your browser has been updated and needs
to be restarted
--
Have firefox ask user to exit firefox *BEFORE* updating.
https://bugs.launchpad.net/bugs/274468
There is an older bug report about some problems that show up because
firefox is updated while it is running: Bug 252548
--
Have firefox ask user to exit firefox *BEFORE* updating.
https://bugs.launchpad.net/bugs/274468
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: firefox (Ubuntu)
Importance: Undecided = Wishlist
--
Have firefox ask user to exit firefox *BEFORE* updating.
https://bugs.launchpad.net/bugs/274468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I see one problem with this feature.
What if you are in the middle of something when you start updating
(multitasking)
This is one reason why we prompt you after to restart.
** Package changed: firefox (Ubuntu) = firefox-3.0 (Ubuntu)
** Changed in: firefox-3.0 (Ubuntu)
Status: New =
In response to John Vivirito's comment #9 - obviously the prompt to close
*BEFORE* executing the update would have minimal impact on multitasking.
Imagine you have 9 updates, and firefox is, say, 7th of 9.
The prompt would only trigger on launch of the 7th update, the firefox one, in
a similar
I wonder what makes Firefox so special as for updating. I have not had
similar problems with other software. Anyway, I guess Ubuntuzilla could
be a workaround and would let you get updates sooner after their
release.
--
Have firefox ask user to exit firefox *BEFORE* updating.
With regards to comment #11 - the idea of halting an application while updating
it is not unusual for daemons.
Databases, whatever.
In this case the concept is the same. There are a number of resources
on the file system referenced by the application and the profile and the
profile data stores
*** This bug is a duplicate of bug 270303 ***
https://bugs.launchpad.net/bugs/270303
After reviewing bug #270303 I argue this close as duplicate was invalid.
bug #270303 was more about notification message issues, not about the
more general issue of people ending up with corrupt profiles
*** This bug is a duplicate of bug 270303 ***
https://bugs.launchpad.net/bugs/270303
** This bug has been marked a duplicate of bug 270303
MASTER - firefox (intrepid): your browser has been updated and needs to be
restarted
--
Have firefox ask user to exit firefox *BEFORE* updating.
Those two bug report are likely linked to this update/localstore.rdf
issue:
https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/270303
https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/289365
--
Have firefox ask user to exit firefox *BEFORE* updating.
First off, this has been happening for a very very long time in mozilla,
it seems unlikely the injection of ubuntu help will resolve things any
time soon (although I could be wrong - certainly sqllite has taken over
in other portions of the mozilla profile).
Secondly, I don't see this as just a
I'd like to emphasise that this issue is not typical, but there often
seem to be a few after each update.
Also, there are some people who managed to miss the informational
notice, then get panicky when their browser starts causing weird errors.
This would also avoid that behaviour.
--
Have
Elaboration, it'd be nice if perhaps it opened up one of those handy dialogs on
install, asking the person to exit firefox, and telling them that firefox would
be shut down for all users (there might be others on the machine) after they
hit Next.
They hit Next, a kill is issued, the install
I was talking with Derek on IRC about this, where I agreed, and I've had
a change of heart regarding this issue after reading this:
http://kb.mozillazine.org/Corrupt_localstore.rdf
It seems like that an update is not the only way localstore can get
corrupted, and it looks like the ff people
15 matches
Mail list logo