In my case, I discovered that it was due to a null password : I created a guest account and configured gdm so that passwod ios not required for this account. In order to be coherent I deleted the password with 'passwd -d guest'. This creates a 'null' password that causes the assertion fail. If an account without password is authorized, then in liboobs-2.22.0/oobs/oobs-usersconfig.c line 362, the assertion g_return_val_if_fail ((login && password && homedir && shell), FALSE); should be replaced by g_return_val_if_fail ((login && homedir && shell), FALSE).
As having a password does not change the behaviour of gdm (it still not requires the passwd for this guest account), I put a password to "guest" and everything is now ok.
I had a look to the backends outputs previously attached above:
- in test-backends output, there is a password for root account. This should be the cause of the pb, as for me
- in UsersConfig.out, I do not see anything wrong about passwords..
I had the same problem.
In my case, I discovered that it was due to a null password : I created a guest account and configured gdm so that passwod ios not required for this account. In order to be coherent I deleted the password with 'passwd -d guest'. This creates a 'null' password that causes the assertion fail. If an account without password is authorized, then in liboobs- 2.22.0/ oobs/oobs- usersconfig. c line 362, the assertion g_return_ val_if_ fail ((login && password && homedir && shell), FALSE); should be replaced by g_return_ val_if_ fail ((login && homedir && shell), FALSE).
As having a password does not change the behaviour of gdm (it still not requires the passwd for this guest account), I put a password to "guest" and everything is now ok.
I had a look to the backends outputs previously attached above:
- in test-backends output, there is a password for root account. This should be the cause of the pb, as for me
- in UsersConfig.out, I do not see anything wrong about passwords..