That's the same SoaS I tried. Didn't happen for me.

Art Hunkins
  ----- Original Message ----- 
  From: Bert Freudenberg 
  To: Development of live Sugar distributions 
  Cc: sugar-devel Devel 
  Sent: Monday, June 13, 2011 1:39 PM
  Subject: Re: [Sugar-devel] Strawberry - login screen




  On 13.06.2011, at 10:35, Peter Robinson wrote:





    On Mon, Jun 13, 2011 at 6:23 PM, Bert Freudenberg <[email protected]> 
wrote:



      On 13.06.2011, at 06:50, Peter Robinson wrote:





        On Mon, Jun 13, 2011 at 2:38 PM, Esteban Arias 
<[email protected]> wrote:

          hi!

          do you know why sugar on stick - SoaS release 1 (Strawberry), shows 
login when I change configuration from control panel ?
          for example, I change nike name in "About me"; then restart with 
login screen...

          I put "liveuser" and the system starts ok!

          It is possible to dont show login screen?


        You can change settings in the gdm.conf file


      It would be nice if SoaS would not show the GDM login screen at all, just 
like on the XO. This still happens in SoaS v5. 

    Have you tested the new images I posted yesterday? It shouldn't on those. 


  Yes, it happens in SoaSv5-20110612-i686.iso.


    Getting rid of it all together has pros and cons and I've not seen patches, 
or even suggestions for that matter, from anyone for the best way to address 
this issue to also allow multiple UX and users.
     
        and it needs a blank password. 


      When doing a liveinst it does not accept a blank password.


    Doesn't stop you from removing it later.



  Doesn't stop me, true, but stops teachers and other "normal" users.


  - Bert -




------------------------------------------------------------------------------


  _______________________________________________
  Sugar-devel mailing list
  [email protected]
  http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
SoaS mailing list
[email protected]
http://lists.sugarlabs.org/listinfo/soas

Reply via email to