https://bugs.kde.org/show_bug.cgi?id=410999
Bug ID: 410999
Summary: Regression: kwalletd5 breaks wallet access for
applications like Chromium
Product: frameworks-kwallet
Version: 5.61.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: general
Assignee: va...@kde.org
Reporter: kdeb...@customcdrom.de
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
(I think this problem is related to Bug #400462 "kwalletd legacy dbus service
file". I'm not entirely sure if it's actually a KDE bug or a packaging bug in
KDE Neon.)
STEPS TO REPRODUCE
1. Upgrade to KDE Wallet from Frameworks 5.61.0.
2. Perform "qdbus org.kde.kwalletd"
OBSERVED RESULT
qdbus will complain that the service could not be found (unfortunately I was
stupid enough not to make a copy of the acutal error message before downgrading
KDE Wallet again, sorry. :-( )
EXPECTED RESULT
As in KWallet from Frameworks 5.60.x:
$ qdbus org.kde.kwalletd
/
/MainApplication
/modules
/modules/kwalletd
/modules/kwalletd5
/org
/org/kde
/org/kde/kwalletd5
SOFTWARE/OS VERSIONS
KDE Neon
KDE Plasma: 5.16.4
KDE Frameworks 5.61.0
Qt 5.12.3 (kompiliert gegen 5.12.3)
Das xcb Fenstersystem
KDE Applications: 19.08.0
ADDITIONAL INFORMATION
Yesterday's KDE Frameworks update broke Chromium's Wallet integration, access
to all stored passwords was immediately lost.
Apparently, Chromium tries to contact Wallet using the dbus service name
org.kde.kwalletd which worked flawless up to and including KDE Frameworks 5.60.
In Frameworks 5.61 Bug #400462 was implemented which states a question about a
malformed service file in Frameworks up to version 5.60, but which also
explicitly states that the service file should just be fixed such that the
"org.kde.kwalletd" service name is provided properly.
(Please read the original request in #400462.)
Unfortunately, at least in the KDE Neon packaging of Frameworks 5.61, the
service file providing org.kde.kwalletd is removed entirely, breaking existing
applications without any prior notice!
I tried to recreate / restore the org.kde.kwalletd.service file, but to no
avail - the dbus service was available again afterwards, but seemed to look
differently than in Frameworks 5.60 and Chromium still wasn't able to access
its stored passwords.
So I manually pinned the KDE Wallet packages to version 5.60.0 in APT
preferences and downgraded just KDE Wallet. Afterwards, Chromium worked fine
again after a logout and re-login.
If this was an intended breakage to remove old compatibility cruft, there
should have been a *really* *big* *warning* in the KF 5.61 release notes! Your
users may lose access to important credentials simply by upgrading, and
depending on their tech saviness, they may lose it permanently!
A backup of your home directory will not help in this case, you'd need to
restore your whole system from a backup if you don't know how to downgrade KF
or at least KDE Wallet manually. (And before I did I even wasn't sure if it
would work at all.)
If this was not an intended breakage, the problem should be fixed really soon
from my point of view.
If it's a packaging issue in KDE Neon, it should quickly be fixed there, before
too many users get bitten badly... :-/
--
You are receiving this mail because:
You are watching all bug changes.
