Docky.exe crashed with signal 5 in _XError()

Bug #633604 reported by Francesco Muriana
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Docky
Incomplete
Medium
Unassigned
docky (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: docky

Docky.exe crashed with signal 5 in _XError(). This appened after the login sound of Ubuntu Maverick Beta.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: docky 2.0.6-2
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Sep 9 00:04:30 2010
ExecutablePath: /usr/lib/docky/Docky.exe
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/mono
PackageArchitecture: all
ProcCmdline: mono /usr/lib/docky/Docky.exe
ProcEnviron:
 LANG=it_IT.utf8
 SHELL=/bin/bash
Signal: 5
SourcePackage: docky
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
 XFlush () from /usr/lib/libX11.so.6
Title: Docky.exe crashed with signal 5 in _XError()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Francesco Muriana (f-muriana) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError (dpy=0x7fd084057310, rep=0x139dc00)
 process_responses (dpy=0x7fd084057310,
 _XEventsQueued (dpy=0x7fd084057310,
 XFlush (dpy=0x7fd084057310) at ../../src/Flush.c:39

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 docky (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Robert Dyer (psybers)
Changed in docky:
assignee: nobody → Jason Smith (jassmith)
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Robert Dyer (psybers) wrote :

Has this happened again? If/when it does, please post your ~/.xsession-errors file here (which should contain a stack trace from mono).

Changed in docky:
assignee: Jason Smith (jassmith) → nobody
Changed in docky (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for docky (Ubuntu) because there has been no activity for 60 days.]

Changed in docky (Ubuntu):
status: Incomplete → Expired
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.