I've got /usr/bin/firefox set up as my protocol handler for http and https. I.e. the config editor has that value for the network.protocol-handler.app.http{,s} settings. When firefox is already running, another instance executed by thunderbird will operate in remote more, i.e. tell the running instance to open the document while the new process will terminate almost immediately. Things are different if firefox is not running yet. In that case, the firefox process keeps running to display the browser windows. Its parent PID is that of thunderbird-bin (the binary, not the gentoo package of that name). When thunderbird is closed, all its windows are closed, but the process keeps running while the browser is open. Reproducible: Always Steps to Reproduce: 1. Configure firefox as the browser for thunderbird, see above 2. Close firefox 3. Click on a link in an email 4. Close thunderbird 5. for pid in $(pgrep thunderbird-bin); do pstree -p $pid; done 6. Start thunderbird again Actual Results: 3. opens firefox window 4. closes all windows 5. lists a thunderbird-bin process owning the firefox process 6. thunderbird complains that there is already another instance running, which should be terminated first Expected Results: 5. thunderbird should terminate, probably making init the parent of firefox 6. thunderbird should start up without hassle, as there is no TB window open
Which versions of firefox and thunderbird? Are you using the source packages or the -bin ones? Please upgrade to the latest of both, attach your emerge --info, and then reopen this bug. Thanks!
Created attachment 300083 [details] emerge --info for firefox
Created attachment 300085 [details] emerge --info for thunderbird
(In reply to comment #1) > Which versions of firefox and thunderbird? 9.0 each. > Are you using the source packages or the -bin ones? Source. > Please upgrade to the latest of both, attach your emerge --info, > and then reopen this bug. Thanks! Done.
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team