Bug 1873029
| Summary: | bugs can't be reported: "No matching actions found for this event" | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||
| Component: | libreport | Assignee: | abrt <abrt-devel-list> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 33 | CC: | abrt-devel-list, abrt-sig, alciregi, awilliam, bugzilla, ekulik, jakub, jpesco, mcatanza, mgrabovs, michal.toman, mmarusak, msuchy, nielsenb, robatino | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | AcceptedBlocker | ||||||||||||
| Fixed In Version: | libreport-2.14.0-8.fc33 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2020-09-21 20:48:44 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 1766775 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Kamil Páral
2020-08-27 08:11:46 UTC
Created attachment 1712782 [details]
example error message
Created attachment 1712783 [details]
example error message #2
Created attachment 1712784 [details]
example error message #3
Proposing as a BetaBlocker using the same argument as in bug 1860616 comment 8: "Bug hinders execution of required Beta test plans or dramatically reduces test coverage" Which reporting frontend are you using? Sounds like report-gtk and https://github.com/abrt/libreport/commit/85b687098bcedb67285ab787b8bd506d328c34e0. I don't know, you have more of them? :) Whichever one is the preinstalled one in Workstation. Doesn't the screenshot help to answer that? Kamil, were you able to report anything before this update? We've been tracking https://pagure.io/fedora-workstation/issue/156 since the retrace server is down and manual reporting process depends on that. (In reply to Michael Catanzaro from comment #7) > Kamil, were you able to report anything before this update? No, I wasn't, because of bug 1860616. But on my F32, I'm not able to report anything because FAF is down and ABRT doesn't want to proceed without it. I intend to report it against F33 and propose it as a blocker, but I first need to confirm it actually happens on F33. And so far, I've been blocked by bug 1860616 and this bug. Once that is resolved and I can progress further, I'll report another bug regarding FAF, if needed. (In reply to Kamil Páral from comment #8) > No, I wasn't, because of bug 1860616. But on my F32, I'm not able to report > anything because FAF is down and ABRT doesn't want to proceed without it. I > intend to report it against F33 and propose it as a blocker, but I first > need to confirm it actually happens on F33. And so far, I've been blocked by > bug 1860616 and this bug. Once that is resolved and I can progress further, > I'll report another bug regarding FAF, if needed. You might want to also follow https://pagure.io/fedora-workstation/issue/156 and https://pagure.io/fedora-workstation/issue/130. If ABRT can be made functional again in F33 timeframe, that would be great. Otherwise... well, I don't think we want to delay release on it.... We have +4 in the ticket: https://pagure.io/fedora-qa/blocker-review/issue/45 so setting accepted. I do care about the "update hasn't gone stable" point, but it seems reasonable to accept this as a blocker to try and ensure we don't push an update stable with this bug in it. Created attachment 1714606 [details]
screenshot
I'm not seeing this; instead I see the processing failed message.
I cropped that image tightly, but I am not given an option to process the stack trace locally. Chris: was that with a newly-generated crash? Apparently you still can't report crashes for which the directory was created before the ztsd-supporting update even after you update. You have to cause a new crash after updating and try reporting that. It was a new crash. Decided to file a new bug since my case looks different from this one; bug 1878317. I see this with 20200912.n.0 compose with FEDORA-2020-59e144acee applied. Steps to reproduce: 1) Install Workstation Live 20200912.n.0 2) `$ bodhi updates download --updateid=FEDORA-2020-59e144acee` 3) `$ sudo dnf install ./*` 3) Reboot 4) `$ will_abort` 5) Step through steps to submit report, observe "No matching actions" error in gnome-abrt. This seems to be fixed with this update: https://bodhi.fedoraproject.org/updates/FEDORA-2020-444a3363f0 meaning: abrt-2.14.4-5.fc33.x86_64 gnome-abrt-1.3.6-5.fc33.x86_64 libreport-2.14.0-8.fc33.x86_64 However, that update still causes bug 1878317, so it's not clear whether it'll get pushed stable. FEDORA-2020-444a3363f0 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-444a3363f0 FEDORA-2020-444a3363f0 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-444a3363f0 FEDORA-2020-444a3363f0 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-444a3363f0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-444a3363f0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-444a3363f0 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |