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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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,
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781418
Title:
User not being initialized correctly on login
To manage notifications about this bug go to:
Have just went to this bug while trying to solve PAM warnings problem on my
AskUbuntu question ( https://askubuntu.com/q/1096931/66509 ).
So I have installed all mentioned package with:
sudo apt-get install libpam-winbind libpam-kwallet4 libpam-kwallet5
and got the result - my user is
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
I don't know why this happens, but seems to be something broken by the
way and update didn't fix anything in my case. There are still 2 calls
to 'setgroups(0, NULL)', one for libpam-kwallet and another for
pam_kwallet5 after my user and group are already set. Of course, this
drops all
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781418
Title:
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
ZdravkoG:
After the package upgrades did you reboot before testing? I've not been
able to reproduce it since whereas before the upgrade it would happen
100% of the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
I added an additional log report to the function drop_privileges() since
that contains a call to setgroup(0, NULL) which, if called as the user,
would have the effect of removing all the supplementary groups.
diff --git a/pam_kwallet.c b/pam_kwallet.c
index 07b357d..147f129 100644
---
Hello,
I had this problem on 16.04 after a normal maintenance "apt dist-
upgrade" and it caused quite some confusion. A big Thank You to the
people who published the workaround.
I sincerely hope this regression in a LTS release gets fixed soon.
--
You received this bug notification because
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,
Some other notes:
https://unix.stackexchange.com/questions/458194/missing-groups-at-each-
startup/
and horrible unconclusive Fedora bugreport:
https://bugzilla.redhat.com/show_bug.cgi?id=1581495
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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
: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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781418
Title:
User not being initialized correctly on
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781418
Title:
User not being
I can confirm *commenting out* (and not the reverse) these lines in
/etc/pam.d/lightdm fixes the problem:
auth optional pam_kwallet.so
auth optional pam_kwallet5.so
Cheers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781418
Title:
Simon
Copied you on this one. Is this potentially as a result of the recent
CVE upload to Libpam... Sounds like a real regression.
** Also affects: kwallet-pam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
24 matches
Mail list logo
