Development Team/Jhbuild: Difference between revisions

Line 116:

Note that due to a [https://bugs.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap <keymap name></code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended. The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.

== Running sugar in a VNC session ==

Many users and developers have reported problems with running sugar-emulator, which uses Xephyr. As an alternatice, you can run sugar inside a VNC session. To accomplish this, install a complete set of VNC packages (both server and client) and create a <code>~/.vnc/xstartup</code> file containing the code below:

#!/bin/sh

exec ~/sugar-jhbuild/sugar-jhbuild run dbus-launch --exit-with-session sugar

Now, you may run Sugar by creating a VNC session and accessing it using a VNC viewer. E.g.:

vncserver :1

vncviewer :1

== Run an individual activity ==

Line 133:

Line 144:

The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).

~~== Running sugar in a VNC session ==~~

Many users and developers have reported problems with running sugar-emulator, which uses Xephyr. As an alternatice, you can run sugar inside a VNC session. To accomplish this, install a complete set of VNC packages (both server and client) and create a <code>~/.vnc/xstartup</code> file containing the code below:

~~#!/bin/sh~~

~~exec ~/sugar-jhbuild/sugar-jhbuild run dbus-launch --exit-with-session sugar~~

~~Now, you may run Sugar by creating a VNC session and accessing it using a VNC viewer. E.g.:~~

~~vncserver :1~~

~~vncviewer :1~~

== Other commands ==

@@ Line 116: / Line 116: @@
 Note that due to a [https://bugs.sugarlabs.org/ticket/342 bug in Xephyr] your keyboard might not work as expected. A partial workaround is to run <code>setxkbmap &lt;keymap name&gt;</code> by adding this command line to <code>~/.sugar/debug</code>. Most "regular" keys should work fine after that, some "special keys" (e.g. cursor up/down) might still refuse to operate as intended.  The "keymap name" usually is a two letter country code, e.g. "de" for german or "fr" for french.
+== Running sugar in a VNC session ==
+Many users and developers have reported problems with running sugar-emulator, which uses Xephyr. As an alternatice, you can run sugar inside a VNC session. To accomplish this, install a complete set of VNC packages (both server and client)  and create a <code>~/.vnc/xstartup</code> file containing the code below:
+ #!/bin/sh
+ exec ~/sugar-jhbuild/sugar-jhbuild run dbus-launch --exit-with-session sugar
+Now, you may run Sugar by creating a VNC session and accessing it using a VNC viewer. E.g.:
+ vncserver :1
+ vncviewer :1
 == Run an individual activity ==
@@ Line 133: / Line 144: @@
 The default size of 800x600 is currently the minimum that should work without issues. I.e. activities should be tested to work in this mode (and in others as well).
-== Running sugar in a VNC session ==
-Many users and developers have reported problems with running sugar-emulator, which uses Xephyr. As an alternatice, you can run sugar inside a VNC session. To accomplish this, install a complete set of VNC packages (both server and client)  and create a <code>~/.vnc/xstartup</code> file containing the code below:
- #!/bin/sh
- exec ~/sugar-jhbuild/sugar-jhbuild run dbus-launch --exit-with-session sugar
-Now, you may run Sugar by creating a VNC session and accessing it using a VNC viewer. E.g.:
- vncserver :1
- vncviewer :1
 == Other commands ==