Created attachment 1825204 [details] screenshot Description of problem: As shown in the attached screenshot,there are 7 user crash and 1 system crash, but I'm unable to report any one. Version-Release number of selected component (if applicable): libreport-2.15.2-6.fc35.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1825205 [details] journal
Created attachment 1825208 [details] one fail screenshot
Created attachment 1825209 [details] another fail screenshot
Proposed as a Blocker for 35-final by Fedora user lnie using the blocker tracking app because: All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test.
I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1980154. Could you please try other component, not webkit? Reporting should work just fine on F35.
Created attachment 1825322 [details] screenshot3
As I said,I could not report any bug successfully,here is the screenshot when I tried to report gnome-shell bug but failed
It looks like there have been some issues with getting the correct debuginfo packages for the crashes submitted to Retrace Server. We have also been recording an unusually high failure rate since late Monday in our monitoring. I'm going to investigate
I join this thread because I am also having similar issues. For some time, I have not been able to retrace any problem using the remote server. The only way to do it is to create a local stack and retrace the error locally. This is not optimal, because it requires a lot of data to be downloaded and installed and takes much longer than with the retrace server and it creates another obstacle for users to report bugs using Abrt.
I tried today with a gnome-shell crash and a will_cpp_segfault crash (retrace job #969440777), both failed with "retrace job failed".
Discussed during the 2021-09-27 blocker review meeting: [0] The decision to delay the classification of this as a blocker bug was made as the current vote is not clear on this one; we will note the F33 decision in the ticket and see if anyone who voted +1 wishes to reconsider, or if any other way to resolve this appears. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-09-27/f35-blocker-review.2021-09-27-16.00.txt
Upgrade today ABRT on my F35kde. ABRT crash on exit, dumped core. packages info: gnome-abrt-1.4.0-2.fc35.x86_64 abrt-debugsource-2.14.6-7.fc35.x86_64 abrt-debuginfo-2.14.6-7.fc35.x86_64 abrt-dbus-debuginfo-2.14.6-7.fc35.x86_64 abrt-libs-2.14.6-8.fc35.x86_64 abrt-dbus-2.14.6-8.fc35.x86_64 python3-abrt-2.14.6-8.fc35.x86_64 abrt-2.14.6-8.fc35.x86_64 abrt-addon-kerneloops-2.14.6-8.fc35.x86_64 abrt-retrace-client-2.14.6-8.fc35.x86_64 abrt-addon-ccpp-2.14.6-8.fc35.x86_64 abrt-addon-pstoreoops-2.14.6-8.fc35.x86_64 abrt-addon-vmcore-2.14.6-8.fc35.x86_64 abrt-addon-xorg-2.14.6-8.fc35.x86_64 abrt-plugin-bodhi-2.14.6-8.fc35.x86_64 python3-abrt-addon-2.14.6-8.fc35.noarch abrt-tui-2.14.6-8.fc35.x86_64 abrt-gui-libs-2.14.6-8.fc35.x86_64 abrt-gui-2.14.6-8.fc35.x86_64 abrt-desktop-2.14.6-8.fc35.x86_64 abrt-cli-2.14.6-8.fc35.x86_64
Created attachment 1827373 [details] Journalctl output from the moment I exit ABRT
perhaps the bug I'm seeing is this other here ( https://bugzilla.redhat.com/show_bug.cgi?id=1997315 ) or?
I can confirm we're seeing significantly higher failure rates in retrace jobs in the past two weeks, that is since we've deployed Fedora 35 support. The culprit may be what appears to be a bug in GDB when attempting to retrace Fedora 35 crashes (see https://github.com/abrt/retrace-server/issues/436). What we're considering right now is switching to debuginfod-backed retracing (see https://github.com/abrt/retrace-server/pull/434). I'll be working to put that into production on Monday at the latest. --- Geraldo, that seems to be the case indeed.
thanks for your attention Matej :)
Vote total of -4 (+3, -7) across https://pagure.io/fedora-qa/blocker-review/issue/475 and the blocker meeting at https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2021-09-27/f35-blocker-review.2021-09-27-16.00.log.txt , so this is rejected as a blocker - note we rejected https://bugzilla.redhat.com/show_bug.cgi?id=1885154 for F33, so we felt bound to follow that decision here. Still, it's a significant issue and it would be very much for the better if it's fixed by release date. If any changes are needed during the freeze I expect this would be granted an FE.
I believe this should be fixed since Friday. Retrace Server should now be able to produce backtraces as usual.