On an install from the Dual CD the default desktop in the login manager is not LXDE which is the only desktop installed so login fails until LXDE is chosen.
Works fine here, have you chose something special in the install ?
Keywords: (none) => NEEDINFOComponent: Installer => RPM PackagesSource RPM: (none) => lxdm
I just did another install. Used Custom partitioning as I'm installing to USB drive. Chose my language, Canadian English. Changed my time zone to PST in the summery screen. I left every thing else default but login still fails until I change the Desktop to LXDE from Default.
I'm not able to reproduce this. In LXDM for me it shows Desktop:Default Language:Default then logs me in to LXDE. Could it be that your keyboard has not been correctly set in LXDM, so typing your password is actually entering incorrect letters? Could you try with a very simple password. What keyboard settings do you use btw? I'll test here too.
I've now done 6+ installs. I've verified the ISO. I've put it on a flash drive. No way I know of to verify this. I've burnt it to a CD and verified. I've installed using two different computers, a desktop and a laptop both with AMD 64bit processors. I've installed 32bit systems and 64bit systems. In all cases choosing a user while the Desktop is set to Default results in LXDM disappearing, a busy cursor for a few seconds then LXDM reappearing. If I change Default to LXDE, Openbox or drak3d they open as expected so it's not a keyboard/password problem. I've also tried installing task-kde and after that Default opened with a KDE desktop.
ok, have you errors in the syslog ? in the ~./.xsession-errors (or .xsession-errors.old)
I'm not sure if this should be closed or not. The bug appears to only happen when using an old /home partition and user even though the old system was not using LXDM as the display manager.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0Whiteboard: (none) => 3alpha1
no more valid
Status: UNCONFIRMED => RESOLVEDResolution: (none) => WORKSFORME
(In reply to Manuel Hiebel from comment #7) > no more valid Do you mean you've tested or that no one else has reported this?
I have tested. and in fact if you have already a conf file, but not corresponding packages for them, something will be broken anyway.