On Sun, 27 May 2012 21:53:59 +0200
Jakub Wilk wrote:
> >It seems that this only happens when a user wants to unlock the
> >screen, not when logging in.
>
> Does it happen regardless of whether the entered password was correct
> or not?
This is always happening, regardless of if the password is
severity 544687 serious
owner 544687 !
thanks
* Christoph Pleger , 2012-05-24, 10:33:
That is, unix2_chkpwd is called recursively again and again and the
user cannot be authenticated.
It seems that this only happens when a user wants to unlock the screen,
not when logging in.
Does it happen r
Processing commands for cont...@bugs.debian.org:
> severity 544687 serious
Bug #544687 [libpam-unix2] libpam-unix2: forks numerous instances of
unix2_chkpwd
Severity set to 'serious' from 'important'
> owner 544687 !
Bug #544687 [libpam-unix2] libpam-unix2: forks numerous instances of
unix2_chkp
> That is, unix2_chkpwd is called recursively again and again and the user
> cannot be authenticated.
It seems that this only happens when a user wants to unlock the screen,
not when logging in.
--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscr
Hello,
though I obviously do not have the exactly same bug occurring, because the
corresponding change that introduced my bug took place two days after
Jakub's last message, I add my bug description to this report, because my
bug fits perfectly to the subject. That is, unix2_chkpwd is called
recur
5 matches
Mail list logo
