Bug 2141237
| Summary: | ABRT on KDE can't store any passwords: Secret Service is not available | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||
| Component: | kf5-kwallet | Assignee: | KDE SIG <kde-sig> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 37 | CC: | abrt-devel-list, abrt-sig, bcotton, droidbittin, geraldo.simiao.kutz, jakub, jgrulich, jmilan, jonha87, kde-sig, me, mgrabovs, michal.toman, msrb, rdieter, robatino, than | ||||||||
| Target Milestone: | --- | Keywords: | CommonBugs | ||||||||
| Target Release: | --- | Flags: | bcotton:
fedora_prioritized_bug+
|
||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | https://ask.fedoraproject.org/t/common-issues/28363 RejectedBlocker | ||||||||||
| Fixed In Version: | kf5-kwallet-5.100.0-1.fc37 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2022-11-17 01:27:53 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Kamil Páral
2022-11-09 09:00:37 UTC
Created attachment 1923294 [details]
screenshot of the secret service error in abrt
Created attachment 1923295 [details]
rpm -qa
Nominating as a F37 Final blocker due to: https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria#Default_application_functionality When reporting a bug, remembering the authentication credentials for a bug tracker sounds like a basic functionality of a bug reporting tool. Especially when those credentials can't be entered easily (username+password), but it's a very long string of random characters, which can't even be retrieved again, but needs to be generated anew each time. This sounds related: https://bugs.kde.org/show_bug.cgi?id=458341 Thanks a lot, Jonathan. From what I understand from that thread, we could either disable the new Secret Service API from KWallet (which would make it fallback to whatever service backend has been used before) or we could cherrypick that patch from the last comment to enable "plain" support in KWallet. The former is probably safer. Can reproduce this bug on a F36 KDE too: abrt-*-2.15.1-1.fc36 gnome-abrt-1.4.2-1.fc36.x86_64 libreport-2.17.4-1.fc36.x86_64 libsecret-0.20.5-1.fc36.x86_64 gnome-keyring-42.1-1.fc36.x86_64 kf5-kwallet-5.99.0-1.fc36.x86_64 pam-kwallet-5.26.2-1.fc36.x86_64 kf5-plasma-5.99.0-1.fc36.x86_64 We're both right. This bug didn't affect F36 on release, but it was introduced with some update. I'll try to figure out which exact change caused this. This is the change that broke ABRT in F36: working: kf5-kwallet-5.91.0-1.fc36.x86_64 kf5-kwallet-libs-5.91.0-1.fc36.x86_64 broken: kf5-kwallet-5.99.0-1.fc36.x86_64 kf5-kwallet-libs-5.99.0-1.fc36.x86_64 A Common Bug description: https://ask.fedoraproject.org/t/common-issues/28363 (In reply to Jonathan Haas from comment #4) > This sounds related: https://bugs.kde.org/show_bug.cgi?id=458341 Indeed, thanks for the link, Jonathan. This was a huge timesaver ;) In today's Go/No-Go meeting, we agreed to reject this as a blocker on the basis that the majority does not consider this to violate basic functionality and those who do would be willing to waive it, so in the interests of time, we are taking this as a consensus to reject https://meetbot.fedoraproject.org/fedora-meeting/2022-11-10/f37-final-go_no_go-meeting.2022-11-10-17.02.log.html#l-78 While it was rejected as a blocker, proposing as a prioritized bug because I think it's really important that our users can easily report program crashes. +1 Prio Bug +1 FE Updated F36 now with frameworks from kde-SIG copr (https://copr.fedorainfracloud.org/coprs/g/kdesig/kde/). Confirmed, no more bug with the new 5.100 kf5-kwallet-5.100.0-1.fc36.x86_64 kf5-kwallet-libs-5.100.0-1.fc36.x86_64 In today's Prioritized Bugs meeting, we agreed to accept this as this presents a major roadblock to bug reporting on KDE Plasma based variants https://meetbot.fedoraproject.org/fedora-meeting-1/2022-11-16/fedora_prioritized_bugs_and_issues.2022-11-16-15.05.log.html#l-63 It appears that update FEDORA-2022-a57b72eeb5 contains a fix for this, so I'm setting this to ON_QA. FEDORA-2022-a57b72eeb5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a57b72eeb5 FEDORA-2022-a57b72eeb5 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. (In reply to Kamil Páral from comment #9) > This is the change that broke ABRT in F36: > > working: > kf5-kwallet-5.91.0-1.fc36.x86_64 > kf5-kwallet-libs-5.91.0-1.fc36.x86_64 > > broken: > kf5-kwallet-5.99.0-1.fc36.x86_64 > kf5-kwallet-libs-5.99.0-1.fc36.x86_64 The upstream report says pretty clearly that kf5-kwallet 5.97 is the release that introduced the Secret Service implementation, causing this regression. 5.100 fixes it by adding "plain" protocol support, so 5.97, 5.98, and 5.99 are the broken versions (and 5.99 is the one that was backported to F36). So kf5-kwallet-5.100 should be pushed to F36 updates ASAP. Created attachment 1925158 [details]
screenshot of working ABRT on F37 with kwallet 5.99.0-1
Just a weird detail here: yesterday Ben Williams (jbwillia) made a batch of F37 respins, just in case, and the KDE spin was build with kf5-kwallet-5.99.0-1... and the bug seems fixed too.
I know this is no longer an issue as for today the new version is at the stable repos, so I add this print just for the records.
(In reply to Geraldo Simião from comment #21) > Just a weird detail here: yesterday Ben Williams (jbwillia) made a batch of > F37 respins, just in case, and the KDE spin was build with > kf5-kwallet-5.99.0-1... and the bug seems fixed too. I don't think it's fixed on that respin. It just doesn't show up in Live environments, not sure why. It has to be tested when installed. (In reply to Fedora Update System from comment #18) > FEDORA-2022-a57b72eeb5 has been submitted as an update to Fedora 37. > https://bodhi.fedoraproject.org/updates/FEDORA-2022-a57b72eeb5 I can confirm that this bug is now fixed with kf5-kwallet-5.100.0-1.fc37 . |