Re: [Sugar-devel] Problems starting the XO
On Tue, Sep 4, 2012 at 3:38 PM, Ajay Garg wrote: > May be this could be improved sometime in the future :) Fix the packaging, and don't use --force. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
> > > Wouldn't of made a difference, sugar requires sugar-toolkit but doesn't > state a minimum version level of the toolkit to enforce. > > In this case is a packaging problem, but forcing rpm to ignore the errors is not a good idea, at least you know what are doing. Gonzalo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
On Tue, 2012-09-04 at 12:50 -0300, Gonzalo Odiard wrote: > The error was from your part, when did "rpm --force --nodeps" > You should not do this. > > Wouldn't of made a difference, sugar requires sugar-toolkit but doesn't state a minimum version level of the toolkit to enforce. Jerry > Gonzalo > > On Tue, Sep 4, 2012 at 12:38 PM, Ajay Garg > wrote: > Yup, I had the missing updated "sugar-toolkit" package. > > But I have to say, that there wasn't any hint of any error-log > anywhere :-\ > May be this could be improved sometime in the future :) > > > Thanks Jerry, Gonzalo and Ruben. > > > Thanks and Regards, > Ajay > > > > > On Sun, Sep 2, 2012 at 9:38 AM, Gonzalo Odiard > wrote: > I don't know what rpms are you using in dx, > but if you want use the last code in sugar, should > update sugar-toolkit too. > > > yum update sugar > > > should be a better option. > > > Gonzalo > > > On Sun, Sep 2, 2012 at 12:19 AM, Ajay Garg > wrote: > Also, for brevity, I am attaching the python > files of the culprit "src/jarabe/journal" > folder, as this could help in reproducing the > issue. > > I am sorry for bothering everyone on the > weekend; but this does not seem to show any > hints of the solution to the path :-\ > > > Regards, > Ajay > > > > > On Sat, Sep 1, 2012 at 11:44 PM, Ajay Garg > wrote: > Hi Martin. > > Thanks for the reply. > > On Sat, Sep 1, 2012 at 11:12 PM, > Martin Langhoff > wrote: > On Sat, Sep 1, 2012 at 4:25 > PM, Ajay Garg > > wrote: > > Thanks Chris and Mikus for > the replies. > > > Hi Ajay, > > please ansert cjb's question. > It has a good chance of > leading to your > answer. What deps are you > ignoring? Why --force? > > I am sorry I did not give the full > info :( > Usually, for "development" testing, I > use this method, as long as only > "sugar" changes are involved. > > When I first came across the issue, I > followed the normal way, and installed > the "sugar-control-frame" and > "sugar-control-accessibility" packages > too (dependencies of "sugar"). I > installed all the three packages > without "--force" then. > > However, there came to be no > difference in behaviour (as long as > XO-boot was concerned). :( > > > > > > > Also -- /var/log/olpc-dm* logs > are likely to have important > info. > Please post them. > > >
Re: [Sugar-devel] Problems starting the XO
The error was from your part, when did "rpm --force --nodeps" You should not do this. Gonzalo On Tue, Sep 4, 2012 at 12:38 PM, Ajay Garg wrote: > Yup, I had the missing updated "sugar-toolkit" package. > > But I have to say, that there wasn't any hint of any error-log anywhere > :-\ > May be this could be improved sometime in the future :) > > > Thanks Jerry, Gonzalo and Ruben. > > > Thanks and Regards, > Ajay > > > > > On Sun, Sep 2, 2012 at 9:38 AM, Gonzalo Odiard wrote: > >> I don't know what rpms are you using in dx, >> but if you want use the last code in sugar, should update sugar-toolkit >> too. >> >> yum update sugar >> >> should be a better option. >> >> Gonzalo >> >> >> On Sun, Sep 2, 2012 at 12:19 AM, Ajay Garg wrote: >> >>> Also, for brevity, I am attaching the python files of the culprit >>> "src/jarabe/journal" folder, as this could help in reproducing the issue. >>> >>> I am sorry for bothering everyone on the weekend; but this does not seem >>> to show any hints of the solution to the path :-\ >>> >>> >>> Regards, >>> Ajay >>> >>> >>> >>> >>> On Sat, Sep 1, 2012 at 11:44 PM, Ajay Garg wrote: >>> Hi Martin. Thanks for the reply. On Sat, Sep 1, 2012 at 11:12 PM, Martin Langhoff < martin.langh...@gmail.com> wrote: > On Sat, Sep 1, 2012 at 4:25 PM, Ajay Garg > wrote: > > Thanks Chris and Mikus for the replies. > > Hi Ajay, > > please ansert cjb's question. It has a good chance of leading to your > answer. What deps are you ignoring? Why --force? > I am sorry I did not give the full info :( Usually, for "development" testing, I use this method, as long as only "sugar" changes are involved. When I first came across the issue, I followed the normal way, and installed the "sugar-control-frame" and "sugar-control-accessibility" packages too (dependencies of "sugar"). I installed all the three packages without "--force" then. However, there came to be no difference in behaviour (as long as XO-boot was concerned). :( > > Also -- /var/log/olpc-dm* logs are likely to have important info. > Please post them. > Please find attached the entire "/var/log/" directory, of the "failed-to-launch-X-server" boot on the XO-1. Note that the names of the files are capitalized and shortened - it so happened when I copied the "var/log/" directory onto my pen-drive, from the shell login on the XO. Thanks and Regards, Ajay > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- Software Architect - OLPC > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > >>> >>> ___ >>> Devel mailing list >>> Devel@lists.laptop.org >>> http://lists.laptop.org/listinfo/devel >>> >>> >> > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
Yup, I had the missing updated "sugar-toolkit" package. But I have to say, that there wasn't any hint of any error-log anywhere :-\ May be this could be improved sometime in the future :) Thanks Jerry, Gonzalo and Ruben. Thanks and Regards, Ajay On Sun, Sep 2, 2012 at 9:38 AM, Gonzalo Odiard wrote: > I don't know what rpms are you using in dx, > but if you want use the last code in sugar, should update sugar-toolkit > too. > > yum update sugar > > should be a better option. > > Gonzalo > > > On Sun, Sep 2, 2012 at 12:19 AM, Ajay Garg wrote: > >> Also, for brevity, I am attaching the python files of the culprit >> "src/jarabe/journal" folder, as this could help in reproducing the issue. >> >> I am sorry for bothering everyone on the weekend; but this does not seem >> to show any hints of the solution to the path :-\ >> >> >> Regards, >> Ajay >> >> >> >> >> On Sat, Sep 1, 2012 at 11:44 PM, Ajay Garg wrote: >> >>> Hi Martin. >>> >>> Thanks for the reply. >>> >>> On Sat, Sep 1, 2012 at 11:12 PM, Martin Langhoff < >>> martin.langh...@gmail.com> wrote: >>> On Sat, Sep 1, 2012 at 4:25 PM, Ajay Garg wrote: > Thanks Chris and Mikus for the replies. Hi Ajay, please ansert cjb's question. It has a good chance of leading to your answer. What deps are you ignoring? Why --force? >>> >>> I am sorry I did not give the full info :( >>> Usually, for "development" testing, I use this method, as long as only >>> "sugar" changes are involved. >>> >>> When I first came across the issue, I followed the normal way, and >>> installed the "sugar-control-frame" and "sugar-control-accessibility" >>> packages too (dependencies of "sugar"). I installed all the three packages >>> without "--force" then. >>> >>> However, there came to be no difference in behaviour (as long as XO-boot >>> was concerned). :( >>> >>> >>> >>> >>> Also -- /var/log/olpc-dm* logs are likely to have important info. Please post them. >>> >>> >>> Please find attached the entire "/var/log/" directory, of the >>> "failed-to-launch-X-server" boot on the XO-1. >>> >>> Note that the names of the files are capitalized and shortened - it so >>> happened when I copied the "var/log/" directory onto my pen-drive, from >>> the shell login on the XO. >>> >>> >>> Thanks and Regards, >>> Ajay >>> >>> >>> >>> >>> m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel >>> >>> >> >> ___ >> Devel mailing list >> Devel@lists.laptop.org >> http://lists.laptop.org/listinfo/devel >> >> > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
I don't know what rpms are you using in dx, but if you want use the last code in sugar, should update sugar-toolkit too. yum update sugar should be a better option. Gonzalo On Sun, Sep 2, 2012 at 12:19 AM, Ajay Garg wrote: > Also, for brevity, I am attaching the python files of the culprit > "src/jarabe/journal" folder, as this could help in reproducing the issue. > > I am sorry for bothering everyone on the weekend; but this does not seem > to show any hints of the solution to the path :-\ > > > Regards, > Ajay > > > > > On Sat, Sep 1, 2012 at 11:44 PM, Ajay Garg wrote: > >> Hi Martin. >> >> Thanks for the reply. >> >> On Sat, Sep 1, 2012 at 11:12 PM, Martin Langhoff < >> martin.langh...@gmail.com> wrote: >> >>> On Sat, Sep 1, 2012 at 4:25 PM, Ajay Garg >>> wrote: >>> > Thanks Chris and Mikus for the replies. >>> >>> Hi Ajay, >>> >>> please ansert cjb's question. It has a good chance of leading to your >>> answer. What deps are you ignoring? Why --force? >>> >> >> I am sorry I did not give the full info :( >> Usually, for "development" testing, I use this method, as long as only >> "sugar" changes are involved. >> >> When I first came across the issue, I followed the normal way, and >> installed the "sugar-control-frame" and "sugar-control-accessibility" >> packages too (dependencies of "sugar"). I installed all the three packages >> without "--force" then. >> >> However, there came to be no difference in behaviour (as long as XO-boot >> was concerned). :( >> >> >> >> >> >>> >>> Also -- /var/log/olpc-dm* logs are likely to have important info. >>> Please post them. >>> >> >> >> Please find attached the entire "/var/log/" directory, of the >> "failed-to-launch-X-server" boot on the XO-1. >> >> Note that the names of the files are capitalized and shortened - it so >> happened when I copied the "var/log/" directory onto my pen-drive, from >> the shell login on the XO. >> >> >> Thanks and Regards, >> Ajay >> >> >> >> >> >>> >>> m >>> -- >>> martin.langh...@gmail.com >>> mar...@laptop.org -- Software Architect - OLPC >>> - ask interesting questions >>> - don't get distracted with shiny stuff - working code first >>> - http://wiki.laptop.org/go/User:Martinlanghoff >>> ___ >>> Devel mailing list >>> Devel@lists.laptop.org >>> http://lists.laptop.org/listinfo/devel >>> >> >> > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
On Sat, Sep 1, 2012 at 4:25 PM, Ajay Garg wrote: > Thanks Chris and Mikus for the replies. Hi Ajay, please ansert cjb's question. It has a good chance of leading to your answer. What deps are you ignoring? Why --force? Also -- /var/log/olpc-dm* logs are likely to have important info. Please post them. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
Thanks Chris and Mikus for the replies. Well, I seem to have close down on the cause; but not close enough :( The solution is still not in sight. I have been making some changes in the sugar-code, to have the "Transfer to Many" feature working. Things work fine on sugar-emulator; however, when I replace the files in "src/jarabe/journal" folder on the XO, I fail to get the XO booting. Now, the code is fairly big in amount; and it will take many days to pin-point the issue (without any "log" info). But one thing is sure, only when the files in "src/jarabe/journal" are updated, does the XO fail to boot. I tried one thing - I removed the directory "/home/olpc/.sugar", and rebooted, but the XO still failed to boot. One thing I did notice, is that on reboot, the directory "/home/olpc/.sugar" gets re-created, with the journal re-indexed info; but unfortunately, there still is NO "/home/olpc/.sugar/default/shell.log" :( So, answers to the following two queries will help in nailing the issue :: a) Is it possible to (temporarily) stop the re-indexing of the journal on reboot? If yes, that could give some hints as to if this is where the problem occurs. b) Better still, is it possible to have "shell.log" created as the first file after the directory "/home/sugar/.sugar" is created? Any further help will be highly appreciated :) Thanks and Regards, Ajay On Sat, Sep 1, 2012 at 5:15 PM, Mikus Grinbergs wrote: > On 09/01/2012 12:21 AM, Gonzalo Odiard wrote: > >> Sep 1 04:47:41 xo-05-2a-1f kernel: [ 104.561223] init: prefdm respawning >> too ffast, stopped >> > > I can't help you - but I've run into such a situation before. > > X (the display) is crashing - and is being automatically restarted, only > to crash again (and again, and again. and ...). I used to know how to stop > these automatic restarts by commenting out something in /etc -- but things > have changed an I don't know any longer. > > You being able to capture /var/log/messages implies that these automatic > restarts were NOT interfering with you looking at the system. [And it > implies to me that you might manually "patch" kernel files to correct > whatever is causing the crash.] > > > What you did capture does not show the actual problem. You will need to > do additional looking - for instance, /var/log/Xorg.0.log and > /home/olpc/.sugar/default/**logs/shell.log Perhaps capture 'dmesg' > > > Wish you luck, mikus > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
Hi Gonzalo. Thanks for the reply. On Sat, Sep 1, 2012 at 10:51 AM, Gonzalo Odiard wrote: > Any information in shell.log? Nothing. That file does not even exist. The only file in "/home/olpc/.sugar/default/logs/" is "datastore.log", but it is empty :-\ Thanks again. Regards, Ajay > Gonzalo > > On Sat, Sep 1, 2012 at 1:57 AM, 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" >> >> >> 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 >> >> >> >> >> ___ >> Sugar-devel mailing list >> sugar-de...@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Problems starting the XO
Any information in shell.log? Gonzalo On Sat, Sep 1, 2012 at 1:57 AM, 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" > > > 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 > > > > > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
