/usr/bin/sugar does not exit if window is closed

[quozl]

Running /usr/bin/sugar from a GNOME Terminal under X11 is not something we had planned, but if it is done and the window is closed, Sugar does not exit.

[sarthak0527]

I would like to work on this issue.

[chimosky]

@sarthak0527 feel free to open a PR when you have one.

[sarthak0527]

I'm new to open source , could you guide me how can I solve this issue ?

[quozl]

Not really, if we knew how to solve the issue we would just go ahead and do so.

[chimosky]

@sarthak0527 a great place to start would be reproducing the issue, you'll have to run it from GNOME though.
You'll need to have sugar installed before you run the command above in your terminal.

[sarthak0527]

@chimosky I have installed the sugar . Now what should I do next?

[quozl]

The issue is;

Running /usr/bin/sugar from a GNOME Terminal is not something we had planned, but if it is done and the window is closed, Sugar does not exit.

Have you run GNOME Terminal?

When GNOME Terminal is running, have you run /usr/bin/sugar?

When the Sugar window is closed, what do you observe about the Sugar process?

[sarthak0527]

I did run GNOME Terminal.

After running /usr/bin/sugar , it is running but in system monitor it is not showing .

Also when the sugar window is closed ,I oberserve nothing about the process.

[quozl]

System monitor does not show all processes. The shell command sudo ps ax may be helpful for listing all processes.

When you say you observe nothing about the process, what do you mean? Does the process exit, or is it still running as described in this issue? You have to be familiar with Linux process creation and termination to be able to detect this issue.

[solo-daemon]

@quozl i would like to work on this

[quozl]

My commiserations to you. Good luck!

[DaffyTheDuck]

Hi there! May I know what was the expected output ?

[quozl]

/usr/bin/sugar is a shell script derived from bin/sugar.in, and generates quite a lot of output in various places. The output it generates is not the concern in this issue, it is that the processes run by the shell script do not terminate when an enclosing GNOME Terminal is closed.

[DaffyTheDuck]

/usr/bin/sugar is a shell script derived from bin/sugar.in, and generates quite a lot of output in various places. The output it generates is not the concern in this issue, it is that the processes run by the shell script do not terminate when an enclosing GNOME Terminal is closed.

Hmm! as I ran this command in my terminal, I noticed that it changed my cursor style and replaced it with the one in sugar environment, also in the output of ps ax I see no process of sugar running. Also it keeps the cursor in the same way even the terminal is closed! as i've little experience in linux and it's processes, i would love it if you enlighten me more on this 😄

[quozl]

Yes, that's right.

Sugar was never intended to be run from any terminal, but rather as an X windows session manager, or the .xsession file. Sugar does work properly when run in that way.

All logs are kept in .sugar/default/logs and that's where you can look for an explanation of why Sugar terminated early.

Changing cursor is one of the steps of Sugar startup (src/jarab/main.py search for cursor-theme), and there is code to put it back the way it was if Sugar is exited normally.

So given your description I'd say Sugar failed to start, and the explanation will be in the logs. That isn't what happened in this issue though.