Description of problem:
When reporting a bug in ABRT, you need to provide a Bugzilla API key. However, in that dialog, there's a red warning text:
> Secret Service is not available, your settings won't be saved!
And exactly as declared, if you provide your API key, close ABRT and reopen it again, the field is again empty. I assume this might affect more than the API key, but it's extremely problematic specifically for the API key, because it can't be retrieved again from Bugzilla (you can only generate a new one). So each time you want to report a bug in KDE through ABRT, you need to go to Bugzilla and generate a *new* API key. I'm not sure if there's a limit on how many you can have. Or you need to have the key written down somewhere else.
This is a regression in F37. In F36, ABRT doesn't contain this warning and saving the API key works as expected.
When gnome-abrt is started in terminal, I see this error printed when showing the password dialog:
> Can't call method 'OpenSession' over DBus on path '/org/freedesktop/secrets' interface 'org.freedesktop.Secret.Service': GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Algorithm plain is not supported. (only dh-ietf1024-sha256-aes128-cbc-pkcs7 is supported)
The Secret Service seems to be operational in general, because if I launch KDE Wallet, I can connect to the keyring just fine. And I can even use Seahorse (a GNOME-based password manager) to create new password entries, and they correctly show up in KDE Wallet. So the Secret Service itself doesn't seem to be broken, only ABRT can't connect to it. That might be ABRT's fault or some library's fault (libsecret? libreport?).
Version-Release number of selected component (if applicable):
= F37 (broken) =
= F36 (working) =
Steps to Reproduce:
1. start ABRT (Problem Reporting)
2. go to Preferences -> Report to Fedora (any) -> Configure -> Bugzilla
3. see a red warning message at the bottom of the dialog
4. provide some value in "API key" field, confirm and close everything
5. close and reopen ABRT
6. go back to the "API key" field, it's empty
Created attachment 1923294 [details]
screenshot of the secret service error in abrt
Created attachment 1923295 [details]
Nominating as a F37 Final blocker due to:
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:
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:
A Common Bug description:
(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
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
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
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
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:
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.
I can confirm that this bug is now fixed with kf5-kwallet-5.100.0-1.fc37 .