** Changed in: firefox (Ubuntu)
Sourcepackagename: mozilla-firefox => firefox
Status: New => Confirmed
--
firefox should kill non-responding instance and start up
https://bugs.launchpad.net/bugs/185020
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
For the record: this dialog only happens to me when using alternative
window managers or xfce; metacity, when application doesn't responde to
close request, offers to kill the it and does actually kill firefox "to
death" - starting another instace directly after works.
--
firefox should kill non-
I have been frustrated by this bug for a long time. I don't remember
ever seeing it on windows for some reason. It sounds like either of the
suggestions above are workable.
I'm surprised this is only set to importance 'wishlist' it's a serious
issue which stops users from starting ff. If we accept
I also agree it's a usability issue that Firefox sometimes tells the
user there's a hanging firefox but doesn't offer a workaround for it.
As a note, MIT's variant of Firefox deployed on the clusters will offer
on that dialog to kill the offending Firefox process and/or remove stale
locks. It'd be
