unity-window-decorator crashes when a java application closes a progress dialog window

[Christian Leutloff]

Binary package hint: compiz-gnome

The Java application is opening a dialog, showing progress information. When it is done then all the window decoration vanishes.

In /var/log/syslog this segfault is reported:

unity-window-de[1938]: segfault at 318 ip 0000000000415d6f sp 00007fff069acba0 error 6 in unity-window-decorator[400000+1b000]

The same Java program has been running successfully for a long time. Even on a Dell Mini 9 with the OEM Ubuntu version based on 8.04 LTS.

Is the syslog information enough to find the code location where the unity-window-decorator crashes? I can do some debugging with gdb and/or eclipse - but I have not developed with gnome, unity, compiz. Can you point me to a place where I can get the information to provide more useful information in a timely manner? I have read the wiki Unity FilingBugs.

ls -altr /var/crash is empty
The suggested way using `unity --advanced-debug` will this give a stack trace for the unity-window-decorator, too?

TiA Christian

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: unity 3.8.12-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
Architecture: amd64
CheckboxSubmission: 10b5b7d76f6fa22b9b6429c42051cd3f
CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,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: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI.A.2:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1920x1200 1600x1200 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAQrCqgUzI0MisTAQOANCB46rMlrFEwtCYQUFSlSwCBgKlAcU8BAQEBAQEBAQEBKDyAoHCwI0AwIDYAB0QhAAAaAAAA/wBHMjg2SDlBSjI0MlMKAAAA/ABERUxMIDI0MDhXRlAKAAAA/QA4TB5TEQAKICAgICAgAB0=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Tue May 17 09:57:40 2011
DistUpgraded: Log time: 2011-04-29 20:59:57.477447
DistroCodename: natty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Giga-byte Technology Device [1458:d000]
   Subsystem: Giga-byte Technology Device [1458:d000]
MachineType: Gigabyte Technology Co., Ltd. EG45M-DS2H
ProcEnviron:
 LANGUAGE=de_DE:en
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-9-generic root=UUID=1f48bc9a-204e-483e-ade8-4e4878928518 ro quiet splash vt.handoff=7
ProcVersionSignature_: Ubuntu 2.6.38-9.43-generic 2.6.38.4
ProcVersionSignature__: Ubuntu 2.6.38-9.43-generic 2.6.38.4
ProcVersionSignature___: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Renderer: Unknown
SourcePackage: unity
UpgradeStatus: Upgraded to natty on 2011-04-30 (17 days ago)
dmi.bios.date: 07/18/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: EG45M-DS2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/18/2008:svnGigabyteTechnologyCo.,Ltd.:pnEG45M-DS2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG45M-DS2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EG45M-DS2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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

[Maurice Knopp (maurice-knopp)]

This is affecting me as well in "Ubuntu Classic" aka Gnome environment. I use Intellij IDEA and some other java applications wich ran without problems in 10.04 and 9.04. My colleagues (all using ThinkStation S10 with NVIDIA Quadro FX 1700 and binary driver) have the exact same issue, regardless of using unity or classic gnome.

Right now, I run "compiz --replace" every time the window decorator crashes to recover from that bug. On a normal workday this bug occurs from 10-20 times. Pretty annoying :)

[Maurice Knopp (maurice-knopp)]

Here my var/log/syslog

-----
May 23 12:38:10 intel64 kernel: [20150.442456] unity-window-de[7992]: segfault at 318 ip 0000000000415d6f sp 00007fff33ab16b0 error 6 in unity-window-decorator[400000+1b000]
May 23 12:40:44 intel64 kernel: [20303.990597] unity-window-de[13344]: segfault at 318 ip 0000000000415d6f sp 00007fffae535540 error 6 in unity-window-decorator[400000+1b000]

[Pedro Villavicencio (pedro)]

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.

[Christian Leutloff (leutloff-sundancer)]

The requested crash report is found in Bug #789498. Therefore I have marked this bug a duplicate of this one.