[Bug 1781418] Re: User not being initialized correctly on login
This bug is very old, if it is still an issue please update the bug with information from a supported release. ** Changed in: kwallet-pam (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Seems this was my problem too. What I noticed was that docker suddenly could not be run except as root. And none of the usual remedies for that had any effect. Luckily KDEwallet started demanding a login at the same time which pointed me to this bug. Tobias advice above fixed the problem so I think that confirms the diagnosis. Kubuntu 18.04 with KDE Plasma 5.12.7, KDE Frameworks 5.44.0 and Qt 5.9.5. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
I had the same issue. Even with libpam-kwallet5 to version 4:5.12.7-0ubuntu0.1. However, removing libpam-kwallet4 then rebooting appears to have resolved the issue. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
I faced this problem on two different machines (both lightdm + plasma desktop, on both I happily used this combination on Ubuntu 16.04 but once I upgraded to 18.04, or soon afterwards, I lost all my groups). Switched to sddm on both, it helped. So mayhaps lightdm should be dropped or downgraded, the issue (https://whatstatus.co/guess-ill-die) is fairly critical (usb doesn't work, sudo has issues, pluggable devices don't work). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Similarly to comment #15: updating libpam-kwallet-common, libpam- kwallet4 and libpam-kwallet5 to version 4:5.12.7-0ubuntu0.1 from proposed repository and rebooting didn't change anything for me. Only the workaround on comment #5 is currently useful, but I don't know which other problems it may cause... As an additional test, I uncommented again the 2 "pam_kwallet" lines in /etc/pam.d/lightdm, rebooted, and the problems reappeared. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Upgrading libpam-kwallet5 to 4:5.12.7-0ubuntu0.1 and a reboot fixed this problem on my machine. Thanks for linking this to #1784964 TJ. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Hi @tj, Yes, I initially have try logout/login (I think should be enough) - no result. After that full reboot - same thing. So, currently command 'id' give me result: uid=1000(zdravko) gid=1000(zdravko) групи=1000(zdravko) that's all. I can't see in this thread more deep discussions about what is going on. What is the actual reason. I take a look on the link in Your post #14. There is not clear description, again. Only strange standard error stream descriptor close is pointed as a reason. There are also other possible 'gaps' (not pointed there) - relying that buffer sized to length of c-string can safely keep all string (together with the terminator!, which will be there as result of 'strcpy()'). But this doesn't mater. Do You think that pointed there is enough for fixing the trouble? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Hi everyone, I have similar problems. Updating to libpam-kwallet packages (libpam- kwallet-common, libpam-kwallet4 and libpam-kwallet5) to version 4:5.12.7-0ubuntu0.1 from proposed repository didn't solve anything for me. Probably the problem solving is still in progress or may be never started (officially). Here I want to ask somebody from Canonical to assign this bug! So, final solution (official) to be available soon (on regular bionic-update). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
After the package upgrade to libpam-kwallet 4:5.12.7 from bionic- proposed the issue has gone away. That seems to be due to commit 8da1a470 included in this version: commit 8da1a47035fc92bc1496059583772bc4bd6e8ba6 Author: Maximiliano Curia Date: Fri May 4 22:06:06 2018 +0200 Avoid giving an stderr to kwallet Summary: The fixes for CVE-2018-10380 introduced a regression for most users not using kde, and some for kde sessions. In particular the reorder of the close calls and creating a new socket caused that the socket is always assigned the file descriptor 2, aka stderr. BUG: 393856 Test Plan: It works Reviewers: #plasma, aacid Reviewed By: aacid Subscribers: asturmlechner, rdieter, davidedmundson, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D12702 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-10380 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
I faced this problem on two different machines (both lightdm + plasma desktop, on both I happily used this combination on Ubuntu 16.04 but once I upgraded to 18.04, or soon afterwards, I lost all my groups). Switched to sddm on both, it helped. So mayhaps lightdm should be dropped or downgraded, the issue is fairly critical (usb doesn't work, sudo has issues, pluggable devices don't work). Picture in my case: - after lightdm login $ id uid=1000(marcin) gid=1000(marcin) groups=1000(marcin) - after sddm login $ id uid=1000(marcink) gid=1000(marcink) groups=1000(marcin),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),109(netdev),113(lpadmin),128(sambashare),147(lxd),999(docker) ** Bug watch added: Red Hat Bugzilla #1581495 https://bugzilla.redhat.com/show_bug.cgi?id=1581495 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Switched to gdm for now, which does not have this behaviour. `journalctl |grep lightdm` reveals these messages between cycles: ~~~ Aug 23 20:27:41 systemname systemd[1824]: pam_unix(systemd-user:session): session closed for user lightdm Aug 23 20:27:41 systemname systemd[1]: Removed slice User Slice of lightdm. Aug 23 20:27:44 systemname lightdm[1504]: ** (lightdm:1504): WARNING **: Session pid=6321: Error reading from session: Interrupted system call Aug 23 20:27:44 systemname lightdm[1504]: Failed to write utmpx: Permission denied Aug 23 20:27:44 systemname lightdm[10528]: pam_unix(lightdm:session): session closed for user username Aug 23 20:27:44 systemname dbus[1117]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.132" (uid=1000 pid=10528 comm="lightdm --session-child 12 21 ") interface="org.freedesktop.login1.Manager" member="ReleaseSession" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=1096 comm="/lib/systemd/systemd-logind ") Aug 23 20:27:44 systemname lightdm[10528]: pam_systemd(lightdm:session): Failed to release session: Access denied Aug 23 20:27:44 systemname lightdm[10528]: pam_kwallet(lightdm:session): pam_kwallet: pam_sm_close_session Aug 23 20:27:44 systemname lightdm[10528]: pam_kwallet5(lightdm:session): pam_kwallet5: pam_sm_close_session Aug 23 20:27:44 systemname lightdm[10528]: pam_kwallet(lightdm:setcred): pam_kwallet: pam_sm_setcred Aug 23 20:27:44 systemname lightdm[10528]: pam_kwallet5(lightdm:setcred): pam_kwallet5: pam_sm_setcred Aug 23 20:27:44 systemname lightdm[6321]: pam_kwallet5(lightdm:session): pam_kwallet5: Impossible to write walletKey to walletPipe Aug 23 20:27:44 systemname lightdm[1504]: ** (lightdm:1504): WARNING **: Error getting ConsoleKit session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files Aug 23 20:27:46 systemname lightdm[11277]: pam_kwallet(lightdm-greeter:setcred): (null): pam_sm_setcred Aug 23 20:27:46 systemname lightdm[11277]: pam_kwallet5(lightdm-greeter:setcred): (null): pam_sm_setcred Aug 23 20:27:46 systemname lightdm[11277]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Aug 23 20:27:46 systemname systemd[1]: Created slice User Slice of lightdm. Aug 23 20:27:46 systemname systemd[11281]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0) Aug 23 20:27:46 systemname systemd-logind[1096]: New session c3 of user lightdm. Aug 23 20:27:46 systemname systemd[1]: Started Session c3 of user lightdm. Aug 23 20:27:46 systemname lightdm[11277]: pam_kwallet(lightdm-greeter:session): (null): pam_sm_open_session Aug 23 20:27:46 systemname lightdm[11277]: pam_kwallet(lightdm-greeter:session): pam_kwallet: open_session called without kwallet_key Aug 23 20:27:46 systemname lightdm[11277]: pam_kwallet5(lightdm-greeter:session): (null): pam_sm_open_session Aug 23 20:27:46 systemname lightdm[11277]: pam_kwallet5(lightdm-greeter:session): pam_kwallet5: open_session called without kwallet5_key Aug 23 20:27:47 systemname lightdm[11331]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "username" Aug 23 20:28:02 systemname lightdm[11331]: pam_ecryptfs: pam_sm_authenticate: /home/username is already mounted Aug 23 20:28:02 systemname lightdm[11331]: pam_kwallet(lightdm:auth): (null): pam_sm_authenticate Aug 23 20:28:02 systemname lightdm[11331]: pam_kwallet5(lightdm:auth): (null): pam_sm_authenticate Aug 23 20:28:02 systemname lightdm[11241]: Oops, secure memory pool already initialized Aug 23 20:28:03 systemname lightdm[11277]: pam_unix(lightdm-greeter:session): session closed for user lightdm ~~~ -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
:D Well I most certainly hope people can *think* when they see the lines are active by default. Good luck to anyone who's trying to fix this bug ! Cheers. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Except I can't, so it has to stay there. Hopefully everybody who runs into this reads on... -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
@MibuKyoshiro True, sorry I seem to have been overly tired when writing this. I'm correcting it in my original comment. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1781418] Re: User not being initialized correctly on login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kwallet-pam (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwallet-pam in Ubuntu. https://bugs.launchpad.net/bugs/1781418 Title: User not being initialized correctly on login To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1781418/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
