+- Maui Forums (https://forums.mauilinux.org)
+-- Forum: Maui Support (https://forums.mauilinux.org/forumdisplay.php?fid=74)
+--- Forum: Plasma Desktop (https://forums.mauilinux.org/forumdisplay.php?fid=84)
+--- Thread: [Closed] - KWallet breaks with a simple logout/in. (/showthread.php?tid=24027)
RE: KWallet breaks with a simple logout/in. - kdemeoz - 23rd October 2016
Hi again & thanks. No, afraid not:
Restore Previous Session has been my default setting since Day 1 of my Maui usage, & since about Day 1.5 of my Mint 17.x KDE4 usage from late 2013.
Whilst logically there must be a cause for & hence a solution to this bug, i have a sinking feeling that for the foreseeable future it mightn't reveal itself to me.
RE: KWallet breaks with a simple logout/in. - kdemeoz - 23rd October 2016
Following some hours more of online research today, looking for possible clues to this ongoing problem, i have some more questions pls:
1. http://www.gossamer-threads.com/lists/gentoo/user/318788?page=last --> did not initially seem relevant to MY problem [& i'm not even sure if it applies to Maui / Neon / Plasma 5.8.x at all], but i decided to examine the directory mentioned; /etc/sddm. There's only one file there; Xsession. I opened it in Kate, but it's far too complex for me to understand. Is there any possibility this file is not correctly accessed following a re-login, causing the kwallet password prompt & rejection? Or [more likely], is this an entirely irrelevant red herring?
2. https://nwrickert2.wordpress.com/2016/08/19/taming-kdewallet/#comments --> similar questions to above; i'm not sure if this is applicable & relevant to me.
3. I looked again at Plasma's KDE Wallet and Wallet Manager. The specific reason, throughout my thread here, for me alleging that kwallet is "broken" after logging out/in [but is instead perfectly fine after a cold start or a hot reboot], is that every time i start my Tower, or Resume it, or Reboot it, or Logout/In, the FIRST THING i then do is to activate my VPN, by clicking the Network Manager applet in the System Tray. Then, & only following the logout/in rather than any other start mode, it prompts me for my kwallet password [which should not occur, as it should have got this from my login], & then it rejects my inputted password.
Hence my next question: should i be surprised that Network Manager is not listed as one of the applications authorised to connect to my wallet? How can that be right? If it's not authorised, WHY do i even get prompted when i try to connect to the VPN after logout/in, & alternatively HOW could i have no problem activating my VPN via Network Manager from a cold-start, reboot, or resume?
Do you think it might be worthwhile me trying either of these: (a) delete the current wallet & create a new one? (b) create a second wallet alongside the current one?
I know this post is now tortuously long, & my thread is also complicatedly long, but here's another bit of info i've realised wrt this problem. When i do a reboot & then login, i hear the nice Maui musical chord signifying the startup. Conversely, after only a logout/in, there is NO music, & in fact the Audio Volume applet is frequently broken [its popup is blank]. Maybe therefore there is a much deeper problem, causing both of these faults?
RE: KWallet breaks with a simple logout/in. - davidedmundson - 23rd October 2016
>1
> Is there any possibility this file is not correctly accessed following a re-login
Not really, you'd see much bigger issues.
Unless you have any specific reason to think it is SDDM, I don't think there's any reason to think it is.
What is probably much more relevant is the PAM -> KWallet backend which unlocks your wallet when you login. Do you have the same password for your wallet as your user? Any logs from there should be in /var/log/auth.log
After logout do you have any files /tmp/kwallet* ? Is kwalletd5 still running?
RE: KWallet breaks with a simple logout/in. - kdemeoz - 24th October 2016
Thanks David,
"Do you have the same password for your wallet as your user?"
Well, it was always my intention for them to be the same, but i have no recollection during / after my Maui installation of having been prompted specifically for a kwallet password. My memory in general is bad & maybe i'm wrong here & was prompted after all, in which case i would have certainly used the same pswd as my user login.
My Maui installation to my Tower's SSD was over the top of my existing Mint 17.3 KDE4 installation, in root, but i deliberately did NOT format my separate /opt & /home partitions, ie, i reused them from Mint.
Given that i did use kwallet in Mint, could it be that one of the legacy files buried in /home, still had my original kwallet pswd, which was then why once i first logged into Maui i was not prompted for my wallet pswd?
Two more disclosures, also in case relevant. My /home partition was in Mint encrypted from installation via Ubiquity & is still so in Maui.
Also I deliberately use /tmp mounted as a ramdrive via this fstab line:
Code:
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0I looked at /var/log/auth.log :
Code:
Oct 23 09:10:46 kdemeoz-Z97-HD3 sudo: kdemeoz : TTY=unknown ; PWD=/home/kdemeoz ; USER=root ; COMMAND=/usr/lib/linuxmint/mintUpdate/checkAPT.py
Oct 23 09:10:46 kdemeoz-Z97-HD3 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 23 09:10:51 kdemeoz-Z97-HD3 sudo: pam_unix(sudo:session): session closed for user root
Oct 23 09:17:01 kdemeoz-Z97-HD3 CRON[14302]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 23 09:17:01 kdemeoz-Z97-HD3 CRON[14302]: pam_unix(cron:session): session closed for user root
Oct 23 09:55:46 kdemeoz-Z97-HD3 sudo: kdemeoz : TTY=unknown ; PWD=/home/kdemeoz ; USER=root ; COMMAND=/usr/lib/linuxmint/mintUpdate/checkAPT.py
Oct 23 09:55:46 kdemeoz-Z97-HD3 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)Code:
Oct 23 17:25:47 kdemeoz-Z97-HD3 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 23 17:25:51 kdemeoz-Z97-HD3 sudo: pam_unix(sudo:session): session closed for user root
Oct 23 17:42:05 kdemeoz-Z97-HD3 polkit-agent-helper-1[4349]: pam_ecryptfs: pam_sm_authenticate: /home/kdemeoz is already mounted
Oct 23 17:42:05 kdemeoz-Z97-HD3 polkitd(authority=local): Operator of unix-session:2 successfully authenticated as unix-user:kdemeoz to gain TEMPORARY authorization for action org.kde.kcontrol.kcmkwallet5.save for system-bus-name::1.418 [/usr/bin/systemsettings5] (owned by unix-user:kdemeoz)
Oct 23 18:10:47 kdemeoz-Z97-HD3 sudo: kdemeoz : TTY=unknown ; PWD=/home/kdemeoz ; USER=root ; COMMAND=/usr/lib/linuxmint/mintUpdate/checkAPT.py
Oct 23 18:10:47 kdemeoz-Z97-HD3 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)Code:
Oct 22 20:05:10 kdemeoz-Z97-HD3 systemd-logind[1091]: New session 8 of user sddm.
Oct 22 20:05:10 kdemeoz-Z97-HD3 sddm-helper: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Oct 22 20:05:10 kdemeoz-Z97-HD3 sddm-helper: pam_systemd(sddm-greeter:session): Cannot create session: Already running in a session
Oct 22 20:05:12 kdemeoz-Z97-HD3 systemd-logind[1091]: Removed session 1.
Oct 22 20:05:19 kdemeoz-Z97-HD3 sddm-helper: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Oct 22 20:05:19 kdemeoz-Z97-HD3 sddm-helper: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Oct 22 20:05:19 kdemeoz-Z97-HD3 systemd-logind[1091]: New session 9 of user kdemeoz.
Oct 22 20:05:19 kdemeoz-Z97-HD3 sddm-helper: pam_unix(sddm:session): session opened for user kdemeoz by (uid=0)
Oct 22 20:05:19 kdemeoz-Z97-HD3 sddm-helper: pam_systemd(sddm:session): Cannot create session: Already running in a session
Oct 22 20:05:19 kdemeoz-Z97-HD3 sddm-helper: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Oct 22 20:05:19 kdemeoz-Z97-HD3 sddm-helper: pam_kwallet5(sddm:session): pam_kwallet5: final socket path: /tmp/kwallet5_kdemeoz.socket
Oct 22 20:05:19 kdemeoz-Z97-HD3 sddm-helper: pam_unix(sddm-greeter:session): session closed for user sddm
Oct 22 20:05:20 kdemeoz-Z97-HD3 polkitd(authority=local): Registered Authentication Agent for unix-session:9 (system bus name :1.249 [/usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_AU.UTF-8)I looked at /tmp :
I can see a file kwallet5_kdemeoz.socket, but no other file containing the string kwallet. As you said to look "After logout", do you mean i need to logout, then switch to a TTY, login to it, then inspect /tmp again via CLI?
EDIT - I believe that KDE4 & Plasma5 are different animals, but as a point of reference, i am certain i could reliably logout then in to Mint 17.3 KDE4 without breaking kwallet, ie, without being prevented from reconnecting to my VPN, without being asked manually for my wallet password, & without it being rejected.
RE: KWallet breaks with a simple logout/in. - davidedmundson - 24th October 2016
>Mint. Given that i did use kwallet in Mint, could it be that one of the legacy files buried in /home, still had my original kwallet pswd, which was then why [once i first logged into Maui] i was not prompted (i think] for my wallet pswd?
Plausible, the encryption scheme even changed between the two releases.
> "After logout", do you mean i need to logout, then switch to a TTY, login to it, then inspect /tmp again via CLI?
Yes, that's what I meant:
RE: KWallet breaks with a simple logout/in. - kdemeoz - 25th October 2016
(24th October 2016, 15:53)davidedmundson Wrote: >Mint. Given that i did use kwallet in Mint, could it be that one of the legacy files buried in /home, still had my original kwallet pswd, which was then why [once i first logged into Maui] i was not prompted (i think] for my wallet pswd?
Plausible, the encryption scheme even changed between the two releases.
> "After logout", do you mean i need to logout, then switch to a TTY, login to it, then inspect /tmp again via CLI?
Yes, that's what I meant:
---[A]---
I've now looked at /tmp, "after logout", in tty2. That same file i previously mentioned, kwallet5_kdemeoz.socket, was the only one therein containing the string kwallet. I cannot tell from your question; is this file's existence a good thing or a bad thing?
I then Ctrl+Alt+F7'd back to the login screen, logged in, was pleasantly surprised that this time the start-music did play, but alas kwallet was still broken... ie, as soon as i tried to connect to my VPN i was [as usual] asked for my wallet password, which [as usual] was rejected, after which [as usual] my attempt to connect to my VPN was also rejected. Sigh.
Still in the graphical session, in Konsole i ran sudo systemctl restart sddm. As usual, though this did restart the session, the new session post-login still had a broken wallet. I returned to tty2, & therein repeated my sudo systemctl restart sddm, but [can you guess?] the new session post-login still had a broken wallet.
Now i once again gave up & did the full reboot, after which all is good again... but the next time i want or need to logout/in, this whole mess will repeat.
---[B]---
"Plausible, the encryption scheme even changed between the two releases".
Are you implying that my decision to reuse my Mint's encrypted /home partition when i installed Maui into root, was bad practice & therefore contributing to my hassles now?
RE: KWallet breaks with a simple logout/in. - kdemeoz - 27th October 2016
David?
RE: KWallet breaks with a simple logout/in. - kdemeoz - 28th October 2016
Hi starbuck. Do you have any thoughts on what i should do now pls, given the startling statement by David, but his lack of subsequent clarification?
RE: KWallet breaks with a simple logout/in. - starbuck - 28th October 2016
From what I read its either you have set a password in Mint 17.3 and since the encryption scheme has changed, that might be the problem. I dont know if you can simply reset / remove your current wallet and start a new one in your current system.
Otherwise, have you tried entering NO (aka "blank") password at all and just click continue?
RE: KWallet breaks with a simple logout/in. - kdemeoz - 29th October 2016
I'm beginning [/continuing] to fret that i might have made a biiiiiiiiiiiiiiiiiiiiiiig mistake by reusing my Mint's encrypted /home partition when i installed Maui [even though ALL the research i did in 2013 when i first began investigating Linux to free myself from Windows said that the entire rationale for having separate / & /home partitions was to safeguard & reuse all my data whenever i wanted to reinstall or replace my Linux distro].
One part of me wonders if i should now just abandon all further attempts to troubleshoot this tricky wallet / logout/in problem & reinstall Maui by blowing away BOTH / & /home -- literally a completely clean start. The other part of me says that's idiotic & a huge over-reaction [not to mention a vast amount of work given Maui is now tweaked exactly how i want it, & my (very large) number of programs are all likewise installed & tweaked just how i want them].
My level of confidence in solving this myself is not high, given that David set off that verbal bomb but then went silent, & both starbuck & leszek (in a different thread] have said or implied that they don't know about kwallet & encryption wrt KDE4 vs Plasma5. That means my only alternative seems to be trial & error [many hours over several days of online research have not helped], which unnerves me -- given my /home partition is encrypted, & this Tower is my primary pc, i'm quite nervous that if i experiment with any of delete kwallet / change kwallet pswd / set kwallet pswd to blank / create second kwallet, could it cripple my system? Eg, it would be a calamity if i then rebooted & found that i then could not login due to /home refusing to decrypt because i'd buggered the password...?
Following is the result of searching my /home for all instances of "wallet". I assume [but do not know] that some of these might be legacy from Mint KDE4, & others might be current from Maui Plasma5. I speculate [but again do not know] that Plasma5 probably does not read any folders that were from KDE4... but what if some of those folders are common to both DEs, & so now cause Plasma5 to be confused?
All suggestions & comments will be gratefully received by this confused little black duck.