[Debian-olpc-devel] Bug#522231: Bug#522231: Bug#522231: Bug#522231: sugar-emulator: sugar-shell crashes on startup
Matijs van Zuijlen
Matijs.van.Zuijlen at xs4all.nl
Sat Apr 4 08:45:32 UTC 2009
Jonas Smedegaard wrote:
> On Fri, Apr 03, 2009 at 01:49:22PM +0200, Matijs van Zuijlen wrote:
>> Jonas Smedegaard wrote:
>>>> "/usr/bin/sugar-shell": not in executable format: File format not
>>> Above seems suspicious.
>> I think it's a message from gdb when it's asked to make the backtrace
>> for bug-buddy.
> I am confused - how did bug-buddy and gdb get involved when you invoked
> some commands from a terminal?!?
The terminal is running from within gnome, and bug-buddy is installed. That
seems enough to trigger this. I can disable bug-buddy by setting
GNOME_DISABLE_CRASH_DIALOG=1. Then I get:
[matijs at apricot] GNOME_DISABLE_CRASH_DIALOG=1 sugar-emulator
INFO:sugar-emulator:Attempting to find free port for X11 (Xephyr)
INFO:sugar-emulator: Found free port: #2 (6002)
INFO:sugar-emulator:Starting the Xephyr nested X display on display 2
DEBUG:sugar-emulator:Xephyr command: Xephyr :2 -ac -fullscreen -dpi 114
INFO:sugar-emulator:Attempting to launch sugar to replace this process:
dbus-launch dbus-launch --exit-with-session sugar-shell
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
unrecognised device identifier!
1238833340.231385 ERROR dbus.proxies: Introspect error on
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The
name org.freedesktop.ohm was not provided by any .service files
zsh: segmentation fault (core dumped) GNOME_DISABLE_CRASH_DIALOG=1 sugar-emulator
[matijs at apricot] XIO: fatal IO error 11 (Resource temporarily unavailable) on X
after 50 requests (50 known processed) with 0 events
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":2.0"
after 579 requests (579 known processed) with 0 events remaining.
> Are you using Debian or Debian + some custom stuff?
No, just plain Debian. I am running metacity with compositing enabled, though.
That could be considered unusual.
> Please if you do unusual things then tell about it, to ease isolating
> the problem and find a fix.
I'll try eliminiting some variables ...
> Please provide output of the following commands too:
> which python
> $(which python) --version
More information about the Debian-olpc-devel