Description of problem: periodically icecat suffers from a firefox main() problem: processes are still running beyond application close.This causes the dreaded "firefox is already running, please close it or reboot." message.Looking at top shows no icecat processes, yet killing it reveals no error. Version-Release number of selected component (if applicable): 21 How reproducible: sometimes Steps to Reproduce: 1.open icecat 2. close it 3. try to open it again Actual results: process has zombied itself...MMMMM. Expected results: icecat should close everything and free itself when closed.
That is, you use IceCat but Fedora shows you as it's Firefox already running? Try to use icecat-31.7 on Fedora 21 and see if this problem persists: http://koji.fedoraproject.org/koji/taskinfo?taskID=10337326
icecat-38.3.0-4.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-4d0606c585
icecat-38.3.0-4.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-53f5dda608
icecat-38.3.0-4.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update icecat' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-53f5dda608
icecat-38.3.0-4.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update icecat' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-4d0606c585
icecat-38.3.0-4.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
icecat-38.3.0-4.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.