The problem happens for me only after some time. Restarting winbind
fixes it for some minutes.
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
https://bugs.launchpad.net/bugs/546874
You received this bug notification because you are a member of Ubuntu
Server Team,
If the workarounds above didn't work, why do you think that's the same
bug at all? I think you should open a new report.
The other issue is that if you actually upgraded your system using 'apt-
get upgrade' (not even 'dist-upgrade'?!), that's not the correct
procedure and is likely to break. See
Got the same problem:
- can not log in
- can not change passwork
- can not create new user
1. case: native 9.10 srv to 10.04 srv with apt-get upgrade. There was no Samba
but Likewise 5.4.0.7985. Testbed Intel Celeron 667MHz
2. case production file and www server 9.10 srv. Samba. No Likewise.
Reproduced on a beta2 candidate, installing samba-server task, cannot log in on
console.
See attached /etc/pam.d contents.
** Attachment added: /etc/pam.d contents
http://launchpadlibrarian.net/43230186/pamd.tar
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
** Changed in: samba (Ubuntu Lucid)
Status: Triaged = In Progress
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
https://bugs.launchpad.net/bugs/546874
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Tags added: iso-testing
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
https://bugs.launchpad.net/bugs/546874
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
This bug was fixed in the package samba - 2:3.4.7~dfsg-1ubuntu2
---
samba (2:3.4.7~dfsg-1ubuntu2) lucid; urgency=low
* debian/winbind.pam-config: Fix password PAM profile for winbind, thanks to
Steve Langasek for investigation and fix (LP: #546874)
* debian/winbind.prerm,
This happened to me on a clean install of ubuntu server i386 with
packages dns, openssh, lamp, and samba. I was not able to login after
the install. Above fix worked for me chrooted from a live cd.
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
Disable Winbin NT/AD authentication by running:
sudo dpkg-reconfigure -plow libpam-runtime
... worked for me. Pretty show stopping bug! I experienced this on 64
bit install of Lucid beta.
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
** Changed in: samba (Ubuntu)
Milestone: None = ubuntu-10.04-beta-2
** Also affects: samba (Ubuntu Lucid)
Importance: High
Status: Triaged
** Changed in: samba (Ubuntu Lucid)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: samba (Ubuntu Lucid)
Milestone:
breaks the passwd and the systemsettings way of changing the password in
lucid beta1.
workaround works,
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
https://bugs.launchpad.net/bugs/546874
You received this bug notification because you are a member of Ubuntu
http://cdimage.ubuntu.com/ubuntu-server/daily/20100331/
Tried installing with this: turns out login is broken. Even holding
SHIFT to go into single-user mode comes up with a read-only filesystem I
can't remount as rw to run the dpkg-reconfigure on.
** Also affects: shadow
Importance:
** Changed in: base-passwd
Status: New = Invalid
** Changed in: shadow
Status: New = Invalid
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
https://bugs.launchpad.net/bugs/546874
You received this bug notification because you are a member of Ubuntu
Well, if base-passwd shadow aren't impacted, then what the heck are?
I'm curious how a samba package ends up breaking normal user login
password changing processes. I knew to check here about the problem
because I tried updating some samba packages yesterday ended up
breaking Samba access to a
There seem to be two issues:
* one is about the profile itself, which apparently breaks pam config when
enabled
* the other is about winbind.{postinst,prerm} not calling pam-auth-update
--package to enable/disable the profile (which is marked Default:yes, so it
will get enabled by the next
If you simply remove winbind, it fails to update pam config. You still
must run pam-auth-update to unfsck it.
--
passwd - can't login, change password (pam_winbind pam-auth-update profile)
https://bugs.launchpad.net/bugs/546874
You received this bug notification because you are a member of
If this is Winbind NT/AD authentication that you're having to disable,
then the bug is in samba. Reassigning.
** Package changed: pam (Ubuntu) = samba (Ubuntu)
** Changed in: samba (Ubuntu)
Status: New = Triaged
--
passwd - can't login, change password
sudo dpkg-reconfigure -plow libpam-runtime
Fixed it.
It was set to use Winbind NT/Active Directory authentication. I did not ask it
to this, it seems maybe Samba is setting this by default.
Thanks
--
passwd - can't login, change password
https://bugs.launchpad.net/bugs/546874
You received this
Yes, the purpose of the 'winbind' package is to provide integration with
a Windows domain or AD realm; that extends to enabling pam_winbind by
default now that this is supported.
Of course, any problems this causes for you being able to use your local
system accounts is a bug.
BTW, the idiomatic
19 matches
Mail list logo
