Summary: | gnome-base/gdm-2.20.7: Unable to use keyboard at gdm login prompt after editing /etc/conf.d/net | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gabriel Marcano <gabemarcano> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://www.debianhelp.org/node/4064 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gabriel Marcano
2008-08-09 20:43:52 UTC
The workaround from the debianhelp page in the URL page is also valid. By running "XDMCP chooser" and canceling out, the keyboard begins to function correctly in gdm, thus allowing me to continue into a session. Another note: The keyboard begins to function once the XDMCP chooser is initiated. By exiting the X server (Ctrl-alt-backspace) or canceling out of the chooser (which apparently does the same thing; I don't know the inner workings of the chooser), gdm is restarted and the keyboard is functional once more, allowing me to login and start a session. It appears that the order GDM is loaded does matter. To "optimize" GDM, I had added it to the "boot" runlevel. By placing it in the "default" runlevel, it began to work as expected. no wonder it didn't work :) The thing is, I obtained this "optimization" from one of the many Gentoo wiki sites. Also, the problem doesn't manifest itself unless I modified /etc/conf.d/net. That, I would say, is odd. I'm just glad it's working now. For the record, the various Gentoo wiki articles are almost never written by Gentoo developers. Some articles may be very good, some very dangerous. YMMV. |