eclipse crashed with SIGSEGV in gdk_window_enable_synchronized_configure()

Bug #863469 reported by Peter Aldaron
94
This bug affects 16 people
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

after an unexpected suspension, X server was killed. after reboot, system throws this error.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: eclipse-platform 3.7.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Fri Sep 30 13:03:17 2011
ExecutablePath: /usr/lib/eclipse/eclipse
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
ProcCmdline: /usr/lib/eclipse/eclipse
SegvAnalysis:
 Segfault happened at: 0x7f50bac0176e <gdk_window_enable_synchronized_configure+14>: mov 0x18(%rdi),%rbx
 PC (0x7f50bac0176e) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: eclipse
StacktraceTop:
 gdk_window_enable_synchronized_configure () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: eclipse crashed with SIGSEGV in gdk_window_enable_synchronized_configure()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Peter Aldaron (peteraldaron) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 IA__gdk_window_enable_synchronized_configure (window=0x0) at /build/buildd/gtk+2.0-2.24.6/gdk/x11/gdkwindow-x11.c:5448
 gtk_window_realize (widget=0x1831020) at /build/buildd/gtk+2.0-2.24.6/gtk/gtkwindow.c:4949
 g_closure_invoke (closure=0x181b4d0, return_value=0x0, n_param_values=1, param_values=0x1804360, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x1831020, emission_return=0x0, instance_and_params=0x1804360) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3202
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3003

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 eclipse (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in eclipse (Ubuntu):
status: New → Confirmed
Benjamin Drung (bdrung)
visibility: private → public
Revision history for this message
Vladimir Scherbaev (zemik) wrote :

A have this problem on 12.04 with latest upgrade.

Revision history for this message
Josh Burghandy (kid1000002000) wrote :

Also having this problem in 12.04 with latest update/upgrades. Have tried completely removing and reinstalling to no avail.

Revision history for this message
Martin Stechert (martin-stechert) wrote :

For me linux-image-3.0.0-18-generic (3.0.0-18.31~lucid1 from linux-image-generic-lts-backport-oneiric) caused such Problems with lucid (eclipse constabntly cased with different traces). Using a different kernel solved the problem for me.

tags: added: precise
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.