Created attachment 713834 [details] bug demonstration video Description of problem: I just booted F19 Alpha TC1. I see abrt telling me to report a bug. I choose to auto-report everything in the future. When I open ABRT GUI, the problem is marked as not reported. I expect the problem to be reported, because I've confirmed all previous questions. I've seen this problem several times now, in various situations. This is the first time I managed to report it. Version-Release number of selected component (if applicable): abrt-2.1.2-1.fc19.x86_64 abrt-addon-ccpp-2.1.2-1.fc19.x86_64 abrt-addon-kerneloops-2.1.2-1.fc19.x86_64 abrt-addon-python-2.1.2-1.fc19.x86_64 abrt-addon-vmcore-2.1.2-1.fc19.x86_64 abrt-addon-xorg-2.1.2-1.fc19.x86_64 abrt-dbus-2.1.2-1.fc19.x86_64 abrt-desktop-2.1.2-1.fc19.x86_64 abrt-gui-2.1.2-1.fc19.x86_64 abrt-libs-2.1.2-1.fc19.x86_64 abrt-plugin-bodhi-2.1.2-1.fc19.x86_64 abrt-retrace-client-2.1.2-1.fc19.x86_64 How reproducible: easily in my VM with Alpha TC1, I see the kernel problem quite often Steps to Reproduce: 1. hit Report problem 2. say Yes for auto-reporting 3. open ABRT GUI and select the problem, it says Reported: No.
Created attachment 713835 [details] journalctl output
See bug 924271 for a followup problem. It might be related, or not.
(In reply to comment #2) > See bug 924271 for a followup problem. It might be related, or not. Thank you for all your effort. The second bug helped me to figure out what happend. The root cause is in the super simple reporting mode which is known as Shortened Reporting and which is enabled by default in GNOME. The auto-report runs the 'report_uReport' event which failed in your case. You can see the failure in the second video attached to the second bug. If the ShortenenedReporting mode is enabled and if the reporting is started from the notification bubble, ABRT doesn't show any error messages. So, it looks like that the problem has been reported but it wasn't. The ShortenedReporting mode is a result of an attempt to make bug reporting less frustrating for common users. The Shortened Reporting can be enabled or disabled by adding either 'ShortenedReporting = "yes"' or 'ShortenedReporting = "no"' line to $HOME/.config/abrt/settings/abrt-applet.conf
I see. So this is not really a bug, it's just a consequence of libreport (or whatever) crashing. You might want to improve the situation a bit, but overall, this can be closed, no? The obvious idea is to show another bubble popup "Shortened reporting failed, please report manually [Report]" if shortened reporting fails. But I'm not sure it's the best idea, it adds another type of popups, another complexity. A very small improvement that occurred to me is that you could display "Reported: Failed" instead of "Reported: No" in the bug details window. That would make absolutely clear that ABRT tried to report it, but it didn't work, instead of creating confusion as it was in my case. It could also display text "Please report manually" or similar. That could be easy to implement. What do you think?
(In reply to comment #4) Definitely, it needs some improvement. The obvious idea you proposed above doesn't fit into the reporting simplification effort but I will implement the small improvements. So, I'm not closing this ticket yet.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.