Hide Forgot
Description of problem: if bugs are reported when abrt-applet isn't running when it runs it alerts about them instead of ignoring. Version-Release number of selected component (if applicable): abrt-gui-2.0.19-2.fc18.i686 Steps to Reproduce: 1. report a bug with abrt-gui when abrt-applet isn't running. 2. login to a session that auto-starts abrt-applet. 3. Actual results: abrt-applet notifies of the crash. Expected results: abrt-applet should ignore the already reported bugs. Additional info:
Actually the issue must be something else. Because I had a crash earlier today, 'reported' it to a log file (bug went to the reported bugs list) and now that I logged back in (not just a log back in but after a fresh boot) I got a notification again. I didn't click neither 'Ignore' nor 'Report' in the notification bubble.
(In reply to comment #1) > Actually the issue must be something else. Because I had a crash earlier > today, 'reported' it to a log file (bug went to the reported bugs list) and > now that I logged back in (not just a log back in but after a fresh boot) I > got a notification again. > I didn't click neither 'Ignore' nor 'Report' in the notification bubble. Thank you for your comment. That's another bug. If you have time, please file a new bugzilla ticket for this.
fixed in git commit c590e3959bebac69619a11fc6742c926b51105cf Author: Jakub Filak <jfilak@redhat.com> Date: Fri Dec 7 10:13:46 2012 +0100 abrt-applet: alerts only not reported problems
(In reply to comment #2) > (In reply to comment #1) > > Actually the issue must be something else. Because I had a crash earlier > > today, 'reported' it to a log file (bug went to the reported bugs list) and > > now that I logged back in (not just a log back in but after a fresh boot) I > > got a notification again. > > I didn't click neither 'Ignore' nor 'Report' in the notification bubble. > > Thank you for your comment. That's another bug. If you have time, please > file a new bugzilla ticket for this. I didn't because I wasn't able to reproduce it.
Hi Jakub, it happened today. I had reported a crash to a log file and in a next boot abrt-applet alerted again. Do you want me to open another bug report or is it fixed already (sorry if I misunderstood)?
(In reply to comment #5) > Hi Jakub, it happened today. I had reported a crash to a log file and in a > next boot abrt-applet alerted again. > Do you want me to open another bug report or is it fixed already (sorry if I > misunderstood)? Hi Sergio, Yes, please open a new ticket for that. abrt-applet doesn't update its list of already notified problems if you leave the notification bubble to disappear without any user action.
abrt-2.0.20-1.fc18,btparser-0.24-1.fc18,libreport-2.0.20-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/abrt-2.0.20-1.fc18,btparser-0.24-1.fc18,libreport-2.0.20-1.fc18
abrt-2.0.20-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/abrt-2.0.20-1.fc17
Package abrt-2.0.20-1.fc18, btparser-0.24-1.fc18, libreport-2.0.20-1.fc18: * should fix your issue, * was pushed to the Fedora 18 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.20-1.fc18 btparser-0.24-1.fc18 libreport-2.0.20-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20725/abrt-2.0.20-1.fc18,btparser-0.24-1.fc18,libreport-2.0.20-1.fc18 then log in and leave karma (feedback).
abrt-2.0.20-1.fc18, btparser-0.24-1.fc18, libreport-2.0.20-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
abrt-2.0.20-1.fc17, btparser-0.24-1.fc17, libreport-2.0.20-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.