seamonkey-bin crashed with signal 5 in _XError()

Bug #327633 reported by elihh
10
Affects Status Importance Assigned to Milestone
seamonkey (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: seamonkey

jaunty 2.6.28-7-generic

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/seamonkey/seamonkey-bin
Package: seamonkey-browser 1.1.13+nobinonly-0ubuntu1 [modified: usr/share/seamonkey/chrome/installed-chrome.txt]
ProcCmdline: /usr/lib/seamonkey/seamonkey-bin -remote xfeDoCommand(openChat)
ProcCwd: /home/eli
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: seamonkey
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XGetWindowProperty () from /usr/lib/libX11.so.6
 ?? ()
Title: seamonkey-bin crashed with signal 5 in _XError()
Uname: Linux 2.6.28-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
elihh (elihh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gdk_x_error (display=0x8e9eaa8, error=0xbf961d38)
_XError (dpy=0x8e9eaa8, rep=0x8d9d1f8)
_XReply (dpy=0x8e9eaa8, rep=0xbf961e3c, extra=0, discard=0)
XGetWindowProperty (dpy=0x8e9eaa8, w=30408914,
XRemoteClient::GetLock (this=0xbf9621c0, aWindow=30408914,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in seamonkey:
importance: Undecided → Medium
Revision history for this message
dino99 (9d9) wrote :

That's quite old; report with newer active version if needed

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

Other bug subscribers

Remote bug watches

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