Do.exe crashed with signal 5 in _XError()

[Jitech]

Binary package hint: gnome-do

Do.exe crashed with signal 5 in _XError()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-do 0.8.3.1+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 20 17:40:23 2010
ExecutablePath: /usr/lib/gnome-do/Do.exe
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/mono
ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
ProcEnviron:
 PATH=(custom, user)
 LANG=cs_CZ.utf8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-do
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XGetGeometry () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: Do.exe crashed with signal 5 in _XError()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError (dpy=0xcc6320, rep=0x16626b0)
 _XReply (dpy=0xcc6320, rep=<value optimized out>,
 XGetGeometry (dpy=0xcc6320, d=75550761,
 ?? () from /usr/lib/libgdk-x11-2.0.so.0

[Steve Beattie (sbeattie)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #640167, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.