Strange, since yesterday updates the system stays in text mode, without even login console. Beta2 x86_64 KDE install. I just configured automatic login in MCC. Pressing ALT+F7 starts X session.
>Pressing ALT+F7 starts X session. Do you mean that the DM service actually does not start until you press ALT-F7 (which would be really strange) or that it starts on tty7 but doesn't switch to tty7 automatically, and you have to do it yourself to see the DM prompt ?
CC: (none) => ftg
> it starts on tty7 but doesn't switch to tty7 automatically, and you have to do it yourself to see the DM prompt ? I think this is what I get. And I thought we had now DM in ALT-F1?
It depends on the state of affairs at the time beta2 was cut. It's been my experience that current cauldron systems which are not recent fresh installs but have been upgraded with --auto-select over time still use tty7 and exhibit other oddities. But I would have expected beta2 to use tty1 as well.
I've run into a case that may be related. In one install, I'm using kdm with autologin. On a normal boot, it does start kde on tty1. If I add the option rd.break=pre-udev, and just enter 'exit' at each shell, kde starts up, but it is on tty7. In my case, it does switch, so I don't have to press the alt+ctrl+f7, but it is confusing if I use alt+ctrl+f12 to look at the syslog entries, and then try to get back to kde.
CC: (none) => davidwhodgins
It did not happen anymore for 2 weeks.
Status: NEW => RESOLVEDResolution: (none) => FIXED