Discussion:
[frameworks-kwallet] [Bug 397319] New: Cannot access kwallet after upgrading from Fedora 26 to Fedora 28
Add Reply
b***@kde.org
2018-08-09 15:23:09 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

Bug ID: 397319
Summary: Cannot access kwallet after upgrading from Fedora 26
to Fedora 28
Product: frameworks-kwallet
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
Assignee: ***@kde.org
Reporter: spam-***@2deadmen.com
CC: kdelibs-***@kde.org
Target Milestone: ---

I have posted about this on the StackExchange website :

https://unix.stackexchange.com/questions/461369/cannot-access-kwallet-after-upgrading-fedora-26-28

Here is the contents of that post:

=====================================
When I try to open my wallet there is the standard read error that suggests the
password may be incorrect. This happens both from kwalletmanager5 and using
kwallet-query. The password is correct. My guess is something was changed in
the KDE software with my upgrade to F28 yesterday. My understanding is that the
best approach therefore would be to find a way to open the wallet somehow, say
with an older version of kwalletmanager5, and export it to XML, then import it.

What would be my options for accomplishing this? Or is there a better approach?
=====================================

I have also posted this on the Fedora website:
https://ask.fedoraproject.org/en/question/125129/cannot-access-kwallet-after-upgrading-f26-f28/
(currently awaiting moderation)


I have tried installing KDE on a CentOS 7 machine, and it has the same issue. I
have also tried backups of the kwl and salt files to ensure there is not some
unknown issue with data corruption. I am currently open to any possible means
to recover the kwallet. Please let me know what logs or information, if any, I
can provide to clarify the context of this bug. Sorry, I wasn't sure about the
version numbers involved, except for the fact that the kwalletmanager on Fedora
28 that I am using appears to be version 17.12.3.


Thank you
--
You are receiving this mail because:
You are watching all bug changes.
Rex Dieter
2018-08-09 19:23:20 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

Rex Dieter <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-08-09 21:17:04 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #1 from spam-***@2deadmen.com ---
I have managed to compile what I believe to be kwallet 5.45, substituting
/usr/lib64/libkwalletbackend5 and /usr/bin/kwalletd5 with the versions built
during this process. Unfortunately this didn't work, but I suspect I did
something incorrectly.

When kdesrc-build installed the binaries into kwallet/bin, it installed the
libraries with version 5.49.0 (i.e. it installed "libkwalletbackend5.so.5.49.0,
instead of libkwalletbackend5.so.5.45.0). However I ensured the source at hand
for kwallet was 5.45 by downloading the tar.gz myself, putting it in the
kdesrc-build local source tree, and disabling git updates using kdesrc-build
--build-only. So my suspicion is that this apparently erroneous name for
libkwalletbackend5 is due to the kdesrc-build installer thinking it is indeed
at 5.49.0 for all the build software.
I haven't been able to figure out by any other means what the versions of these
binaries installed are, so if anyone can clarify that would be good.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-08-09 21:58:46 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #2 from spam-***@2deadmen.com ---
I figured out why the built files were 5.49.0 instead of 5.45.0.

Additionally, to test, I replaced not just libkwalletbackend5.so.5 but also
libKF5Wallet.so.5, in addition to /usr/bin/kwalletd5. To clarify, I am doing
this to try to isolate whatever logic in the backend I presume to have changed
in the version which is breaking the wallet opening. Unfortunately, I have just
tried this with 5.45, 5.41, and 5.39, and had no success.
I'm not sure what the other moving parts are in this system, and how else I
might best try to open my wallet with earlier versions of whatever the relevant
encryption logic in kwallet is. So far I have assumed that all the relevant
code must reside in those two libraries and kwalletd5 (and kwallet-query, which
I have been using to try to open it), but this might be wrong.

Maybe it is something simpler, something to do with Blowfish vs GPG? I don't
recall which one my wallet is encrypted with. It might be blowfish.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-08-09 21:59:43 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #3 from spam-***@2deadmen.com ---
I should also add, normally I would assume that somehow my wallet had become
corrupt, but since I am testing this as well with backups of my wallet files, I
don't see any alternative than there is something going on with kwallet.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-08-09 23:06:44 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #4 from spam-***@2deadmen.com ---
I've been taking a look at BlowfishPersistHandler::read. What's the best way to
output data from here or anywhere in the program, to a log file, so I can
examine what's happening ?
--
You are receiving this mail because:
You are watching all bug changes.
Christoph Feck
2018-08-09 23:56:12 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #5 from Christoph Feck <***@kde.org> ---
Fedora 26 was KDE4-based, right? I think to migrate the wallet, you would need
to have both kwalletmanager4 and kwalletmanager5 installed. Then either the
migration might be automatic (I don't know the exact conditions for migration),
or you manually export from kwalletmanager4 to XML and import into
kwalletmanager5.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-08-10 00:17:01 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #6 from spam-***@2deadmen.com ---
Hmm, I don't think so, I've been using kwalletmanager5 and related utilities
for a while now. Come to think of it, I do remember upgrading to KDE5.I guess
this was when I upgraded from 24 to 26, but with 26, I'm almost positive it's
been KDE5.
--
You are receiving this mail because:
You are watching all bug changes.
63257245
2018-08-10 00:48:18 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #7 from 63257245 <spam-***@2deadmen.com> ---
It certainly is strange .. backendpersisthandler.cpp, the file that ends up
returning -9 to indicate the incorrect password, has not changed significantly
for some time, and neither have kwalletbackend.cc, blowfish, cc, etc. I wish I
could think of a way that some how this is PEBKAC and that I am messing up, but
I am testing this using the kwalletpath test binary (passes the path to my
wallet directly, instead of by name), and the password is definitely correct,
since I have been using this wallet daily for years with the same password.
One thing I have noticied is that since the upgrade, my locale is wrong/broken
variously. Many programs warn/alert me that it is broken. I notice that in
kwalletd.cpp, line 682, we convert the password to UTF8. I wonder if somehow
there is some tricky locale magic happening in there? My password is entirely
in [a-zA-Z0-9] though.
--
You are receiving this mail because:
You are watching all bug changes.
63257245
2018-08-10 16:34:53 UTC
Reply
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=397319

--- Comment #8 from 63257245 <spam-***@2deadmen.com> ---
F26 and F24, net-install images, were no luck until I uninstalled kf5-kwallet
on F24 and reverted to the KDE4 version of kwallet (with kwalletd being started
by kwalletmanager via kdeinit4). At that point I was able to open the wallet.
I've been using KDE5 for some time now, so I presume that somehow in my F26
installation of KDE5 the conditions had converged to make it possible to use
half KDE5 kwallet, half KDE4, at least insofar as I had been running kwalletd5
(and to my knowledge, kwalletmanager5), yet working with this wallet which
apparently is a KDE4 wallet, given that I was only able to open it as described
above.
Anyway, having recovered my data, I no longer have a stake in this issue, but I
am at your service to examine the issue further and determine what bugs, if
any, exist, etc.
Thanks
--
You are receiving this mail because:
You are watching all bug changes.
Loading...