Since latest Kubuntu 15.04 Vivid updates, KWallet asks for password for applications. After entering password correctly, I get error with code -9 as shown in Snapshot1.png. I get the same error, if I open kwalletmanager, click open then enter the password. This happens lots of times in login sessions. This is a critical bug, because it causes you to lose access to important data, like Google Chrome & Opera passwords, when you need it, and email passwords (I won't be able to refresh email in KMail). Reproducible: Sometimes Actual Results: I get error with code -9. Expected Results: The application accesses KWallet. Kubuntu Vivid is a beta version. Kubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/kwalletmanager/+bug/1434426.
Created attachment 91679 [details] Snapshot1.png
Steps to produce: 1. Install Kubuntu 15.04 64 bit. 2. Update all packages.
Please confirm: you did a fresh install but you reused the existing .kwl files from your previous KDE4 installation?
I formatted and created new partitions. I removed everything. I don't know if this is useful. While I was using Kubuntu Live USB, I was asked to create a wallet and migrate my old wallet, even though I didn't have any previous wallets.
And you got the "error -9" you show on the screen capture from a new kwallet installation? Or perhaps you copied the old .kwl file from your backup on the new system?
I don't have any backup and I get the error, after entering the password correctly.
I am seeing the same. This is what I did: 1. A recent install of 14.04. 2. A dist-upgrade to vivid. 3. Create a new user. 4. I *think* I was asked to migrate my passwords at one point, but I am not 100% sure. 5. I *was* asked to provide new passwords for the wallet. Is it possible that kmail is looking for a KDE4 wallet whereas I have a KDE5 one?
(In reply to Shaheed Haque from comment #7) > Is it possible that kmail is looking for a KDE4 wallet whereas I have a KDE5 one? Well, it might be. However, I'm not using kubuntu myself so I cannot confirm that.
I worked around the issue as follows: 1. Rename this file out of the way: $ mv ./.kde/share/apps/kwallet/kdewallet.kwl ./.kde/share/apps/kwallet/kdewallet.kwl.old 2. Start kmail. You will be prompted for passwords, supply them. 3. There should now be a new file in the above location: $ ls ./.kde/share/apps/kwallet/kdewallet.kwl ./.kde/share/apps/kwallet/kdewallet.kwl
The workaround I reported in comment 9 is not perfect; each time kmail does new mail checking, I seem to get prompted for the password, but at least it functions well enough to get/read email.
I've got the same error sometimes. What fixed it here was 'killall -9 kwalletd', and then retrying with kwalletmanager.
Note: This bug doesn't happen always, so sometimes Kmail & Google Chrome access the wallet without being asked to enter password.
Yesterday, the bug occured. I was asked to enter the password for email. It gave me error, even though I entered it correctly, but after closing the window, I could check email normally. This happened in Kubuntu 15.04 stable version. Make it confirmed. It affects many people.
I have the same problem, and it is driving me nuts! However, there is a twist to it. after i get the error message, I enter the OLD password and the error goes away. I did upgrade non-conventional way. I made a new installation on a new computer; then i copied the contents of the home dir to the new computer; then I logged in to my new plasma5 session. I think I was led through the kwallet migration process, and I have entered a NEW password. But when I get the error (usually - after a resume), I have to enter the OLD password from the old kwallet for the error to go away. I think one indicator of the problem is a process kwalletd5 running besides kwalletd kwalletmanager and kwalletd (zombie), but I am not yet sure of this. Now, I have tried to do away with the problem a few times. I exported all my passwords to an xml file; I have logged out of plasma session and moved away all the kwallet configuration and storage files (~/.kde/share/config/kwallet* and ~/.kde/share/apps/kwallet/), logged in to plasma, set up kwallet, imported the contents of the old kwallet from the xml file. But it seems the problem still occurs sometimes!
(In reply to Shaheed Haque from comment #10) > The workaround I reported in comment 9 is not perfect; each time kmail does > new mail checking, I seem to get prompted for the password, but at least it > functions well enough to get/read email. This might be a configuration of kwallet issue: launch kwalletmanager and see if the kwallet is set up to continue to be open if the applications are not using it.
Do you want any data? This bug is critical and annoying.
Could you also check please if you by chance have dublicate kwallets in ~/.local/share/kwallet* (or something similar in ~/.local/share/)? I was surprised to find dublicates (perhaps those with the old password) there. After I removed those files, the problem was gone.
In ~/.local/share/kwalletd there were 3 files: .directory, kdewallet.kwl and kdewallet.salt.
Ok, so note the access/modification times of those files and compare with the same parameters of the files in ~/.kde/share/apps/kwallet* ; then move those files away; then see if the problem is solved perhaps.
May you explain how to do this in detail?
You can run these commands on the command line: stat ~/.local/share/kwalletd/* ## list files in .local subfolder with detailed stats; save output somewhere stat ~/.kde/share/apps/kwallet/* ## list files in .kde subfolder with detailed stats; save output somewhere ## this way you can see which of the files are actually accessed by the kwallet mv ~/.local/share/kwalletd ~/ ## this command will move the folder to your home dir Then see if kwallet still gives you trouble. If so, paste the output of the above stat commands in this thread, maybe we will see something while looking at it...
You can also run the stats command two times; one time - right after you have entered the kwallet password and it WORKED; second time - right after you entered the kwallet password and it DID NOT WORK. I guess that way you can see which wallet access was attempted in each case.
After I failed to access Chrome passwords and Kontact, I ran the 2 commands. Output of stat ~/.local/share/kwalletd/*: File: ‘/home/sherif/.local/share/kwalletd/kdewallet.kwl’ Size: 148 Blocks: 8 IO Block: 4096 regular file Device: 802h/2050d Inode: 17848942 Links: 1 Access: (0600/-rw-------) Uid: ( 1000/ sherif) Gid: ( 1000/ sherif) Access: 2015-05-18 18:43:09.577220364 +0200 Modify: 2015-05-14 03:56:10.666062531 +0200 Change: 2015-05-14 03:56:10.710063256 +0200 Birth: - File: ‘/home/sherif/.local/share/kwalletd/kdewallet.salt’ Size: 56 Blocks: 8 IO Block: 4096 regular file Device: 802h/2050d Inode: 17848920 Links: 1 Access: (0600/-rw-------) Uid: ( 1000/ sherif) Gid: ( 1000/ sherif) Access: 2015-05-18 18:43:09.405153055 +0200 Modify: 2015-05-14 03:56:01.757915735 +0200 Change: 2015-05-14 03:56:01.757915735 +0200 Birth: - Output of stat ~/.kde/share/apps/kwallet/*: File: ‘/home/sherif/.kde/share/apps/kwallet/kdewallet.kwl’ Size: 2208 Blocks: 8 IO Block: 4096 regular file Device: 802h/2050d Inode: 17830486 Links: 1 Access: (0600/-rw-------) Uid: ( 1000/ sherif) Gid: ( 1000/ sherif) Access: 2015-05-21 22:51:42.413404752 +0200 Modify: 2015-05-21 22:51:04.851491542 +0200 Change: 2015-05-21 22:51:04.851491542 +0200 Birth: - File: ‘/home/sherif/.kde/share/apps/kwallet/kdewallet.salt’ Size: 56 Blocks: 8 IO Block: 4096 regular file Device: 802h/2050d Inode: 17825803 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ sherif) Gid: ( 1000/ sherif) Access: 2015-05-21 22:50:35.648634990 +0200 Modify: 2015-05-08 15:43:00.780726152 +0200 Change: 2015-05-08 15:43:00.780726152 +0200 Birth: -
I can confirm the same error (Kubuntu 15.04) Chronological happenings: After a clean, fresh install of the system, when first trying to connect to WiFi, a kwallet window appeared, asking whether to import KDE4-kwallets or 2 other options, which I can't remember. I wondered, why they ask for Import from KDE4 after a fresh install. Until now no issues, but I didn't try KMail, etc. yet. Now I tried to import my old kwallet.kwl file from my old KDE4/Kubuntu 14.10 Installation and that's, where exactly that error happened. The password is not working any more. Maybe that information helps to figure out, if it concerns only KDE4-wallets.
Further testing: Upgrade to Plasma 5.3 did not change anything. Funnily even just closing the wallet in kwalletmanager and reopening afterwards leads to the same error. It seemed at that moment, that password input is only successful when opening is requested by an application. After that I just copied the old KDE4 kdewallet.kwl file to the directory of the KDE5 kdewallet.kwl, while KDE was down. After KDE-Login, KNetworkManager requested to open the KWallet, which seemed to work orderly, as WLAN was connected. BUT Opening KWalletManager showed a closed wallet. And more suspicious, this time it could be opened. (And my old passwords where there, as it was the KDE4 wallet originally). Repeating to reopen the wallet worked fine. What didn't work, was to import the KDE5-Wallet, same error. I don't see any systematic behaviour, why this error occurs. Just to participate this information in case it might be helpful.
I reinstalled Kubuntu 15.04. After first restart then running Kontact, it asked me to enter password, even though I didn't make any password (I wasn't asked to make a password for KDE wallet).
In Vivid Kwallet is automatically created when you create a user, with the same password as your account. This is done to automatically enable Single Sign On, so you do not have to enter password twice upon login. However, later you may have to enter kwallet password if you do not use apps that need kwallet for a while, and it gets closed. See kwallet settings in system settings to tune this behaviour. It may also be that, if you use encrypted home dir, the single sign on does not work and you may be asked for kwallet password immediately upon login. Before doing reinstall, did you try moving kwallet in .local away?
Thanks Donates Glodenis. I have strange behavior: Before being asked to migrate KWallet and enter a new password, I was being asked to enter password (Root password worked). After migrating KWallet and entering a new password, I still need root password. How did you know about it?
Kubuntu 15.04, fresh install on formatted drive. Same error every time for instance when my wifi is trying to connect.
Seems related to: https://bugs.kde.org/show_bug.cgi?id=173094 The status of that was "resolved invalid" and the root cause seemed to be a different version of kmail and kwallet. The version of my kmail is 4.14.6 (using kde developement platformd 4.14.6) the version of the rest of the applications differ but all report being based on kdeframeworks 5.9.0 ps aux shows two instances of the kwallet daemon: kwalletd and kwalletd5 I understand that this "bug" would me rather an issue of the packagers of Ubuntu than a KDE issue.
I'm not sure. I was asked to enter password for K*something* 5. I think root password didn't work and KWallet password worked.
I'm not sure. I was asked to enter password for K*something* 5. I think root password didn't work and KWallet password worked. Usually, root password works.
I am also having this issue. Fresh install of Kubuntu 15.04. I didn't copy any old wallets or installed any old packages that I know of. I simply updated all my packages and started using KDE. Whenever I do anything (e.g. Kmail, Chrome, plug-in my external drive) I enter the collect password and it gives me the same error. Help? Also, why is there a kdewallet.kwl both in ~/.kde/share/apps/kwallet and in ~/.local/share/kwalletd?
Strange, I also have kwallet files in both places, although I remember deleting those from ~/.local (if I remember correctly, after that the error you are talking about never appeared again). Now I have: $ ls -l ~/.local/share/kwalletd ~/.kde/share/apps/kwallet/ ~/.kde/share/apps/kwallet/: viso 120 -rw------- 1 dg dg 98344 Bir 29 15:04 kdewallet.kwl -rw-r--r-- 1 dg dg 56 Bal 25 21:25 kdewallet.salt ~/.local/share/kwalletd: viso 28 -rw------- 1 dg dg 4524 Bir 29 14:31 kdewallet.kwl -rw------- 1 dg dg 56 Geg 6 07:34 kdewallet.salt By the way, sometimes I do get asked for a password twice in a row; since in that case it is different programs asking for it, and since I do not get any error messages, that is a different problem from the one being discussed here. So I suggest try moving files from ~/.local/kwalletd and see what happens, maybe the problem will go away (you should do that while you are not in your Plasma session).
i moved the wallets and the salts to .bak files, rebooted, and then used the same password for the wallet as for my login. Everything is now working. I can't say which particular step made things work, but I am not having issues at the moment...
Hi, I'm also seeing this on a kubuntu 15.10 install, first login ok, then every logout/login will ask for the kde5 and kde wallet migration manager password. Only when rebooting and login again it will not ask for my password. Then I upgraded to latest plasma 5.5 from the backports ppa, and now I get asked for those two passwords every time I log in. On journalctl I see this error message: kwallet5(sddm:session): pam_kwallet5: open_session called without kwallet5_key
I just fixed it by creating another user with the same password as me, and the copying the following files from the test user to mine (and setting ownership of those files to my user): .config/kwalletrc .local/share/kwalletd/kdewallet.* There wasn't anything on .kde/share/apps/kwallet/ on the new user but there were the same two wallet files as in .local/share/kwalletd on my user so I delete them, logged in with my user and I wasn't asked for any of the wallet passwords as before.
Had same problem with 16.04 beta 2 and found this page. For some reason I fixed it by changing my user password, logging out and back in. After logging back in with my new user password once again Kwallet came up. I entered the new user password, again it gave me error code -9. I tried my original user password and it worked. I logged out and in again a few times and still the old user password worked for Kwallet, no more code -9. I then went into the settings and changed the Kwallet password to something new. I logged out and back in and typed the new Kwallet password and again it worked fine. I haven't encountered the code -9 since. I hope that helps a few of you. -Bugs Bunny
I kept getting error -9: read error - possibly incorrect password. The auto migration tool couldn't migrate my old kwallet into the new plasma kwallet. After a few hours and running into this bug report thread I finally got it working. It seems that the old kwallet 4 was running along the new kwallet5 kwalletd (4.14.20) kwalletd5 What solved it for me in the end was killing everything with kwalletd in it and restarting kwallet manager so that the migration agent could fix one wallet at a time. This will hopefully help somebody stuck at importing their old kwallet file.
Since latest kubuntu LTS update, there is now no longer any way to get the wallet open, even downloading the old package and running that still gives the -9 error code.
SUMMARY My previous hdd was displaying block errors, so I replaced it with an SSD hdd, and a fresh install of Fedora 29 with updates. Installed KDE, unaware it is an "enhanced" version, including a new kwalletmanager, of which I was also unaware it is an "enhanced" version. Now, kwm cannot open my old wallet. It produces "Error 9, possibly wrong password." BULLSHIT! kwm has been buggered. The password given is correct. STEPS TO REPRODUCE 1. Load an older wallet, kwallet3 or kwallet4, I don't remember which it was started under, but it shouldn't bloody matter!! Wallets should be retro, something which seems lost on the "developers." 2. Try to open it using the same pw under which it was encrypted. 3. OBSERVED RESULT "Error 09, possibly wrong password." EXPECTED RESULT open the bloody wallet! Give access to the passwords and other data stored there, so the users who put their faith in your product are not stranded for want of their passwords through no fault of their own. SOFTWARE/OS VERSIONS Linux Fedora 29 & updates KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION The traditional icons do not show. There's just a "cheap" looking little "window" which appears and very little works on it. "Import wallet" does not work, nothing happens.
I am using KDE Neon User edition 5.19 (based on Ubuntu 18.04) and, after updating the packages about an hour ago and restarting, KDE Wallet keeps asking me for a password when trying to connect to the Wi-Fi, as described in this bug. Previously it was working fine. The password I am entering is correct, but it does not seem to do any good. Versions: kwalletmanager 4:20.04.2-0xneon+18.04+bionic+build37 libkf5wallet-bin 5.71.0-0xneon+18.04+bionic+build47 libkf5wallet-data 5.71.0-0xneon+18.04+bionic+build47 libkf5wallet5:amd64 5.71.0-0xneon+18.04+bionic+build47 libkwalletbackend5-5:amd64 5.71.0-0xneon+18.04+bionic+build47 libpam-kwallet-common 4:5.19.0-0xneon+18.04+bionic+build51 libpam-kwallet5 4:5.19.0-0xneon+18.04+bionic+build51
Created attachment 129400 [details] kdewallet error -9 when trying to connect to Wi-Fi This is the screenshot for my previous commennt
Created attachment 129401 [details] attachment-28756-0.html I was never told what the solution was to this bug, or even if there was any. Probably because I pissed them off too much giving them shit for the problem in the first place; I've since moved on but I still have antipathy towards this "team" for creating the fuck-up in the first place, never testing it before releasing it and causing me to lose ~100 or more passwords because of it. I'll never trust this bunch again, not that they seem to give a shit. On Tue, Jun 16, 2020 at 3:25 AM Jaume Sabater <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=345412 > > --- Comment #43 from Jaume Sabater <jsabater@gmail.com> --- > Created attachment 129400 [details] > --> https://bugs.kde.org/attachment.cgi?id=129400&action=edit > kdewallet error -9 when trying to connect to Wi-Fi > > This is the screenshot for my previous commennt > > -- > You are receiving this mail because: > You are on the CC list for the bug.
After going again through all the comments, I just wanted to point out that the content of the directory `~/.kde/share/apps/kwallet/` includes the two expected files (kdewallet.kwl and kdewallet.salt) but the directory `~/.kde/share/apps/kwallet/` does not exist. I understand that this is correct these days.
Relevant log lines in /var/log/syslog, in case it helps debug the issue: ``` Jun 16 10:36:54 ranma kded5[3469]: plasma-nm: Unhandled active connection state change: 1 Jun 16 10:36:54 ranma kded5[3469]: plasma-nm: virtual NMVariantMapMap SecretAgent::GetSecrets(const NMVariantMapMap&, const QDBusObjectPath&, const QString&, const QStringList&, uint) Jun 16 10:36:54 ranma kded5[3469]: plasma-nm: Path: "/org/freedesktop/NetworkManager/Settings/31" Jun 16 10:36:54 ranma kded5[3469]: plasma-nm: Setting name: "802-11-wireless-security" Jun 16 10:36:54 ranma kded5[3469]: plasma-nm: Hints: () Jun 16 10:36:54 ranma kded5[3469]: plasma-nm: Flags: 13 Jun 16 10:36:54 ranma dbus-daemon[3386]: [session uid=1000 pid=3386] Activating service name='org.kde.kwalletd5' requested by ':1.11' (uid=1000 pid=3469 comm="/usr/bin/kded5 " label="unconfined") Jun 16 10:36:54 ranma dbus-daemon[3386]: [session uid=1000 pid=3386] Successfully activated service 'org.kde.kwalletd5' Jun 16 10:36:54 ranma kded5[3469]: plasma-nm: bool SecretAgent::processGetSecrets(SecretsRequest&) const Waiting for the wallet to open Jun 16 10:36:55 ranma kwalletd5[9736]: Application ' "kded5" ' using kwallet without parent window! Jun 16 10:36:55 ranma NetworkManager[1225]: <info> [1592296615.3762] audit: op="statistics" arg="refresh-rate-ms" pid=3544 uid=1000 result="success" Jun 16 10:37:00 ranma plasmashell[3544]: plasma-nm: Wireless scan on "wlp2s0" failed: "Scanning not allowed while unavailable or activating" Jun 16 10:37:00 ranma kwalletd5[9736]: kf5.kwallet.kwalletd: Failed to open wallet "kdewallet" "Read error - possibly incorrect password." Jun 16 10:37:00 ranma kwalletd5[9736]: Application ' "kded5" ' using kwallet without parent window! Jun 16 10:37:03 ranma kwalletd5[9736]: kf5.kwallet.kwalletd: Failed to open wallet "kdewallet" "Read error - possibly incorrect password." Jun 16 10:37:03 ranma kwalletd5[9736]: Application ' "kded5" ' using kwallet without parent window! Jun 16 10:37:10 ranma plasmashell[3544]: plasma-nm: Wireless scan on "wlp2s0" failed: "Scanning not allowed while unavailable or activating" ``` It was the NetworkManager that activated the need to use the wallet as I was attempting to connect to my home Wi-Fi.
After upgrading some packages on KDE Neon 5.19, I also encountered this bug. In addition to Jaume Sabater (https://bugs.kde.org/show_bug.cgi?id=345412#c42), I'd like to point out an -at least temporary- solution by downgrading the corresponding packages to their previous versions: sudo apt install kwalletmanager=4:20.04.1-0xneon+18.04+bionic+build34 libkwalletbackend5-5=5.70.0-0xneon+18.04+bionic+build42 libkf5wallet5=5.70.0-0xneon+18.04+bionic+build42 libkf5wallet-data=5.70.0-0xneon+18.04+bionic+build42 libkf5wallet-bin=5.70.0-0xneon+18.04+bionic+build42 libpam-kwallet5=4:5.18.5-0xneon+18.04+bionic+build50 libpam-kwallet-common=4:5.18.5-0xneon+18.04+bionic+build50 Afterwards just reboot and you should be good to go - without losing any stored secrets.
I just wanted to let you know that I realised a new version (build 48) just poped in the repository and that, after installing, the problem persists: kwalletmanager 4:20.04.2-0xneon+18.04+bionic+build37 libkf5wallet-bin 5.71.0-0xneon+18.04+bionic+build48 libkf5wallet-data 5.71.0-0xneon+18.04+bionic+build48 libkf5wallet5:amd64 5.71.0-0xneon+18.04+bionic+build48 libkwalletbackend5-5:amd64 5.71.0-0xneon+18.04+bionic+build48 libpam-kwallet-common 4:5.19.0-0xneon+18.04+bionic+build51 libpam-kwallet5 4:5.19.0-0xneon+18.04+bionic+build51
(In reply to Karsten Diem from comment #47) > After upgrading some packages on KDE Neon 5.19, I also encountered this bug. > > In addition to Jaume Sabater > (https://bugs.kde.org/show_bug.cgi?id=345412#c42), > I'd like to point out an -at least temporary- solution by downgrading the > corresponding packages to their previous versions: > > sudo apt install kwalletmanager=4:20.04.1-0xneon+18.04+bionic+build34 > libkwalletbackend5-5=5.70.0-0xneon+18.04+bionic+build42 > libkf5wallet5=5.70.0-0xneon+18.04+bionic+build42 > libkf5wallet-data=5.70.0-0xneon+18.04+bionic+build42 > libkf5wallet-bin=5.70.0-0xneon+18.04+bionic+build42 > libpam-kwallet5=4:5.18.5-0xneon+18.04+bionic+build50 > libpam-kwallet-common=4:5.18.5-0xneon+18.04+bionic+build50 > > > Afterwards just reboot and you should be good to go - without losing any > stored secrets. I can confirm that this version downgrade works, but no need to restart the system as a `killall -9 kwalletd5` will do the trick :-)
After a mild heart attack I can also confirm that the downgrade works, hopefully the issue is minor and can be resolved quickly (my install is vanilla KDE Neon, so it's not like I have heaps of old wallets, old configs or random PPAs that could be affecting things). I take extreme issue with trennor and comment #44. That is a very self-centred and aggressive attitude to be taking, it doesn't help anyone. The code is open and if it is critical to you, you have the option to fix it, pay someone to fix it on your behalf or pay for support. Let's all be excellent to one another.
To (temporarily) prevent upgrading those headache-/heart-attack- triggering packages, you might want to pin their versions until the problem has been solved. create /etc/apt/preferences.d/fix_broken_kwallet.pref with Package: kwalletmanager Pin: version 4:20.04.1-0xneon+18.04+bionic+build34 Pin-Priority: 1000 Package: libkwalletbackend5-5 Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libkf5wallet5 Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libkf5wallet-data Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libkf5wallet-bin Pin: version 5.70.0-0xneon+18.04+bionic+build42 Pin-Priority: 1000 Package: libpam-kwallet5 Pin: version 4:5.18.5-0xneon+18.04+bionic+build50 Pin-Priority: 1000 Package: libpam-kwallet-common Pin: version 4:5.18.5-0xneon+18.04+bionic+build50 Pin-Priority: 1000
Created attachment 129409 [details] attachment-3924-0.html I'm glad you don't like my approach because far too often we're expected to simly ACCEPT programmers' fuckups without any retribution or knowing how much programmers' screwups have affected other people. If they don't like it they should bloody well be more careful before releasing shit without testing on the platforms on which they are used. Now those bastards know how someone feels when they DESERT a user upon whom he depended TO GET IT RIGHT THE FIRST TIME!!! I was abandoned with over 100 passwords I could not access, and I was understandably upset and goddamned well let them know it. If they don't like it, too bad; quit fucking up and abandoning your people. THAT'S my message, and if you don't like the way I deliver it, too bad. That's just the way it is. If you don't want me sounding off, take my addy from this list; I don't especially wanna hear about this anymore. It brings back too many bad memories. Sayanora On Tue, Jun 16, 2020 at 5:31 AM Twisted Lucidity <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=345412 > > Twisted Lucidity <lucidlytwisted@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |lucidlytwisted@gmail.com > > --- Comment #50 from Twisted Lucidity <lucidlytwisted@gmail.com> --- > After a mild heart attack I can also confirm that the downgrade works, > hopefully the issue is minor and can be resolved quickly (my install is > vanilla > KDE Neon, so it's not like I have heaps of old wallets, old configs or > random > PPAs that could be affecting things). > > I take extreme issue with trennor and comment #44. That is a very > self-centred > and aggressive attitude to be taking, it doesn't help anyone. The code is > open > and if it is critical to you, you have the option to fix it, pay someone > to fix > it on your behalf or pay for support. > Let's all be excellent to one another. > > -- > You are receiving this mail because: > You are on the CC list for the bug.
(In reply to Jaume Sabater from comment #48) > I just wanted to let you know that I realised a new version (build 48) just > poped in the repository and that, after installing, the problem persists: > > kwalletmanager > 4:20.04.2-0xneon+18.04+bionic+build37 > libkf5wallet-bin > 5.71.0-0xneon+18.04+bionic+build48 > libkf5wallet-data > 5.71.0-0xneon+18.04+bionic+build48 > libkf5wallet5:amd64 > 5.71.0-0xneon+18.04+bionic+build48 > libkwalletbackend5-5:amd64 > 5.71.0-0xneon+18.04+bionic+build48 > libpam-kwallet-common > 4:5.19.0-0xneon+18.04+bionic+build51 > libpam-kwallet5 > 4:5.19.0-0xneon+18.04+bionic+build51 Thanks a lot for the downgrade procedure. After downgrading you could export you wallet(s) in XML, then remove the files : - ~/.config/kwalletmanager5rc - ~/.config/kwalletrc - move the folder ~/.local/share/kdewalletd to ~/.local/share/kdewalletd.backup - update the packages again - close an open session. Open the kdewalletmanager and import previously saved XML in the new wallet.
(In reply to Bruno Patri from comment #53) > (In reply to Jaume Sabater from comment #48) > > I just wanted to let you know that I realised a new version (build 48) just > > poped in the repository and that, after installing, the problem persists: > > > > kwalletmanager > > 4:20.04.2-0xneon+18.04+bionic+build37 > > libkf5wallet-bin > > 5.71.0-0xneon+18.04+bionic+build48 > > libkf5wallet-data > > 5.71.0-0xneon+18.04+bionic+build48 > > libkf5wallet5:amd64 > > 5.71.0-0xneon+18.04+bionic+build48 > > libkwalletbackend5-5:amd64 > > 5.71.0-0xneon+18.04+bionic+build48 > > libpam-kwallet-common > > 4:5.19.0-0xneon+18.04+bionic+build51 > > libpam-kwallet5 > > 4:5.19.0-0xneon+18.04+bionic+build51 > > Thanks a lot for the downgrade procedure. > > After downgrading you could export you wallet(s) in XML, then remove the > files : > - ~/.config/kwalletmanager5rc > - ~/.config/kwalletrc > - move the folder ~/.local/share/kdewalletd to > ~/.local/share/kdewalletd.backup > - update the packages again > - close an open session. > > Open the kdewalletmanager and import previously saved XML in the new wallet. I haven't tried this. I will later, though. Just to clarify, though, are you saying the issue is due to the new version opening files from a previous version (hence your advice on manually migrating the contents of the wallet)?
(In reply to Bruno Patri from comment #53) > After downgrading you could export you wallet(s) in XML, then remove the > files : > - ~/.config/kwalletmanager5rc > - ~/.config/kwalletrc > - move the folder ~/.local/share/kdewalletd to > ~/.local/share/kdewalletd.backup > - update the packages again > - close an open session. > > Open the kdewalletmanager and import previously saved XML in the new wallet. Thank you for the workaround! I've recovered my passwords :-)
The problem seems to be fixed in neon repository. If you created "fix_broken_kwallet.pref" from (https://bugs.kde.org/show_bug.cgi?id=345412#c51), just remove it and check for / apply updates. I recently received libkf5wallet-bin - 5.71.0-0xneon+18.04+bionic+build49 libkf5wallet-data - 5.71.0-0xneon+18.04+bionic+build49 libkf5wallet5 - 5.71.0-0xneon+18.04+bionic+build49 libkwalletbackend5-5 - 5.71.0-0xneon+18.04+bionic+build49 kwalletmanager - 4:20.04.2-0xneon+18.04+bionic+build37 libpam-kwallet5 - 4:5.19.1-0xneon+18.04+bionic+build52 libpam-kwallet-common - 4:5.19.1-0xneon+18.04+bionic+build52 on my KDE Neon 5.19 machine and wallet can be opened just like before.
(In reply to Karsten Diem from comment #56) > The problem seems to be fixed in neon repository. > > I recently received > > libkf5wallet-bin - 5.71.0-0xneon+18.04+bionic+build49 > libkf5wallet-data - 5.71.0-0xneon+18.04+bionic+build49 > libkf5wallet5 - 5.71.0-0xneon+18.04+bionic+build49 > libkwalletbackend5-5 - 5.71.0-0xneon+18.04+bionic+build49 > kwalletmanager - 4:20.04.2-0xneon+18.04+bionic+build37 > libpam-kwallet5 - 4:5.19.1-0xneon+18.04+bionic+build52 > libpam-kwallet-common - 4:5.19.1-0xneon+18.04+bionic+build52 > > on my KDE Neon 5.19 machine and wallet can be opened just like before. I can confirm that this version fixed the problem. Thank you very much for your help.
I second that confirmation, awesome job folks.
Seems that the issue was identified as an upgrade issue and a fix and a workaround were provided - though it was not approved by the original poster who has not been active since 2015.
Created attachment 154990 [details] attachment-22655-0.html no matter, i gave up on kwallet years ago; given that i received NO support because everybody was pissed off I gave them shit for how the whole thing transpired. programmers need to take into account that not every user is a geek; and provide at changes like this detailed warnings and how-tos which the average user (such as me) can understand and follow. Better yet, DON'T ORPHAN just because something's been changed. This caused me no end of trouble, and the lack of help from that bunch just made things worse. Sometimes programmers need a kick in the ass to remind them that not everybody is a geek!! This was one of those times. Better luck next time; I've sworn off KDE partly because of this. But your info is way too late to be of any use to me now. Bye for now. On Tue, Jan 3, 2023 at 6:41 AM Oded Arbel <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=345412 > > Oded Arbel <oded@geek.co.il> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |oded@geek.co.il > Status|REPORTED |RESOLVED > Resolution|--- |WORKSFORME > > --- Comment #59 from Oded Arbel <oded@geek.co.il> --- > Seems that the issue was identified as an upgrade issue and a fix and a > workaround were provided - though it was not approved by the original > poster > who has not been active since 2015. > > -- > You are receiving this mail because: > You are on the CC list for the bug.