#4066 NORM Never A: connecting a network breaks sugar or X

[Zarro Boogs per Child]

#4066: connecting a network breaks sugar or X
----------------------------+-----------------------------------------------
  Reporter:  AlbertCahalan  |       Owner:  jg                               
      Type:  defect         |      Status:  new                              
  Priority:  normal         |   Milestone:  Never Assigned                   
 Component:  distro         |     Version:  Development build as of this date
Resolution:                 |    Keywords:                                   
  Verified:  1              |  
----------------------------+-----------------------------------------------
Changes (by vorburger):

  * version:  => Development build as of this date
  * verified:  0 => 1


Comment:

 Confirming / verified this, in a different context:

 Also with Build 613, if for some reason eth0 is not up / has no IP
 assigned, then Sugar/X keeps attempting to start and fail each time, and
 loops - much faster than every minute for me - like continuously,
 graphical mode with X comes up, then goes away and console with errors
 shows, then tries again... ongoing.  The 'looping' goes on for a while
 (100% CPU) and then something smart in Linux says something to the effect
 of "giving up starting X" and you get a console.

 I got this on a qemu on Windows (where I 'forgot' to specify "-net user
 -net nic,model=rtl8139" as startup parameter), but maybe the same happens
 on a real HW XO if the network is not initialized (unverified) ?

 http://www.vorburger.ch/olpc/screenshots/build613-20071004_0142-startup-
 failure-loop-console-screenshot.png is a screenshot I managed to take at
 the right moment (it disappears and comes and goes - looping X start).  I
 am NOT qualified to diagnose if what is on that screenshot ("(sugar-
 shell:3725): CRITICAL: _wrap_gst_mixer_list_tracks: assertion
 'GST_IS_MIXER (self->obj)' failed") is actually the real cause, but I
 thought it was worth mentioning here.

 The http://wiki.laptop.org/go/Autoreinstallation_image at the time of
 writing this reads "There are a couple of reports of problems upgrading to
 the current q2c28 and 613." - I have no idea if that is related to this??

 PS: Just to avoid any confusion, I want to make it clear that qemu
 emulation and networking DOES work out of the box if you follow the
 instructions on the Wiki (I already updated them to make setting the "-net
 user -net nic,model=rtl8139" etc. parameters clearer).  This comment is
 added in response to devel mailing list feedback.

 PPS: Component "Sugar" more appropriate?  (Not "x window sytem", or is
 it?)

-- 
Ticket URL: <https://dev.laptop.org/ticket/4066#comment:1>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system