<div class="gmail_quote">On Sat, Sep 1, 2012 at 11:53 PM, Jerry Vonau <<a href="mailto:jvonau@shaw.ca" target="_blank">jvonau@shaw.ca</a>> wrote: <blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div class="im">On Sat, 2012-09-01 at 10:27 +0530, Ajay Garg wrote: > Hi all. > > I flashed an image on an XO-1, after building it from osbuilder; and > booted the machine. The process went fine. > > Therafter, I upgraded the "sugar" package, via > "sudo rpm > --force --nodeps --upgrade sugar-0.94.1-31.dx3.rpm" > > </div>Why didn't you just build the image with the new rpm?</blockquote><div> Well, the code changes need to be tested on an XO first (as I said, that things work fine on the sugar-emulator). Only after the testing is passed on the XO, would the changes be comitted, (fresh) rpms generated to the repos, which would then be pulled into the image built from osbuilder. If there is a way to pull the rpms directly into the image, I will be more than happy to do it. Please let me know if you have ideas regarding this :) </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Anyway, I got burnt building a test image with the latest DX3 rpms, you introduced a change in sugar that requires a newer version of sugar-toolkit but sugar's "rpm Requires:" are not set in to enforce a minimum version of sugar-toolkit. </blockquote><div> Hmm.. my bad. But * I guess sugar-toolkit (latest version) is also present in the repos, which should have been pulled. * I think this is not the cause of the problem I am facing. Thanks and Regards, Ajay </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Jerry <div class="HOEnZb"><div class="h5"> > > After that, when I reboot, the sugar-session does not start :-\ > > > I have > > * looked at "/var/log/messages", but nothing sugar specific logs > are there. > * tried out with the serial debugger; nothing specific here too. > > > > For brevity, here are the last few logs of /var/log/messages :: > > #################################################################### > Sep 1 04:47:04 xo-05-2a-1f kernel: [ 67.336082] dcon_freeze_store: > 0 > Sep 1 04:47:11 xo-05-2a-1f kernel: [ 74.967408] init: prefdm main > process endd > ed, respawning > Sep 1 04:47:12 xo-05-2a-1f kernel: [ 75.065137] dcon_freeze_store: > 0 > Sep 1 04:47:16 xo-05-2a-1f rtkit-daemon[1026]: Successfully made > thread 1295 off > process 1295 (/usr/bin/pulseaudio) owned by '500' high priority at > nice level -- > 11. > Sep 1 04:47:26 xo-05-2a-1f kernel: [ 89.818075] init: prefdm main > process endd > ed, respawning > Sep 1 04:47:26 xo-05-2a-1f kernel: [ 89.890318] dcon_freeze_store: > 0 > Sep 1 04:47:31 xo-05-2a-1f rtkit-daemon[1026]: Successfully made > thread 1425 off > process 1425 (/usr/bin/pulseaudio) owned by '500' high priority at > nice level -- > 11. > Sep 1 04:47:41 xo-05-2a-1f kernel: [ 104.561223] init: prefdm > respawning too ff > ast, stopped > Sep 1 04:47:41 xo-05-2a-1f kernel: [ 104.638658] dcon_freeze_store: > 0 > #################################################################### > > > > Any ideas, as to where I can catch the point of failure? > > > I will be grateful for any help. > > > Thanks and Regards, > Ajay > > > </div></div><div class="HOEnZb"><div class="h5">> _______________________________________________ > Devel mailing list > <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a> > <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a> </div></div></blockquote></div>