While the data is in the wallet, applications don't seem to be accessing it(?). I can view the passwords and corresponding uuid's in the wallet after upgrading (kubuntu 15.04), but any time I try to mount an encrypted volume, or connect to one of 244 saved WiFi or VPN networks it prompts for password with blank entry. Reproducible: Always
(In reply to Jason Straight from comment #0) > While the data is in the wallet, applications don't seem to be accessing > it(?). > > I can view the passwords and corresponding uuid's in the wallet after > upgrading (kubuntu 15.04), but any time I try to mount an encrypted volume, > or connect to one of 244 saved WiFi or VPN networks it prompts for password > with blank entry. > > Reproducible: Always What applications? Are you using the "frameworks" version of these applications? For example konqueror is still kde4 based and it uses the old wallet.
Device notifier and Network Manager applet in plasma 5, as well as mounting via dolphin.
If I get it right, the migration wizard correctly migrated the data but your applications are not able to retrieve that data? What happens if you put the password for one item? Does the existing entry get updated or the application woud create another entry. Could you check that for me please?
I see your comment on bug #343789 regarding migration. The first time, the migration failed so I booted back into 4.10 (btrfs snapshot), and exported my wallet to XML, booted back to 5.04 and imported it. On that bug you mention that it needs the old walletd in order to import the wallet. It appears that the old walletd is not available in the ubuntu repositories and could be why migration is failing on ubuntu systems. In my case, having imported exported and imported my wallet, but the imported passwords still not being used: Under SolidLuks it has updated my existing uuid entry with the same password it had, and has not created another entry. Network Management has updated the existing entry with the corresponding UUID from /etc/NetworkManager/system-connections VPN also acts the same. I verified that the VPN connection contained the data in wallet beforehand. I tried to log in, but it prompted me for the password. I opened the connection with the network manager plasma-widget and the password field was blank. I entered the password and told it to store it. Logged in and was not prompted for the password. The data has no visible difference in kwallet. I paied attention to the key name and value.
That should be 14.10 and 15.04 kubuntu versions. Apparently my 1 finger is not working right.
I see kwalletd and kwalletd5 are provided by the kde-runtime package in ubuntu 15.04. That may or may not have been the case when I initially upgraded a couple weeks ago and my migration failed.
So, you exported/imported the wallet or you let the migration wizard do the upgrade?
I exported/imported. I just checked my xml files and the entries for the wifi connection I changed are exactly the same from an export I did before setting the pass to an export I did just now.
Well, looking the xml file will not help, as the applications get the password from the wallet file (.kwl) and not from the xml file. So, I sugest this test : - manually enter a password on a VPN or WiFi or whatever you like when the application prompts you - save that password - close the session and verify if the password prompt dissapeared on next login. If the password prompt dissapeared, then please check the entry in kwalletmanager5. Does it look the same as the one created by the import. For this test's purpose you could create a secondary wallet, using the imported data. Can you do this test and post your findings here, please?
Yeah, I've done that. It saves the existing uuid entry, and all data looks the same.
(In reply to Jason Straight from comment #10) > Yeah, I've done that. It saves the existing uuid entry, and all data looks > the same. And you're sure applications are trying to access the right wallet? You can check that in the system settings.
I don't see where in system settings, but according to settings in kwallet manager I only have one wallet.
I have no idea what the problem would be on your system. Not being a Kubuntu user myself, I'm not sure how to help you. If you're able to open the wallet and inspect it using KWallet Manager, then KWallet is functioning normally.
Thanks for taking the time to look into it. I don't know what to make of it either, not knowing how the queries for matches are performed, or what other data may be in the wallet that I don't see (other than UUID, keys, and values). Strange that network manager and encrypted volumes would have the issue, but smb:// kio seems to have worked.
I'm not using ubuntu myself but Jonathan does. @Jonathan: any clue about this user's issue? Seems to me problems might be located somehow in some applications such as the network manager applet.
I don't know I'm afraid. I do have a similar but I guess unrelated issue where plasma-nm asks to open the wallet but can't even though every other app can fine but my kwallet has been around for ages and includes downgrades to kde4 and upgrades to plasma5 again. We also have the kdelibs4 wallet migration try to pop up even for new Plasma 5 installs with no history.
I can confirm the issue. Tried to connect to VPN from the KF5 Network settings plasmoid. I didn't get any password prompt and the connection attempt timed out with message "necessary secrets were not provided". There is a lot more info about this bug in the redhat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1228119 My system is a bit hacky. I use Debian Stretch with Kubuntu's KDE5 5.3.1 from http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/ . I just wanted to point out that this bug is not Fedora specific, but affects also Kubuntu. Workaround: 1) Change file ~/.kde/share/config/kwalletrc or file ~/.kde/share/config/kwalletmanagerrc setting Enabled=true in section [Wallet] 2) Setting AlreadyMigrated=true might also help 3) Restart sddm 4) Try vpn connection again. 5) This time wallet dialog appears - click cancel (appeared twice for me). 6) Then the regular NM password prompt pops up, login and surf happily. PS: I see in dmesg: [ 5511.055608] kwalletd5[30145]: segfault at 8 ip 00007f29ddc230fc sp 00007ffff79dc480 error 4 in libQt5Core.so.5.4.1[7f29dd911000+533000] [ 5712.135258] kactivitymanage[29698]: segfault at 7f9248854cd0 ip 00007f923011b031 sp 00007ffed2d3ac48 error 4 in libQt5Sql.so.5.4.1[7f9230107000+3f000] But I think this is another issue.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!