[SOLVED] Anyone got OLPC Sugar running?

doragasu · 2014-11-15 19:58:34

I have an old PC I want my 5 year old daughter to use. I'd like to use OLPC Sugar as Desktop Environment.

Right now I have a small arch install with LXDE running in the PC, and I have built a bunch of sugar packages from aur. Instructions in the wiki are a bit confusing and outdated, and I have no idea how to start sugar.

I have figured out I have to use sugar-runner, so I built it, and tried calling it from the terminal (before an X session is started). No luck, an X session starts and immediately exits. Xorg log shows no problems thoug.

Any suggestions?

Last edited by doragasu (2017-02-15 06:22:49)

jasonwryan · 2014-11-15 20:05:00

Moving to AUR Issues...

doragasu · 2014-11-15 20:10:12

A bit more information. Running sugar-runner from a started X session, the screen blacks out for a moment, and then it returns to the LXDE session, showing this error on the console:

Traceback (most recent call last):
  File "/usr/libexec/sugar-runner/xinitrc", line 84, in <module>
    _start_keyring()
  File "/usr/libexec/sugar-runner/xinitrc", line 72, in _start_keyring
    "--components=secrets,pkcs11,ssh,gpg"])
  File "/usr/lib/python2.7/subprocess.py", line 566, in check_output
    process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
xinit: connection to X server lost

waiting for X server to shut down

The same error is also shown when launching sugar-runner from a "pure terminal" (before starting an X session). Also it's not an Xorg error (as I stated before, X shows no errors) but a sugar-runner script one.

Lone_Wolf · 2014-11-16 15:35:03

File "/usr/libexec/sugar-runner/xinitrc", line 84, in <module>
    _start_keyring()
  File "/usr/libexec/sugar-runner/xinitrc", line 72, in _start_keyring
    "--components=secrets,pkcs11,ssh,gpg"])

looks like you may be missing some dependencies.

please run namcap on sugar-runner pkg.tar.xz file and post the output.

It might also be helpful to post the contents of /usr/libexec/sugar-runner/xinitrc .

doragasu · 2014-11-16 15:52:51

How should I exactly invoke namcap? Is this helpful?:

$ namcap -L sugar-runner
-------------------- Namcap rule list --------------------
anyelf              : Check for ELF files to see if a package should be 'any' architecture
array               : Verifies that array variables are actually arrays
badbackups          : Checks for bad backup entries
capsnamespkg        : Verifies package name in package does not include upper case letters
carch               : Verifies that no specific host type is used
checksums           : Verifies checksums are included in a PKGBUILD
directoryname       : Checks for standard directories.
elfexecstack        : Check for executable stacks in ELF files.
elfpaths            : Check about ELF files outside some standard paths.
elftextrel          : Check for text relocations in ELF files.
emptydir            : Warns about empty directories in a package
extravars           : Verifies that extra variables start with an underscore
fhs-infopages       : Verifies correct installation of info pages
fhs-manpages        : Verifies correct installation of man pages
filenames           : Checks for invalid filenames.
fileownership       : Checks file ownership.
giomodules          : Check that GIO modules are registered
glibschemas         : Check that dconf schemas are compiled
gnomemime           : Checks for generated GNOME mime files
hardlinks           : Look for cross-directory/partition hard links
hicoloricons        : Checks whether the hicolor icon cache is updated.
infodirectory       : Checks for info directory file.
infoinstall         : Checks that info files are correctly installed.
invalidstartdir     : Looks for references to $startdir
javafiles           : Check for existence of Java classes or JARs
kdeprograms         : Checks that KDE programs have kdebase-runtime as a dependency
libtool             : Checks for libtool (*.la) files.
license             : Verifies license is included in a PKGBUILD
licensepkg          : Verifies license is included in a package file
lots-of-docs        : See if a package is carrying more documentation than it should
mimedesktop         : Check that MIME associations are updated
mimefiles           : Check for files in /usr/share/mime
missingbackups      : Backup files listed in package should exist
perllocal           : Verifies the absence of perllocal.pod.
permissions         : Checks file permissions.
pkgnameindesc       : Verifies if the package name is included on package description
rpath               : Verifies correct and secure RPATH for files.
rubypaths           : Verifies correct usage of folders by ruby packages
scrollkeeper        : Verifies that there aren't any scrollkeeper directories.
sfurl               : Checks for proper sourceforge URLs
shebangdepends      : Checks dependencies semi-smartly.
sodepends           : Checks dependencies caused by linked shared libraries
splitpkgfunctions   : Checks that all package_* functions exist.
splitpkgmakedeps    : Checks that a split PKGBUILD has enough makedeps.
symlink             : Checks that symlinks point to the right place
tags                : Looks for Maintainer and Contributor comments
urlpkg              : Verifies url is included in a package file

Lone_Wolf · 2014-11-17 13:03:18

https://wiki.archlinux.org/index.php/Na … _to_use_it

namcap *.pkg.tar.xz

doragasu · 2014-11-20 20:00:36

Thanks for help and sorry for the late reply (I'm extremely busy lately). Tried running namcap as you suggested. It reports some stuff, mainly about things in non standard directories, but I don't know if that can cause problems:

$ namcap sugar-runner-0.102.0-1-any.pkg.tar.xz 
sugar-runner W: File (usr/libexec/) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/xephyr-window) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/xinitrc) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/tweak-xwrapper) exists in a non-standard directory.
sugar-runner E: Files in /usr/share/icons/hicolor but no call to gtk-update-icon-cache or xdg-icon-resource to update the icon cache
sugar-runner E: ELF file ('usr/lib/libsugarrunner.so.0.0.0') found in an 'any' package.
sugar-runner W: Dependency python2 included but already satisfied
sugar-runner W: Dependency included and not needed ('sugar-datastore')
sugar-runner W: Dependency included and not needed ('sugar-presence-service')
sugar-runner W: Dependency included and not needed ('sugar')
sugar-runner W: Dependency included and not needed ('xorg-xinit')

Lone_Wolf · 2014-11-21 12:55:49

sugar-runner W: File (usr/libexec/) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/xephyr-window) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/xinitrc) exists in a non-standard directory.
sugar-runner W: File (usr/libexec/sugar-runner/tweak-xwrapper) exists in a non-standard directory.

In the past (like 2+ years back) using /usr/libexec was not uncommon. it's frowned upon now, as everyhting executable should be in /usr/bin instead.
However, authors need to change the sourcecode for that and not all *nixes have changed to /usr/bin yet.

sugar-runner W: Dependency python2 included but already satisfied
sugar-runner W: Dependency included and not needed ('sugar-datastore')
sugar-runner W: Dependency included and not needed ('sugar-presence-service')
sugar-runner W: Dependency included and not needed ('sugar')

namcap often has trouble detecting python dependencies correctly, verify they are needed , if so keep them.

sugar-runner W: Dependency included and not needed ('xorg-xinit')

since sugar-runner uses xinitrc, and that is normally executed by startx , i feel namcap is wrong here (probably bad python script dependency again).

sugar-runner E: Files in /usr/share/icons/hicolor but no call to gtk-update-icon-cache or xdg-icon-resource to update the icon cache

This should be taken care of by a .install file that runs that.
Since it has todo with icons, i doubt it has to do with the problem.

sugar-runner E: ELF file ('usr/lib/libsugarrunner.so.0.0.0') found in an 'any' package.

This means the sugar-runner package has architecture dependent parts, so should use arch=(x86_64 i686) or similar.
------------------------------------------------------

TL:DR : the pkgbuild needs changes, but those probably won't solve the problem.

secrets,pkcs11,ssh,gpg

i'm not sure what package would provide 'secrets' , but the other 3 are much easier.

pcks : pacakge p11-kit
ssh : openssh
gpg : given that this is a python2 program, i suggest python2-pygpgme .

Are those packages present on your system ?

Last edited by Lone_Wolf (2014-11-21 12:56:54)

doragasu · 2014-11-22 17:16:09

Again, thanks a lot for help.

Lone_Wolf wrote:

secrets,pkcs11,ssh,gpg
i'm not sure what package would provide 'secrets' , but the other 3 are much easier.
pcks : pacakge p11-kit
ssh : openssh
gpg : given that this is a python2 program, i suggest python2-pygpgme .

I was only missing openssh, installed it and no luck . Also had installed gnupg (I suspect this matches better than pygame, as it looks like the requirements are cyphers). For secrets, pkgfile command suggests davfs2 package, but I don't think that can help. I have tried it anyway just to make sure and it doesn't work.

I'm suspecting sugar packages are too old and do not work. Right now I have uninstalled sugar-*, and I'm building sugar-*-git to see if it works.

doragasu · 2014-11-22 17:42:42

Built sugar-*-git, and sugar doesn't start, but I think now the error is a bit clearer, it looks like I have a problem with gnome keyring:

$ sugar-runner

Traceback (most recent call last):
  File "/usr/libexec/sugar-runner/xinitrc", line 89, in <module>
    os.kill(int(os.environ["GNOME_KEYRING_PID"]), signal.SIGTERM)
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'GNOME_KEYRING_PID'
xinit: connection to X server lost

waiting for X server to shut down

I think the other problem I had was maybe the same, but now error message is clearer.

I have read here and don't know exactly what to do. I tried starting the keyring using PAM method, but still have the same problem. Maybe I should try installing a login manager such as slim.

doragasu · 2014-11-22 18:36:03

Tried installing gdm, but it didn't work (it starts, and 'systemctl status gdm' doesn't report errors, but gdm screen is never shown). Then tried with lightdm and it works, but sugar session doesn't work.

I'm running out of time and options, I'll have to install one of the distros supported by Sugar project

City-busz · 2014-11-27 09:43:22

Hi, currently I'm working on adding Sugar platform to the official repositories. Stay tuned, packages will be available soon.

doragasu · 2014-11-27 15:30:55

That would be AWESOME, THANKS!

doragasu · 2014-12-26 15:12:20

Any news about this? Almost a month has passed and sugar has not yet appeared on the repos

City-busz · 2017-02-15 04:34:30

I hope that it's not too late, but I added Sugar to the [community] repository now. For more details see the wiki page: https://wiki.archlinux.org/index.php/Sugar

doragasu · 2017-02-15 06:22:21

A bit late for me, but some people will find it useful for sure, so thanks a lot anyway!

Arch Linux

#1 2014-11-15 19:58:34

[SOLVED] Anyone got OLPC Sugar running?

#2 2014-11-15 20:05:00

Re: [SOLVED] Anyone got OLPC Sugar running?

#3 2014-11-15 20:10:12

Re: [SOLVED] Anyone got OLPC Sugar running?

#4 2014-11-16 15:35:03

Re: [SOLVED] Anyone got OLPC Sugar running?

#5 2014-11-16 15:52:51

Re: [SOLVED] Anyone got OLPC Sugar running?

#6 2014-11-17 13:03:18

Re: [SOLVED] Anyone got OLPC Sugar running?

#7 2014-11-20 20:00:36

Re: [SOLVED] Anyone got OLPC Sugar running?

#8 2014-11-21 12:55:49

Re: [SOLVED] Anyone got OLPC Sugar running?

#9 2014-11-22 17:16:09

Re: [SOLVED] Anyone got OLPC Sugar running?

#10 2014-11-22 17:42:42

Re: [SOLVED] Anyone got OLPC Sugar running?

#11 2014-11-22 18:36:03

Re: [SOLVED] Anyone got OLPC Sugar running?

#12 2014-11-27 09:43:22

Re: [SOLVED] Anyone got OLPC Sugar running?

#13 2014-11-27 15:30:55

Re: [SOLVED] Anyone got OLPC Sugar running?

#14 2014-12-26 15:12:20

Re: [SOLVED] Anyone got OLPC Sugar running?

#15 2017-02-15 04:34:30

Re: [SOLVED] Anyone got OLPC Sugar running?

#16 2017-02-15 06:22:21

Re: [SOLVED] Anyone got OLPC Sugar running?

Board footer