Bug 343789

Summary:	Migration from KDE4 kwallet fails
Product:	[Frameworks and Libraries] frameworks-kwallet	Reporter:	Antony Lee <anntzer.lee>
Component:	general	Assignee:	Valentin Rusu <valir>
Status:	REPORTED ---
Severity:	normal	CC:	cfeck, j.straight-kde, kdelibs-bugs, rdieter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description Antony Lee 2015-02-04 20:40:51 UTC

Migration from KDE4 kwallet fails with the error "Cannot read old wallet list. Aborting." and no extra information, leaving the user with no way to access e.g. kdewallet.

Reproducible: Always

Steps to Reproduce:
1. Delete $HOME/.config/kwalletrc, if present
2. Restart KDE
3. Try e.g. to connect to a WPA network, or something else that'll request access to kdewallet.
4. Choose to migrate the preexisting KDE4 wallet.

Actual Results:  
Migration fails with error "Cannot read old wallet list. Aborting."

Expected Results:  
Migration takes place.

Comment 1 Antony Lee 2015-02-05 19:28:12 UTC

Hum, my apologies.  It seems that the migration somehow took place (?), but the error message is still puzzling.

Comment 2 Christoph Feck 2015-02-05 20:39:04 UTC

Okey, changing severity again. If not all old data is accessible, it would be a critical bug, because kwallet may contain keys that you need to unlock other data.

Comment 3 Antony Lee 2015-02-05 21:30:02 UTC

Yup, I understand, no worries.

Comment 4 Valentin Rusu 2015-02-06 00:15:31 UTC

Are you using distribution packages or you compiled KDE with KF5 from the sources?

Comment 5 Antony Lee 2015-02-06 00:49:56 UTC

I am using the Arch Linux packages.

Comment 6 Valentin Rusu 2015-03-17 22:02:24 UTC

Are you people having the old kde4 wallet on your systems? The migration wallet needs the old walletd to be present and running in order to read the old wallet.

Comment 7 Justin Zobel 2021-03-09 05:54:10 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 8 Antony Lee 2021-03-09 10:09:29 UTC

(I personally have no idea whether this is still relevant, so feel free to close.)