Re: [e-users] desklock passwd not working

[Mister O. <mis...@go...>]

Hi,

yes I've checked my E compile options and PAM is definitely enabled for
me.
The strange thing is, that it worked a long time and then after updating
to the newest SVN release sometimes it works, sometimes not. The change
is always after recompiling, it doesn't seem runtime related.

I suppose it has something to do with changes in the code of E or PAM???

--
Mr. Olli

Am Freitag, den 09.01.2009, 14:53 -0200 schrieb Wido:
> Yes, i recall i got the same issue in a previous compilation. It used
> to work some time before, and pam is installed and working and E is
> also compiled with pam support (as i wasn't sure, i recompiled E with
> --enable-pam)
> 
> 2009/1/9 Mister Olli <mis...@go...>:
> > Hi...
> >
> > I also have some troubles with the desktop lock mechanism... I haven't
> > found a pattern when it happens, but from time to time I'm unable to
> > unlock my desktop.
> >
> > I'm sure that I entered the password correctly (after 10 times in a row,
> > watching your fingers ;-)).
> >
> > The only solution is to switch to a console, login, set the E_IPC
> > variable accordingly and issue a 'enlightenment_remote -restart'.
> >
> > My systemlog says the following:
> > =================================================
> > Dec 18 11:56:31 phoenix unix_chkpwd[2079]: no password supplied
> > Dec 18 11:56:31 phoenix unix_chkpwd[2080]: no password supplied
> > Dec 18 11:56:31 phoenix enlightenment: pam_unix(system-auth:auth):
> > authentication failure; logname= uid=1000 euid=1000 tty= ruser=
> > rhost=localhost  user=dante
> > =================================================
> >
> > I doubt that it has something to do with my PAM config, since that
> > problem suddenly appeared after updating E from SVN, and I haven't
> > change for more than a half year...
> >
> >
> > greetz
> > olli
> >
> >
> > Am Donnerstag, den 08.01.2009, 15:58 -0200 schrieb Wido:
> >> Hi folks! i've recently noticed that when E locks, i can put ANYTHING
> >> and it will take it as a valid pass......i think that's wrong. I'm
> >> running lenny updated and e17 updated from less that a week. The
> >> output in /var/log/syslog is this
> >>
> >> Jan  8 15:55:46 lisa enlightenment: pam_sm_authenticate: Called
> >> Jan  8 15:55:46 lisa enlightenment: pam_sm_authenticate: username =
> >> [<username>]
> >> Jan  8 15:55:46 lisa enlightenment: Error attempting to parse
> >> .ecryptfsrc file; rc = [-5]
> >> Jan  8 15:55:46 lisa enlightenment: Warning: Using default salt value
> >> (undefined in ~/.ecryptfsrc)
> >> Jan  8 15:55:47 lisa enlightenment: Error attempting to open
> >> [/home/<username>/.ecryptfs/wrapped-passphrase] for reading
> >> Jan  8 15:55:47 lisa enlightenment: Error attempting to unwrap
> >> passphrase from file [/home/<username>/.ecryptfs/wrapped-passphrase];
> >> rc = [-5]
> >> Jan  8 15:55:47 lisa enlightenment: Error adding passphrase key token
> >> to user session keyring; rc = [-5]
> >> Jan  8 15:55:47 lisa kernel: [144626.824283] enlightenment[4460]:
> >> segfault at 33 ip b7bb5b35 sp bfdb6220 error 4 in
> >> libecore.so.0.9.9[b7ba6000+18000]
> >>
> >> tnks in advance ;