On 10/13/2011 10:16 AM, Adam Williamson wrote:
On Thu, 2011-10-13 at 12:04 -0500, Mike Chambers wrote:
> On Wed, 2011-10-12 at 15:38 -0700, Adam Williamson wrote:
>> On Wed, 2011-10-12 at 14:20 -0800, Erinn Looney-Triggs wrote:
>>
>>> Cool, well glad to see that is being dealt with. No takers for the GDM
>>> problem?
>> Not sure about that one, haven't seen it on either of my systems. They
>> both log me in successfully every time.
> The one thing that I ran into yesterday when doing some test builds, was
> when creating a user I tried to use a specific UID in 500 (due to things
> on my server side) and it caused problems in kdm or gdm. Once I did an
> install and used the default of 1000 (changed things on my server side
> to match and for future upgrade) then things seemed to work as should.
> Although the only thing I didn't test was gdm, as I am using KDE and
> didn't do another install to see what would happen on the gdm/gnome side
> with default user.
>
> If your upgrading then maybe there is a problem since using older #'s,
> then again might be something else totally different.
What I found happened if you used a uid under 1000 was the user simply
didn't show up in gdm at all, as it's considered a 'system user'.
In my case at least this isn't the problem. It would have been had the
alpha install gone correctly, but it managed to corrupt my partitions so
a clean install it was. Thus I stare out from the lofty heights of UID
1000 :).
No this may be related to the fingerprint reader, or at least after
activating the fingerprint bit the whole system went a little more
sideways than usual.
-Erinn