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 <[email protected]> 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 <[email protected]> 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 <[email protected]>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 <[email protected]>wrote: >>> >>>> Hi Martin. >>>> >>>> Thanks for the reply. >>>> >>>> On Sat, Sep 1, 2012 at 11:12 PM, Martin Langhoff < >>>> [email protected]> wrote: >>>> >>>>> On Sat, Sep 1, 2012 at 4:25 PM, Ajay Garg <[email protected]> >>>>> 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 >>>>> -- >>>>> [email protected] >>>>> [email protected] -- 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 >>>>> [email protected] >>>>> http://lists.laptop.org/listinfo/devel >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> Devel mailing list >>> [email protected] >>> http://lists.laptop.org/listinfo/devel >>> >>> >> >
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
