Red Hat Bugzilla – Bug 1004421
f20 SoaS TC3 uses gdm which defaults to gnome. Autologon starts gnome with no chance to choose sugar-desktop
Last modified: 2013-10-02 03:09:12 EDT
Description of problem:f20 SoaS TC3 uses gdm which defaults to gnome. Autologon starts gnome with no chance to choose sugar-desktop. gdm works properly once alt f2 root liveinst is used. This is because there is now a user to login.
See Bz 997478
sugar-emulator is no longer in f20 to be replaced with sugar-runner (not yet packaged) thus sugar is not present in gnome-desktop
Version-Release number of selected component (if applicable):
f20 SoaS TC3 x86_64
Steps to Reproduce:
1- select sugar as default desktop in gdm
2- Or do not use autologin
Via a .ks change
Discussed at 2013-09-04 blocker review meeting . This prevents SoaS from booting properly and would be a blocker for a release blocking DE, therefore accepted as a FE for F20 alpha.
This should be fixed in the kickstart files now. Once we have a TC5 or RC1 it should be all fixed.
f20 TC5 SoaS boots to console login
No DE called
requires login as liveuser then startx
I have had also had experience with the problem of wanting to change the desktop environment of the autologin user. I believe system-config-users should have the following added:
1) change the desktop environment, just as the the shell can now be changed,
2) option to suppress appearance of selected users in the user list.
I'm willing to refile if this comment is misplaced.
Install from DVD on F20 Alpha RC2 X86_64 and the ARM image both boot to multiuser, 'startx' fails. logs attached.
Created attachment 797448 [details]
*** This bug has been marked as a duplicate of bug 1008569 ***