grAndrew wrote: > apt did suggest restarting firefox for the changes to apply BUT it did > not mention that not doing so will render FF unusable nor it did have a > "restart firefox" button -- it is rather easy to close fox window but > not quit firefox - will lead to problems. > > Again, my suggestion is to _force_ users to restart programs if updates > affect the total usability of the package. > > What exactly caused the bug: > > - have a firefox update ready to install (the last one) > - do the update while firefox is running > - firefox3 and ff2 is unusable until you kill and restart ff3 (you may or may > not be able to normally "File->Quit" due to blocking "ASSERT" message) > > Forcing anyone to do anything is never a good idea we leave it up to suggestion and if you dont follow it its not really firefox's fault. Its more of a comment than a suggestion. it tells you in a bubble in upper right gnome panel as well as in terminal wither from update manager or from apt-get.
Did restarting firefox help with the issue? -- Sincerely Yours, John Vivirito https://launchpad.net/~gnomefreak https://wiki.ubuntu.com/JohnVivirito Linux User# 414246 -- ASSERT: *** Search: Search: _installLocation: engine has no file! Stack Trace: 0:ENSURE_WARN(false,_installLocation: engine has no file!,2147500037) 1:() 2:() 3:() 4:epsGetAttr([object Object],hidden) https://bugs.launchpad.net/bugs/252008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs