Do.exe crashed with signal 5 in _XError()

Bug #323118 reported by İsmail Dönmez
182
This bug affects 35 people
Affects Status Importance Assigned to Milestone
gnome-do (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-do

do.exe randomly crashes.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/gnome-do/Do.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: gnome-do 0.6.1.0-0ubuntu3
ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
Signal: 5
SourcePackage: gnome-do
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XEventsQueued () from /usr/lib/libX11.so.6
 XPending () from /usr/lib/libX11.so.6
Title: Do.exe crashed with signal 5 in _XError()
Uname: Linux 2.6.28-6-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
İsmail Dönmez (ismaildonmez) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gdk_x_error (display=<value optimized out>,
_XError (dpy=0x1f64af0, rep=0x22b4160)
process_responses (dpy=0x1f64af0,
_XEventsQueued (dpy=0x1f64af0,
XPending (dpy=0x1f64af0) at ../../src/Pending.c:56

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-do:
importance: Undecided → Medium
Revision history for this message
nyarnon (cabal) wrote :

Confirm same problem on a eeepc 1000h setting report to confirmed

Changed in gnome-do:
status: New → Confirmed
Revision history for this message
Muharem Hrnjadovic (al-maisan) wrote :

Same problem on a Samsung Q45 running Jaunty alpha 4

fn80: ~ $ gnome-do
Gdk-ERROR **: The program 'Do' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
  (Details: serial 757 error_code 16 request_code 60 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Trace/breakpoint trap (core dumped)
fn80: ~ $ uname -a
Linux fn80 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009 x86_64 GNU/Linux

fn80: ~ $ apt-cache show gnome-do | head
Package: gnome-do
Priority: optional
Section: universe/gnome
Installed-Size: 1196
Maintainer: Ubuntu MOTU Developers <email address hidden>
Original-Maintainer: Debian CLI Applications Team <email address hidden>
Architecture: amd64
Version: 0.6.1.0-0ubuntu3

Revision history for this message
wavded (wavded) wrote :

Just happened to me in Karmic Alpha 3, a while after todays updates were installed for gnome-do and gnome-do-plugins

Revision history for this message
Pascal Hartig (passy) wrote :

Happened to me, too. Without an obvious reason.

Revision history for this message
Mark Cariaga (mzc) wrote :

appears on lucid lynx alpha 3..possible regression...

Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in gnome-do (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.