devilspie crashed with signal 5 in _XError()

Bug #522539 reported by Vish
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devilspie (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: devilspie

Not sure what happened i received a report that it just crashed.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 417990aadff2335cd485c57bb06c8968
CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
Date: Tue Feb 16 02:11:31 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/devilspie
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: devilspie 0.22-1
ProcCmdline: devilspie
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Signal: 5
SourcePackage: devilspie
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 _XGetWindowAttributes () from /usr/lib/libX11.so.6
Title: devilspie crashed with signal 5 in _XError()
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Vish (vish) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdk_x_error (display=0x8b7d9a8, error=0xbfff8dec)
 _XError (dpy=0x8b7d9a8, rep=0x8bf3708)
 process_responses (dpy=0x8b7d9a8,
 _XReply (dpy=0x8b7d9a8, rep=0xbfff8f68, extra=0, discard=1)
 _XGetWindowAttributes (dpy=0x8b7d9a8, w=39846489,

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 devilspie (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Vish (vish)
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

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