segfault in unity-window-decorator error 6

Bug #778075 reported by Andrew
96
This bug affects 18 people
Affects Status Importance Assigned to Milestone
Compiz Core
Incomplete
Undecided
Unassigned
compiz (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: compiz

unity-window-decorator segfaulted while using a java swing app with the file open dialog open (jdeveloper)

Syslog:
May 5 13:19:46 anrobins-pc kernel: [73242.349367] unity-window-de[2858]: segfault at 318 ip 0000000000415d6f sp 00007fffdb2f5b90 error 6 in unity-window-decorator[400000+1b000]

May be a duplicate of bug 775430

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: compiz-gnome 1:0.9.4+bzr20110415-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,vpswitch,move,place,mousepoll,regex,grid,imgpng,animation,unitymtgrabhandles,session,workarounds,wall,expo,ezoom,staticswitcher,fade,scale,unityshell]
CompositorRunning: compiz
DRM.card0.DP.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DP.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI.A.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1600x1200 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAQrAigTE0wMjQNAQOAKR947mOQo1dLmyURUFSlSwCBgKlAcU8BAQEBAQEBAQEBSD9AMGKwMkBAwBMAbxMRAAAeAAAA/wBDMDY0NjNDUjIwTUwgAAAA/ABERUxMIDIwMDFGUAogAAAA/QA4TB9QEAAKICAgICAgACU=
DRM.card0.HDMI.A.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.eDP.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1440x900 1440x900
 edid-base64: AP///////wAGr0dBAAAAAAETAQSVHhN4AonllFdUkyciUFQAAAABAQEBAQEBAQEBAQEBAQEBlCWgPlGEDDBAIDMAL70QAAAaDRmgPlGEDDBAIDMAL70QAAAaAAAA/gBEVjVKMYBCMTQxUFc0AAAAAAAAQSEeAAAAAAkBCiAgANU=
Date: Thu May 5 13:21:47 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.0.6, 2.6.38-9-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:040a]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Latitude E6410
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-9-generic root=UUID=71a52b02-65dd-4be1-9f45-8b2a0818ad51 ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Renderer: Unknown
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0667CC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd07/08/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0667CC:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.4+bzr20110415-0ubuntu2
version.ia32-libs: ia32-libs 20090808ubuntu13
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

Revision history for this message
Andrew (andrew-rw-robinson) wrote :
Revision history for this message
Andrew (andrew-rw-robinson) wrote :

running "compiz --replace &" seems to bring the desktop back and the unity bar is still functional

Revision history for this message
frank rothmann (rothmann) wrote :

I have exact the same problem with my lenovo T510.
It happens after closing a java app (yed) .

The compi --replace & brings the desktop back, but it's only a workaround.

Revision history for this message
Idar (idar-borlaug) wrote :

Happends with all java apps. also when using gnome and not unity.

Revision history for this message
coolcow (ruiz-jm) wrote :

I've tried it with gnome, and can confirm that the error occurs there as well.
This bug makes developing Java applications on natty really *%$!...

Revision history for this message
Idar (idar-borlaug) wrote :

Better than compiz --replace fix is : gtk-window-decorator --replace & Then the windows don't jump around.

Revision history for this message
Rocko (rockorequin) wrote :

"unity-window-decorator --replace&disown" works nicely as well.

I think this is a duplicate of 777249. I've posted a gdb backtrace at that bug.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in compiz (Ubuntu):
status: New → Invalid
Revision history for this message
blurry (brendan-robert) wrote :

Compiz goes down in flames with any java application, save Netbeans, but that's because Netbeans passes command line arguments to prevent the JRE's Swing implementation from using OpenGL compositing. It's been a known issue for a long time, too. If you'd like, I'll follow your steps outlined to report the crashes, but I'm going to run it every time it crashes until you guys finally do something about it. No offense, it's more important to me that you fix the window manager crash bugs than it is for you to add more wizbang features to Unity.

Revision history for this message
Harry van Haaren (harryhaaren) wrote :

Blurry: On a side note, perhaps grab those commands that prevent Swing using OpenGL, and stick them into your default java settings. That should temporarily solve the crashing on your machine.

Revision history for this message
Captain Chaos (launchpad-chaos) wrote :

@Pedro Villavicencio: assuming that your instructions have been followed and a new bug was created, would you mind marking this one as a duplicate of it? That way people finding this bug know where to go.

Changed in compiz (Ubuntu):
status: Invalid → New
Revision history for this message
blurry (brendan-robert) wrote :

This might be a dupe of 727143 which just got fixed.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Compiz, in particular, is in heavy development and this bug may have been fixed in the development version of Ubuntu (12.04) if not on your current version. If you are able, it would be of great help if you could confirm if the bug still exists by testing a livecd (available at ubuntu.com). When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue. If you are unable to test the development version, please let us know if you are able to reproduce this issue on Ubuntu 11.10.

Thank you for your help and patience.

Changed in compiz (Ubuntu):
status: New → Incomplete
Changed in compiz-core:
status: New → Incomplete
Revision history for this message
trespasserw (trespasserw) wrote :

It seems to be fixed some time ago - see https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/727143

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.