Issue with display Manager about sugar HOT 7 OPEN

What installation instructions did you follow?

from sugar.

@chimosky I followed the installation instructions for ubuntu and then after that building the packaged sugar by running autogen.sh and then make , further make install.

from sugar.

The ubuntu instructions I'm looking at don't tell you to run autogen.sh, make and make install.

from sugar.

@chimosky so pls suggests how can I undo that. Even I felt that by doing this I made a mistake. What should I do now ? Any recommendations pls .

from sugar.

@chimosky so pls suggests how can I undo that. Even I felt that by doing this I made a mistake. What should I do now ? Any recommendations pls .

Could you tell me exactly what you did in detail? Also link the instructions you followed.

from sugar.

@chimosky what i did was
Firstly I followed Installation Instructions for Ubuntu
After that everything was working fine I could log in to the sugar as well get out of it and log in to ubuntu
Next what i did was
I tried running these 3 instructions
autogen.sh, then make and make install. referring to this
There I tried running autogen.sh where I ran into errors on terminal many a times . But later after updating contents of configure.ac and updating aclocal I executed the remaining two .
but after doing this when I logged into the sugar it showed me the window as shown in ss which I have discussed above

Kindly help me out. I am fixing it up from past two days but to no results

from sugar.

Interesting. You first installed Sugar successfully using our instructions, which installs pre-built package provided by Ubuntu, then you decided to build Sugar from source on top of that. I'm not surprised it broke, because it is very hard to exactly reproduce what Ubuntu had done for you, especially if you mix pre-built package files with files built from source.

Now, log in using another session type or SSH rather than Sugar, and closely examine the .sugar/default/logs directory to see what Sugar has recorded as the reason why it did not start. If that doesn't help, then you will have to debug the X session startup, which requires knowledge of Xorg and how it works. That's outside the scope of Sugar. Tools like debuggers, process lists, strace, and so forth would be deployed. It is not the sort of thing that can be easily transferred from us using a GitHub issue.

from sugar.