Description of problem: SoaS live x86_64 20150706 does not login from live system user Version-Release number of selected component (if applicable): Fedora SoaS live x86_64 rawhide 20150706 How reproducible: Steps to Reproduce: 1.boot live cd 2.login screen appears 3.try to login with blank password Actual results: login as Live System User from blank password crashes x? and restarts login screen. Expected results: start sugar (normal) or at least allow login as Live System User from blank password Additional info: Get a crash? after user attempts to login; restarts login screen. Does the kickstart file need adjusting?
Proposed as a Freeze Exception for 23-alpha by Fedora user satellit using the blocker tracking app because: non-blocking spin does not start; unable to install
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Discussed at today's blocker review meeting [1]. This bug was accepted as Alpha Freeze Exception - Since this affects a non-blocking DE, we'd consider a fix during Alpha freeze. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2015-08-03/
Still does not login in f23 soas Alpha torrent download
Proposed as a Freeze Exception for 23-final by Fedora user satellit using the blocker tracking app because: non-blocking desktop
Created attachment 1069020 [details] errors that may cause f23-soas crash errors that may cause f23-soas crash from peter robinson
https://bugzilla.redhat.com/show_bug.cgi?id=1240147#c9 SugarExt can not be loaded properly, blocking Sugar startup
Proposed as a Freeze Exception for 23-beta by Fedora user satellit using the blocker tracking app because: non-blocking DE will not login live user
*** This bug has been marked as a duplicate of bug 1240147 ***