java crashed with signal 5 in _XError()

Bug #505995 reported by Sef on 2010-01-11
This bug affects 18 people
Affects Status Importance Assigned to Milestone
libx11 (Ubuntu)
openjdk-6 (Ubuntu)

Bug Description

1) Lucid Lynx - 10.04

2) openjdk-6b17-0ubuntu1

3) Not to get a crash report upon rebooting. (Rebooted because kernel 2.6.32-10 was installed.)

4) Got a crash report upon rebooting.

ProblemType: Crash
Architecture: amd64
CheckboxSubmission: 99b5eeec5c67d3139a8cafec670cdb05
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Mon Jan 11 08:27:33 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
Package: openjdk-6-jre-headless 6b17-0ubuntu1
ProcCmdline: /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/../../bin/java sun.applet.PluginMain
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
Signal: 5
SourcePackage: openjdk-6
 ?? () from /usr/lib/
 _XError () from /usr/lib/
 _XReply () from /usr/lib/
 XGetImage () from /usr/lib/
 ?? ()
Tags: lucid
Title: java crashed with signal 5 in _XError()
Uname: Linux 2.6.32-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Sef (jo-ker) wrote :

 gdk_x_error (display=<value optimized out>,
 _XError (dpy=0x215c300, rep=0x7f9124127c30)
 _XReply (dpy=0x215c300, rep=<value optimized out>,
 XGetImage (dpy=0x215c300, d=<value optimized out>,
 X11SD_GetRasInfo (env=<value optimized out>,

Changed in openjdk-6 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Matthias Klose (doko) on 2010-03-17
visibility: private → public
Bryce Harrington (bryce) wrote :

Hi Sef,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

Please attach the output of `lspci -vvnn` too.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: crash
tags: added: needs-xorglog
Changed in libx11 (Ubuntu):
status: New → Incomplete
Eyad Salah (eyad-salah) wrote :

Here is the `lspci -vvnn` output but I don't know if I can reproduce the problem. I'm getting way too many java issues right now. Isn't there a way to find the part you're looking for in my current log files?

I'll try finding the log part using the bug date/time

Bryce Harrington (bryce) wrote :

@computerjy-computerjy - thanks for providing that info, but we would like to see it from the original reporter. We may want to send this bug report upstream, but upstream has a hard and fast rule that logs from someone other than the original reporter are not acceptable. The reason for that is that quite often with bug reports, two people may *think* they have the same issue based on commonality of symptoms and/or hardware, but in truth they have separate issues and mixing the report and the files can cause the developers some confusion.

If this bug report seems not to be getting attention, I would encourage you to file a new bug report with this data, and simply reference this bug report in your bug description.

Changed in libx11 (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Eyad Salah (eyad-salah) wrote :

Thanks for the advice. I'll do that if I see this error again

Bryce Harrington (bryce) wrote :

Okay, well in general this type of error just means the client application wasn't using the X11 protocol properly, or didn't account for some exceptional situation. At this point it looks more likely that this is the case, than that there's an error in libx11, so I'm closing out this task at this time. If more evidence comes to light pointing to an issue in libx11, reopen the libx11 bugtask with the details.

Changed in libx11 (Ubuntu):
status: Incomplete → Invalid
Jim Romines (jimromines-gmail) wrote :

Was trying to load freenet. During load, I resized the splash screen, and the installer << IMMEDIATELY >> crashed. It was quite impressive.

A. Denton (aquina) wrote :

The distribution is EOL (end of life) and the software version is also obsolete. Therefore I recommend to change this bug to WONT FIX now since this annot and won't be reproduced ever according to the original bug report description. I think in case this is still an issue someone will file a new bug with up-2-date information and debug information.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers