Description of problem: SoaS kickstart needs to have lightdm added and -gdm added to kickstart file Version-Release number of selected component (if applicable): Soas f20 Alpha Live x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: SoaS boots to console login https://bugzilla.redhat.com/show_bug.cgi?id=1004421 Expected results: SoaS starts at (Name____) Additional info: http://wiki.sugarlabs.org/go/Fedora_20#SoaS_86_64-dm_.28remix.29 a livecd-tools remix works after these changes. (Downloadable .iso is included in this link)
This also affects the ARM soas images.
http://kojipkgs.fedoraproject.org//work/tasks/2485/5982485/Fedora-20-Nightly-x86_64-Live-soas-20130925.08-1.iso Has fix. boots and installs correctly with anaconda 20-18-1 in Virtualbox ---------- soas.org: (09/24/2013) "Should be fixed in the next nightly, we depended on lightdm-gtk so should have pulled lightdm in (it worked in F-19) but it appears something changed." Peter Robinson
*** Bug 1004421 has been marked as a duplicate of this bug. ***
SoaS-f20-Beta TC-1 x86_64 works but jabber and browse fail to connect to internet "not asking for VNC as no network" (on boot) Anaconda 20-21-1 3.11.2-301
Revision to comment 4 A booted burned CD sees wireless AP's and ad-hoc AP's and connects to Jabber correctly. So it must be a problem in VirtualBox with its bridged networking. Liveinst works fine with CD install to external 320 GB USB HD with reclaim space
SoaS f20 Beta TC1 x86_64 works fine in Boxes in f20 Gnome