Created attachment 631723 [details] output of strace attached to report-gtk process with -f -F -v -s 1000 This is with all F17 updates (from updates and updates-testing) applied as of today, and with a fresh, recently rebooted system. After report-gtk finishes reporting a bug to bugzilla and reports "Status: ASSIGNED https://bugzilla.redhat.com/show_bug.cgi?id=864324", I try to click on the link to view the bug. If firefox is already running when I do that, then I get the "Firefox is already running, but is not responding." pop-up error window. If Firefox is *not* running when I click on the link, then nothing visible happens. When I run strace on report-gtk process, then I observe that in the background, it is calling /usr/bin/gnome-open. For some reason gnome-open is unable to successfully launch firefox. When I run exactly the same gnome-open command from the command line, it works fine. I am unable to figure out how to reproduce the issue or what is causing it. I've attached strace output of the report-gtk process when it's trying to launch firefox. Maybe you can make some sense out of it. I can't figure it out.
Thank you for filling this bug report. It probably happens only when you report a newly detected problem. report-gtk is started from a reported dump directory. A newly reported dump directories are placed at /var/spool/abrt/ by default. After detection a dump directory is readonly for normal users but report-gtk requires write access to a reported problem thus the dump directory is moved from /var/spool/abrt to $XDG_CACHE_HOME/abrt/spool but CWD of report-gtk process remains unchanged and after the move doesn't exist. In this particular case gnome-open is unable to successfully open passed URL.
Fixed in git commit 2e82648d44891f24832d4e3e77b23eeec691b9a7 Author: Jakub Filak <jfilak> Date: Tue Oct 23 11:16:01 2012 +0200 update CWD after stealing of a dump directory - closes rhbz#869032 Signed-off-by: Jakub Filak <jfilak>
abrt-2.0.17-1.fc17,libreport-2.0.17-1.fc17,btparser-0.21-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.17-1.fc17,libreport-2.0.17-1.fc17,btparser-0.21-1.fc17
Package abrt-2.0.17-1.fc17, libreport-2.0.17-1.fc17, btparser-0.21-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.17-1.fc17 libreport-2.0.17-1.fc17 btparser-0.21-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16846/abrt-2.0.17-1.fc17,libreport-2.0.17-1.fc17,btparser-0.21-1.fc17 then log in and leave karma (feedback).
abrt-2.0.18-1.fc17,libreport-2.0.18-1.fc17,btparser-0.22-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.18-1.fc17,libreport-2.0.18-1.fc17,btparser-0.22-1.fc17
Package abrt-2.0.18-1.fc17, libreport-2.0.18-1.fc17, btparser-0.22-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.18-1.fc17 libreport-2.0.18-1.fc17 btparser-0.22-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17495/abrt-2.0.18-1.fc17,libreport-2.0.18-1.fc17,btparser-0.22-1.fc17 then log in and leave karma (feedback).
*** Bug 872811 has been marked as a duplicate of this bug. ***
abrt-2.0.18-1.fc17, libreport-2.0.18-1.fc17, btparser-0.22-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.