Do.exe crashed with signal 5 in _XError()

Bug #640167 reported by Jitech
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-do (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: gnome-do

Not run gnome-do

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-do 0.8.3.1+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4
Uname: Linux 2.6.35-21-generic x86_64
Architecture: amd64
Date: Thu Sep 16 06:21:10 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

Revision history for this message
Jitech (jitech) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-do (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-do (Ubuntu):
status: New → Confirmed
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.