Version: (using KDE KDE 3.2.0) Installed from: Gentoo Packages Compiler: gcc 3.2.3 OS: Linux After installing KDE 3.1.95, I cannot use KDM to log in: It simply does not accept anything I type! When I click on a Username, it is written to the Username: field, as expected, but a password cannot be entered. Same when I attempt to type my username by hand: no reaction. The log doesn't seem to have any interesting entries, so I have no clue what this could be. This (non-)behaviour was there in 3.1.94, too.
Well, there seems to be more than I saw before; note the last line. I think this is still a KDE 3.2 bug, since GDM, and KDM 3.1 worked well. [root@loona ~]# tail /var/log/kdm.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Sun Jan 25 18:17:25 2004 (==) Using config file: "/etc/X11/XF86Config" (II) [GLX]: Initializing GLX extension Warning: font renderer for ".TTF" already registered at priority 10 Warning: font renderer for ".TTC" already registered at priority 10 Creating menu entries for kdm in /usr/kde/3.2/share/config/kdm/sessions... QImage::convertDepth: Image is a null image QImage::smoothScale: Image is a null image xf86KbdEvents Resource temporarily unavailable
Same effect for me. I use KDE on Gentoo. WIth 3.1.x there was no problem with KDM. But with 3.2.0-beta2 and rc1 I can't use it as it doesn't allow me to log in.
please upgrade to qt 3.3.1 & kde 3.2.1 and report if you still see this. do you see this if you use upstream kdm or is it specific to gentoo? does disabling xkb in XF86Config "cure" the problem? is this problem possibly related to bug #75288? xref: http://bugs.gentoo.org/show_bug.cgi?id=40736
Well, bug #75288 pointed me to the right place: .../share/config/kdm/Xservers was stating that X runs on vt7, but I am using vt10 for the X server. So, after changing the config to vt10, the problem went away, kdm runs again. For me, the problem is solved. Maybe you should change/add code for parsing the inittab as you stated over at bug #75288...
*** This bug has been marked as a duplicate of 75288 ***