On Sun, Nov 15, 2009 at 11:16 PM, Dariusz J. Garbowski <thuforuk@xxxxxxxxxxx> wrote: > On 15/11/09 12:24 PM, Adam Pribyl wrote: >> >> I also have troubles with this. The worst thing is that firefox often >> after such update dies, without saving the tabs etc. as it does when it is >> killed. And because it dies after update anyway, I would just suggest to put >> a "killall firefox" in PREIN script. Because this will trigger the firefox >> saving mechanism and would not cause a data loss. > > Particularly a good idea for times when the user is working with a session > on his bank account / fulfilling payments / on his retirement fund account, > etc. > For the record, I see that you argue that Firefox will die or perhaps do > something stupid during/after update. Nevertheless, deliberate killing may > or may not be worse but puts the blame on Fedora... Neither situation is a > happy one but I'm not sure if this is better. It's not a "perhaps do something stupid": As far as I can tell reliably dies every time during the update and the session saving function fails to do its job. Everything the user was working on in Firefox is lost. When firefox is killed it saves the current session state. Even form entry information is saved. I think it's unlikely that j-random-user is going draw much of a distinction between an explicit kill and the current failure. Even if: a desire to avoid blame is not a good reason to do the worse thing. Of course, not crashing would be far better... but with all the on the fly dl-opening Firefox does, I don't know how reasonable that is… -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
