|
Bugzilla – Full Text Bug Listing |
| Summary: | GDM should use the default keyboard layout by default | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Forgotten User Drfk9mafMw <forgotten_Drfk9mafMw> |
| Component: | GNOME | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User Drfk9mafMw
2008-10-28 16:38:27 UTC
What is the UID of those special users? The users I wanted to add later had 2751 and 10002. But maybe this is a misunderstanding: I don't think that the UID is the problem at all. I just specified those in order to be able to reuse the respective already existing homedirs without changes. As I see it, it is not possible to match new users to existing homedirs. This has always worked fine for me -- and unless I use GDM it still works fine. You are using yast to add the users or manually editing? Yes, I was using YaST to add another user, specified a certain UID, and to reuse an existing home folder. Any chance these users have password that have characters that are not letters or numbers? No, it's simple mixed lower/upper case letters and numbers, nothing else. I will try again with beta4 and report back if anything changed. Sometimes, the most obvious does not occur to one. It's so simple: GDM simply does not use the systemwide keyboard layout but proposes its own. So instead of German I had English and the password entered was always wrong. And I never checked that (because KDM does and I was used to that): All there is remaining of this bug is that GDM could use the default layout instead of the one that matches the language. There is no problem with the authentication itself. Aha! Known bug, thanks Daniel. *** This bug has been marked as a duplicate of bug 440863 *** |