When my wife enters her user name the system says it cannot recognize it so she is forced to enter it a second time. Fix?

Could this be a capitalization problem?
User names are case sensitive, and therefore capitalizing them will mean they are rejected.

DannyStaple wrote:

>Support request #1997 on Ubuntu changed:
>https://launchpad.net/distros/ubuntu/+ticket/1997
>
>Comment:
>Could this be a capitalization problem?
>User names are case sensitive, and therefore capitalizing them will mean they are rejected.
>
>
>
>
Thanks for the prompt response Danny but the issue you raise regarding
capatilization is not relevant. My wife's user name is dswart (all
lower case) and time and again (almost invariably I should say) she
enters it only to be told it is not recognized. Then she enters it a
second time and it works. Its a real mystery.

Not that common a name (Danny I mean -- since mostly it is Dan) but my
youngest brother is Danny Swart.

. . Ted Swart . .

Just to clarify, are you running a standard Ubuntu Dapper (6.06) desktop with gnome?

Could she simply have mistyped her password?

DannyStaple wrote:

>Support request #1997 on Ubuntu changed:
>https://launchpad.net/distros/ubuntu/+ticket/1997
>
>Comment:
>Just to clarify, are you running a standard Ubuntu Dapper (6.06) desktop with gnome?
>
>Could she simply have mistyped her password?
>
>
>
YES. I am running a standard 6.06
NO. My wife does not mistype. I have watched he in action several
times. My daughter jswart sometimes uses the same machine and does no
thave the same problem.

As a control, try creating another temporary user for your wife with a different user name, and get her to log in on that a few times, and see if the problem still occurs. Make sure she chooses another password for it as well...

While it is not impossible that there is a bug specifically with the name "dswart" in the gnome login ui, it sounds quite unlikely.

Does your daughter use her own login and password?

DannyStaple wrote:

>Support request #1997 on Ubuntu changed:
>https://launchpad.net/distros/ubuntu/+ticket/1997
>
>Comment:
>As a control, try creating another temporary user for your wife with a different user name, and get her to log in on that a few times, and see if the problem still occurs. Make sure she chooses another password for it as well...
>
Sounds rather an odd thing to do. This would not give her access to her
email bookmarks etc. I you are suggesting this simply to see if another
user name and password would work correctly I am not sure what this
would tell us. What I and my wife would really like is to get rid of
the glitch.

>While it is not impossible that there is a bug specifically with the name "dswart" in the gnome login ui, it sounds quite unlikely.
>
>Does your daughter use her own login and password?
>
>
Yes. My daughter uses her own user name and her own password and, as I have laready indicated she has no problems.

On Sat, 2006-10-07 at 18:48 +0000, TedSwart wrote:
> >As a control, try creating another temporary user for your wife with a different user name, and get her to log in on that a few times, and see if the problem still occurs. Make sure she chooses another password for it as well...
> >
> Sounds rather an odd thing to do. This would not give her access to her
> email bookmarks etc. I you are suggesting this simply to see if another
> user name and password would work correctly I am not sure what this
> would tell us.

This would tell us if it is something your wife is doing, or if there is
some other glitch. Process of elimination and all of that. It is merely
just a test.

> What I and my wife would really like is to get rid of
> the glitch.

Absolutely, but it may not necessarily be the software is what I am
getting at.

> >Does your daughter use her own login and password?
> >
> >
> Yes. My daughter uses her own user name and her own password and, as I have laready indicated she has no problems.

Right. That is definately interesting then. Try the above test, and see
what happens. I have some ideas, but this may or may not qualify them.

After one of these failures, look at the /var/log/auth.log file. This ought to shed some light on the situation.

Jon Anderson wrote:

>Support request #1997 on Ubuntu changed:
>https://launchpad.net/distros/ubuntu/+ticket/1997
>
>Comment:
>After one of these failures, look at the /var/log/auth.log file. This ought to shed some light on the situation.
>
>
>
    Nice try Jon but I am afraid it did not help at all. The
/var/log/auth.log file simply says:

bad user name [dswart]

and this is followed immediately by:

session opened for user dswart by (uid:0)

after the succesful second entry of the user name.

I have also tried registering my wife under a different name and
password which works just fine but does not get us anywhere.

Hmmmm... would you attach your /etc/pam.d/login, /etc/pam.d/[gkx]dm and /etc/pam.d/common*?

Also, the log file really just says "bad user name [dswart]"? When I fail to log into my box, it says:

Oct 12 15:50:36 nick login[3818]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=tty2 ruser= rhost= user=jon
Oct 12 15:50:38 nick login[3818]: FAILED LOGIN (1) on 'tty2' FOR `jon', Authentication failure
Oct 12 15:50:57 nick login[3818]: (pam_unix) check pass; user unknown
Oct 12 15:50:57 nick login[3818]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=tty2 ruser= rhost=
Oct 12 15:50:59 nick login[3818]: FAILED LOGIN (2) on 'tty2' FOR `UNKNOWN', User not known to the underlying authentication module

or, using KDM:

Oct 12 15:57:14 nick kdm: my.hostname.domain:1[7609]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=my.hostname.domain:1 ruser= rhost=my.hostname.domain user=jon

Jon Anderson wrote:

>Support request #1997 on Ubuntu changed:
>https://launchpad.net/distros/ubuntu/+ticket/1997
>
>Comment:
>Hmmmm... would you attach your /etc/pam.d/login, /etc/pam.d/[gkx]dm and /etc/pam.d/common*?
>
>Also, the log file really just says "bad user name [dswart]"? When I fail to log into my box, it says:
>
>Oct 12 15:50:36 nick login[3818]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=tty2 ruser= rhost= user=jon
>Oct 12 15:50:38 nick login[3818]: FAILED LOGIN (1) on 'tty2' FOR `jon', Authentication failure
>Oct 12 15:50:57 nick login[3818]: (pam_unix) check pass; user unknown
>Oct 12 15:50:57 nick login[3818]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=tty2 ruser= rhost=
>Oct 12 15:50:59 nick login[3818]: FAILED LOGIN (2) on 'tty2' FOR `UNKNOWN', User not known to the underlying authentication module
>
>or, using KDM:
>
>Oct 12 15:57:14 nick kdm: my.hostname.domain:1[7609]: (pam_unix) authentication failure; logname= uid=0 euid=0 tty=my.hostname.domain:1 ruser= rhost=my.hostname.domain user=jon
>
>
>
Jon; Yes indeed there is more in the /var/log/ directory. The full
details are:

Oct 12 09:37;50 caesar gdm[4571]: pam_unix bad user name [dswart]
Oct 12 09:37;59 caesar gdm[4571]: session opened for dswart by (uid=0)
Remember there is no attempted password entry between these two lines
since the screen simply offers a second chance at entering the user name.

Have had a look in the /etc/pam.d directory at login, [gkx]dm and
common*? files without learning much

The really, really strange thing about this is that Googling for pam_unix "bad user name" turns up *nothing*. Not even source code.

Actually, it turns up this page.

Does your common-account file say:
account required pam_unix.so

common-auth:
auth optional pam_group.so
auth required pam_unix.so nullok_secure

common-passwd:
password required pam_unix.so nullok obscure min=4 max=8 md5

common-session:
session required pam_unix.so
session optional pam_foreground.so

?

I tried google code search, and did not find anything helpful.

Just a thought, but if you do "grep dswart /var/log/*" is there anything there that might be helpful.

That "bad user name" may well be coming from gdm. Have you tried getting her to login from a console or KDM? Maybe you will see a different error message that is more easily identified.

Danny