Sugar

A product of the OLPC initiative, Sugar is a Desktop Environment akin to KDE and GNOME, but geared towards children and education.

Related articles

Sugar has a special Taxonomy to name the parts of its system. The graphical interface itself constitute the Glucose group. This is the core system can reasonably expect to be present when installing Sugar. But to really use the environment, you need activities (some sort of applications). Base activities are part of Fructose. Then, Sucrose is constituted by both Glucose and Fructose and represents what should be distributed as a basic sugar desktop environment. Extra activities are part of Honey. Note that Ribose (the underlaying operating system) is here replaced by Arch.

Installation
  • For the core system (Glucose), install sugar. It provides the graphical interface and a desktop session, but not very useful on its own.
  • The sugar-fructose group contains the base activities (Fructose) including a web browser, a text editor, a media player and a terminal emulator.
  • The sugar-runner package provides a helper script that makes it possible to launch Sugar within another desktop environment, or from the command line directly.

From Activity Library

The Sugar Activity Library provides many Activity Bundles packaged as zip files with the .xo extension. These bundles can be downloaded and installed to the user's directory from Sugar, but the installation does not ensure that the dependencies are satisfied. Therefore it is not the recommended way to install activities, because they likely fail to start due missing dependencies. Commonly used dependencies:

In order to check why the activity fails to start, look at the log file located at ~/.sugar/default/logs/app_id-1.log.

Starting Sugar

Sugar can be started either graphically, using a display manager, or manually from the console.

Graphically

Select the session Sugar from the display manager's session menu.

Manually

If sugar-runner installed, Sugar can be launched with the sugar-runner command.

Alternative method is to add exec sugar to the file. After that, Sugar can be launched with the command (see xinitrc for additional details). After setting up the file, it can also be arranged to Start X at login.

gollark: GPUs are mostly useful for parallel computing tasks of some kind. Of course, yours is probably worse than the CPU in your... laptop or whatever, I assume you have one.
gollark: Roughly.
gollark: The unusedosmarksGPU™ can do 2TFLOP/s of compute and probably cause some kind of power supply issue because it's PCIe-powered, and thus shares its electricity with the HDD controller card.
gollark: Your GPU is far inferior to the unusedosmarksGPU™.
gollark: My server's GPU is far too underutilized.

See also
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.