I tried to run Proton Mail Bridge, but it couldn't access its secrets. Consequently, I reported [*"No keychain available"* at `github.com/flathub/ch.protonmail.protonmail-bridge/issues`](https://github.com/flathub/ch.protonmail.protonmail-bridge/issues/135#issue-2253012439). However, simultaneously, I happened to experience [*[abrt] kf6-baloo-file: KCrash::defaultCrashHandler(): baloo_file killed by SIGSEGV*](https://bugzilla.redhat.com/show_bug.cgi?id=2276058#c0), and reported that via GNOME ABRT demonstrated to me that GNOME's implementation had failed too. See the attached screenshots for a demonstration of this. Consequently, something underlying had failed. Reproducible: Yes. Steps to Reproduce ------------------ 1. I downloaded an update at approximately 2024-04-19T14+01:00 via KDE Plasma Discover. 2. I applied the update offline during a reboot. 3. I tried to use Proton Bridge and GNOME ABRT. Actual Results -------------- The secrets service didn't appear to exist. Expected Results ---------------- I should have been able to access those applications without issue. Because of [this Reddit comment](https://www.reddit.com/r/kde/comments/d8tjln/comment/f1cmejq/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button#:~:text=There%20used%20to%20be%20Ksecretservice%20%5B1%5D%2C%20but%20I%20think%20it%20never%20made%20the%20cut%20to%20plasma%205%20era%2C%20which%20is%20sad%20because%20several%20other%20programs%20like%20keepassxc%20would%20have%20been%20excellent%20to%20use%20in%20place%20of%20kwallet.%20In%20brief%2C%20there%20is%20no%20longer%20a%20secret%20service%20implementation%20for%20KDE%20that%20I%20am%20aware%20of.), I wasn't certain what component I should report this to.
Created attachment 2027932 [details] GNOME Keyring via Proton Bridge
Created attachment 2027933 [details] Proton Bridge
A reboot fixed it.
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #3) > A reboot fixed it. OS reinitialization didn't permanently remediate it, because it just happened (again): 1. https://github.com/flathub/ch.protonmail.protonmail-bridge/issues/136#issue-2273560688 2. https://github.com/flathub/com.protonvpn.www/issues/229#issue-2273560746 However, a single reinitialization remediated it (presumably) temporarily, again.
Created attachment 2031140 [details] GNOME Keyring via Bitwarden (In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #4) > A single reinitialization remediated it (presumably) temporarily. Now, not even rebooting remediates it. Additionally, I have confirmed that it affects Bitwarden too, meaning that it is not a fault of Proton's. However, notably, NextCloud is never affected (despite also being installed via Flatpak).
It probably got broken by this MR that was intended to implement the secrets portal for Flatpak apps: https://invent.kde.org/frameworks/kwallet/-/merge_requests/67 Please report it[1] and link the ticket here. [1] https://bugs.kde.org
Created attachment 2045217 [details] Proton Bridge RPM (In reply to Daniel Rusek from comment #6) > It probably got broken by this MR that was intended to implement the secrets > portal for Flatpak apps: > > https://invent.kde.org/frameworks/kwallet/-/merge_requests/67 > > Please report it[1] and link the ticket here. > > [1] https://bugs.kde.org It has also broken https://proton.me/download/bridge/protonmail-bridge-3.12.0-1.x86_64.rpm, and this appears to be GNOME's Secret Service, so are you confident that it's due to a KDE MR for Flatpak? Irrespective, thanks - I'll file a ticket at https://bugs.kde.org/enter_bug.cgi?classification=I%20don%27t%20know.
drusek, reported https://bugs.kde.org/show_bug.cgi?id=492541#c0 and updated the title there to match your revision.
> It has also broken > https://proton.me/download/bridge/protonmail-bridge-3.12.0-1.x86_64.rpm, and > this appears to be GNOME's Secret Service, so are you confident that it's > due to a KDE MR for Flatpak? Interesting, thanks! It started happening around the same time the new kwallet (with code from that MR) got released, but it is possible the regression is not caused by that MR. By the way, it is a Freedesktop Secret Service (API), not a GNOME one. The standard is originally from GNOME Keyring developers (in cooperation with KDE Wallet developers), but was accepted into Freedesktop many years ago.
(In reply to `{3rd: "Beedell", 1st: "Roke"}`{.JSON5} from comment #8) > drusek, reported https://bugs.kde.org/show_bug.cgi?id=492541#c0 > and updated the title there to match your revision. Thanks!
(In reply to Daniel Rusek from comment #9) > > It has also broken > > https://proton.me/download/bridge/protonmail-bridge-3.12.0-1.x86_64.rpm, and > > this appears to be GNOME's Secret Service, so are you confident that it's > > due to a KDE MR for Flatpak? > > Interesting, thanks! It started happening around the same time the new > kwallet (with code from that MR) got released, but it is possible the > regression is not caused by that MR. > > By the way, it is a Freedesktop Secret Service (API), not a GNOME one. The > standard is originally from GNOME Keyring developers (in cooperation with > KDE Wallet developers), but was accepted into Freedesktop many years ago. Aha! I think you were right - https://invent.kde.org/frameworks/kwallet/-/merge_requests/67#note_944107 looks like my issue. Worth closing here and transferring to the KDE ticket?
(In reply to `{3rd: "Beedell", 1st: "Roke"}`{.JSON5} from comment #11) > Aha! I think you were right - > https://invent.kde.org/frameworks/kwallet/-/merge_requests/67#note_944107 > looks like my issue. Worth closing here and transferring to the KDE ticket? I am not sure whether it is the same bug. It looks like that one got resolved in KWallet 6.2.1 (https://invent.kde.org/frameworks/kwallet/-/merge_requests/84).
KWallet 6.5.0 is already in Fedora 40. Are you still experiencing the issue when using a fully updated Fedora 40 system?
(In reply to Daniel Rusek from comment #13) > KWallet 6.5.0 is already in Fedora 40. Are you still experiencing the issue > when using a fully updated Fedora 40 system? > ```log > PS /home/RokeJulianLockhart> dnf5 info kf6-kwallet.x86_64 > Updating and loading repositories: > Repositories loaded. > Installed packages > Name : kf6-kwallet > Epoch : 0 > Version : 6.5.0 > Release : 1.fc40 > Architecture : x86_64 > Installed size : 2.1 MiB > Source : kf6-kwallet-6.5.0-1.fc40.src.rpm > From repository : <unknown> > Summary : KDE Frameworks 6 Tier 3 solution for password management > URL : https://invent.kde.org/frameworks/kwallet > License : BSD-3-Clause AND CC0-1.0 AND LGPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-or-later AND LGPL-3.0-or-later > Description : KWallet is a secure and unified container for user passwords. > Vendor : Fedora Project > > PS /home/RokeJulianLockhart> > ``` I've a few updates about ABRT yet to be done, but nothig major, and I'll do them today.
(In reply to Daniel Rusek from comment #12) > (In reply to `{3rd: "Beedell", 1st: "Roke"}`{.JSON5} from comment #11) > > Aha! I think you were right - > > https://invent.kde.org/frameworks/kwallet/-/merge_requests/67#note_944107 > > looks like my issue. Worth closing here and transferring to the KDE ticket? > > I am not sure whether it is the same bug. It looks like that one got > resolved in KWallet 6.2.1 > (https://invent.kde.org/frameworks/kwallet/-/merge_requests/84). Apologies for being hasty. Changed state of https://bugs.kde.org/show_bug.cgi?id=492541#c4.
(In reply to `{3rd: "Beedell", 1st: "Roke"}`{.JSON5} from comment #7) > Created attachment 2045217 [details] > Proton Bridge RPM > > (In reply to Daniel Rusek from comment #6) > > It probably got broken by this MR that was intended to implement the secrets > > portal for Flatpak apps: > > > > https://invent.kde.org/frameworks/kwallet/-/merge_requests/67 > > > > Please report it[1] and link the ticket here. > > > > [1] https://bugs.kde.org > > It has also broken > https://proton.me/download/bridge/protonmail-bridge-3.12.0-1.x86_64.rpm, and > this appears to be GNOME's Secret Service, so are you confident that it's > due to a KDE MR for Flatpak? > > Irrespective, thanks - I'll file a ticket at > https://bugs.kde.org/enter_bug.cgi?classification=I%20don%27t%20know. Apologies - I was wrong about this. I just synchronized the RPM version with the Thunderbird RPM and rebooted to compare, and it does actually retain its secrets. Note that this issue doesn't appear to occur to Bitwarden's Flatpak anymore either, and I can't confirm whether it continues with the GNOME-ABRT RPM (due to not having any crashes unreported in there) but it certainly used to. This means that the issue used to not solely affect Flatpak-packaged applications, but nowadays, it appears to at best affect solely with certain Flatpak applications. Might it be a matter of outdated dependencies within the Flatpak sandbox? This is a little complex for me.
Created attachment 2045326 [details] Screenshot of a Proton Bridge RPM dialog window about orphan process. (In reply to Beedell, Roke Julian Lockhart from comment #16) > (In reply to `{3rd: "Beedell", 1st: "Roke"}`{.JSON5} from comment #7) > > Created attachment 2045217 [details] > > Proton Bridge RPM > > > > (In reply to Daniel Rusek from comment #6) > > > It probably got broken by this MR that was intended to implement the secrets > > > portal for Flatpak apps: > > > > > > https://invent.kde.org/frameworks/kwallet/-/merge_requests/67 > > > > > > Please report it[1] and link the ticket here. > > > > > > [1] https://bugs.kde.org > > > > It has also broken > > https://proton.me/download/bridge/protonmail-bridge-3.12.0-1.x86_64.rpm, and > > this appears to be GNOME's Secret Service, so are you confident that it's > > due to a KDE MR for Flatpak? > > > > Irrespective, thanks - I'll file a ticket at > > https://bugs.kde.org/enter_bug.cgi?classification=I%20don%27t%20know. > > Apologies - I was wrong about this. I just synchronized the RPM version with > the Thunderbird RPM and rebooted to compare, and it does actually retain its > secrets. Note that this issue doesn't appear to occur to Bitwarden's Flatpak > anymore either, and I can't confirm whether it continues with the GNOME-ABRT > RPM (due to not having any crashes unreported in there) but it certainly > used to. This means that the issue used to not solely affect > Flatpak-packaged applications, but nowadays, it appears to at best affect > solely with certain Flatpak applications. > > Might it be a matter of outdated dependencies within the Flatpak sandbox? > This is a little complex for me. GNOME-ABRT still doesn't retain the RedHat BZ key, so it definitely effects outside the sandbox. However, the behaviour of Bridge is really confusing me. I wonder whether it happens to have bugs of its own that, when they interact with this, cause weird failures. I've attached an example.
Is the issue still happening? Some user confirmed that it is now working correctly for them: https://github.com/flathub/com.mojang.Minecraft/issues/116#issuecomment-2351100014 If the problem persists, it could be a good idea to discuss this with the KDE (KWallet) developers or at least in this upstream (KDE) ticket: https://bugs.kde.org/show_bug.cgi?id=492541
(In reply to Daniel Rusek from comment #18) > Is the issue still happening? > > Some user confirmed that it is now working correctly for them: > > https://github.com/flathub/com.mojang.Minecraft/issues/116#issuecomment- > 2351100014 > > > If the problem persists, it could be a good idea to discuss this with the > KDE (KWallet) developers or at least in this upstream (KDE) ticket: > > https://bugs.kde.org/show_bug.cgi?id=492541 drusek, surely you saw https://github.com/flathub/com.mojang.Minecraft/issues/116#issuecomment-2351129116 and haven't forgotten https://bugzilla.redhat.com/show_bug.cgi?id=2276060#c15? I'm a little confused by your recommendations. Apologies.
Two (or more) users have confirmed that it now works correctly for them when using latest Plasma 6.2 (development build) with latest KWallet. Others claimed that it is still broken even on the latest Plasma/KWallet. Downstream tickets (RHBZ or Flathub) will most likely solve nothing. It needs to be properly discussed with upstream and affected users need to provide their experience in the upstream (KDE) ticket.
(In reply to Daniel Rusek from comment #20) > Two (or more) users have confirmed that it now works correctly for them when > using latest Plasma 6.2 (development build) with latest KWallet. Others > claimed that it is still broken even on the latest Plasma/KWallet. > > Downstream tickets (RHBZ or Flathub) will most likely solve nothing. It > needs to be properly discussed with upstream and affected users need to > provide their experience in the upstream (KDE) ticket. It shall be when I'm notified of a response to the KDE ticket. Have I missed something?
It looks like that the issue has been fixed and KWallet now works correctly at least for the Minecraft Flatpak: https://github.com/flathub/com.mojang.Minecraft/issues/116#issuecomment-2520504975 Not sure about the Proton Bridge RPM though. That may be a different problem.
(In reply to Daniel Rusek from comment #22) > It looks like that the issue has been fixed and KWallet now works correctly at least for the Minecraft Flatpak. Not sure about the Proton Bridge RPM though. That may be a different problem. I've reinstalled my OS (Fedora 41 KDE Spin) installation (due to [ https://discussion.fedoraproject.org/t/138821 ][1]) and can confirm that `protonmail-bridge-3.15.0-1.x86_64` continues to lose its credentials every *few* `systemctl reboot`s. [1]: https://discussion.fedoraproject.org/t/installing-fedora-41-kde-spin-removed-windows-boot-loader-from-uefi-gui-and-grub2/138821
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
(In reply to Aoife Moloney from comment #24) This at least momentarily reproduced in F41. I've yet to confirm it in F42.
Doesn't reproduce on F42 in `gnome-abrt-1.4.3-4.fc42.x86_64`, `app/com.protonvpn.www/x86_64/stable --commit=173a1529b74dee36cad710faa5e4f0790c3539001091a234a7cecdc7a0b74d3b` or `warp-terminal-preview-v0.2025.05.28.08.11.preview_06-1.x86_64`, but definitely used to.