Exit. The other, much better possibilities to fix that usecase problem
Feature changed by: Stefan Behlert (sbehlert) Feature #308658, revision 17 Title: Restart button in Firefox - openSUSE-11.3: Rejected by (a_jaeger) + openSUSE-11.3: Rejected by Andreas Jaeger (a_jaeger) reject date: 2010-10-06 16:05:52 reject reason: not done Priority Requester: Mandatory openSUSE-11.4: Evaluation by product manager Priority Requester: Mandatory + Info Provider: (Novell) Requested by: Thorsten Kukuk (kukuk) Product Manager: (Novell) Product Manager: (Novell) Project Manager: (Novell) + Engineering Manager: (Novell) + Developer: (Novell) Partner organization: openSUSE.org Description: We release a lot of MozillaFirefox updates. Every update has the risk, that parts of an already running firefox don't work anymore. Especially popup-windows are very often empty afterwards. Because of the broken popup windows, it is not always possible to close firefox and start it again without loosing the current sessions. If you configure themes and/or plugins, MozillaFirefox offers sometimes a "restart" button. We shoud provide this functionality in the standard menu, too, so that customers can restart firefox without loosing data. Discussion: #1: Wolfgang Rosenauer (wrosenauer) (2010-01-08 07:25:33) What do you mean by "standard menu"? Are there other possibilities to fix that usecase probably? IIRC Ubuntu is using some kind of notifier if an update happens to Firefox to allow the user to restart or close prior to the update. I'd need to look into their implementation but anyhow they are probably relying on some package manager feature anyway here. #3: Thorsten Kukuk (kukuk) (2010-01-11 15:31:10) (reply to #1) With standard menu, I mean something like File->Restart like File- probably is to make sure that all Firefox components always stay compatible. Else I don't know if there are other solutions, but I'm open for suggestions. #5: Sławomir Lach (lachu) (2010-09-15 13:02:37) I suggest simply add lock files onto programs and package managers. It will be global lock files signalizing program are already running (for example in /tmp). Packages should contains path to this global lock files. Problems: - We must modify a lot of programs, like Firefox, to create global lock files - We must check how it works on multiuser environment(one user can turn off Firefox, but others not) - We must disallow program to run on update time #7: Thorsten Kukuk (kukuk) (2010-10-08 11:49:02) (reply to #5) lock files are a bad idea and will not really help. Only think about any web based management tool (like WebYaST), where you need a running firefox to start the update. -- openSUSE Feature: https://features.opensuse.org/308658