[Sugar-devel] sugar-runner stop working?
quozl at laptop.org
Sun Jan 6 17:48:08 EST 2019
On Sun, Jan 06, 2019 at 02:39:32PM +0100, Samson Goddy wrote:
> Hello all,
> I was trying to install sugar alongside my Fedora 28. I keep getting
> this error message,
Perhaps you are using Wayland. Log out and then log in with session
"GNOME on Xorg" or "GNOME Classic" rather than "GNOME".
You didn't include logs from .sugar/default/logs/shell.log, so I can
only guess what went wrong. You can look at your logs to check.
My best guess is you were using Wayland as display manager, which does
not yet work with Sugar. See issue #778.
When it is tried in Fedora 28, the Wnck library returns None for
Wnck.Screen.get_default, which causes a traceback on screen.connect
Because the traceback is in initialisation code rather than a
callback, it is fatal, and Sugar stops.
When you use "GNOME on Xorg", my tests just now show that Sugar starts
> At first, I tried to fix it by doing the following;
> On sugar-runner to specify the version.
> 27. import gi
> 29. gi.require_version('SugarRunner', '1.0')
> 48. gi.require_version('GTK', '3.0')
> On xephyr-window
> 20. import gi
> 22. gi.require_version('SugarRunner', '1.0')
> on xinitrc
> 24. import gi
> 26. gi.require_version('SugarRunner', '1.0')
The PyGObject warnings were fixed in March 2017 in
but there hasn't been a release of sugar-runner since 0.110. If you'd
like to maintain this component, let me know.
> After adding the following, I ran into this error https://
> Am I missing something?
Logs from sugar-runner are not helpful. This could be changed by
adding a message to sugar-runner to remind you to look somewhere else
sugar-runner was written before Wayland became the default, and so
does not tell you not to use Wayland. This could be changed too.
More information about the Sugar-devel