compiz.real crashed with SIGSEGV in addWindowDamage()

[Bill Turner, wb4alm]

Binary package hint: compiz

Was editing two files in OpenOffice.org writer v2.4 (each in their own window) when failure occurred.

Had a number of other File Browser windows also open, but had been switching back and forth between the two OpenOffice screens. Also had a VMware session running.

Note that my desktop is roughly 3840x1024 wide, and 4 desktops are defined...
...so problem could be related to the "large" amount of buffer space required. <grin>

Have noticed that when the screen "restarted" that Avant Window Navigator will not start.

= = = = =

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
    Ubuntu 8.04.2~hardy is installed. (64 bit desktop version)

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.

Compix-Gnome (and pluguns and...) 1:0.7.4-0ubuntu7 is lastest version and is installed.
avant-window-navigator 0.2.1-0ubuntu2

All system and application software is at current release levels according to Synaptic
     as of this morning Wed (Jul 23, 2008.)

3) What you expected to happen
    Documents edits to be applied...

4) What happened instead
    Screen flashed, received error message, and screen was restored with all applications still functioning
    (except avant-window-navigator, which is manually started when I manually start Xwindows (via startx command.)

ProblemType: Crash
Architecture: amd64
Date: Wed Jul 23 18:59:49 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.7.4-0ubuntu7
PackageArchitecture: amd64
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding --sm-client-id default0 core ccp
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
StacktraceTop:
 addWindowDamage ()
 resizeWindow ()
 handleSyncAlarm ()
 ?? ()
 ?? ()
Title: compiz.real crashed with SIGSEGV in addWindowDamage()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare scanner tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:addWindowDamage ()
resizeWindow ()
handleSyncAlarm ()
?? ()
?? ()

[Bill Turner, wb4alm (wb4alm)]

New occurance on 8-19-2008

I have four desktops defined - each desktop displays across three LCD screens (total resolution 3840x1024):

First desktop:
Screen is displayed across three panels:
first panel had an unsaved GEDIT session.
Second Panel Was editing single file in OpenOfice.org
third panel was running VMware Server

Second Desktop: was running Firefox display a "VueToo Hurricane Status page" on Tropical Storm FAY
URL: http://www.vuetoo.com/vue1/Situationpagenews.asp?rc=$cc=&af=&sit=1400&z=&np=
note: this site automatically updates pages, which it was doing at time of failure....
one screen defines 6 screens in a reduced resolution set of frames. Clicking on any frame
displays that frame "full screen" (1440x1024)

Third Desktop:
empty

Fourth Desktop:
empty

Also had Avant Window Navigator open - which will not restart until I restart Xwindows.

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Bill Turner, wb4alm (wb4alm)]

This is an intermitent problem. since the bug report I have had two or three re-occurances. I am a systems level programmer (but not for Linux - yet) and have not been able to determine a cause and am not able to create a situation which will always cause the problem to reoccur.

After reading your instuctions for generating a back trace, it does not seem possible/reasonable for me to run /usr/bin/compiz.real under the control of gdb for weeks (or months) waiting for a failure to occur again.

do you have any other suggestions?

/s/ Bill Turner, wb4alm

[Dimitrios Symeonidis (azimout)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Bill Turner, wb4alm (wb4alm)]

Dimitrios Symeonidis wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an issue
> for you. Can you try with the latest Ubuntu release? Thanks in advance.
>
>
I reported a series of problems with compiz between June 2008
thru Nov 2008, and after not hearing anything, even after spending
time to create supplemental data, I quit reporting the problems,
as it took far too much of my time.

Within the past 2 months, the number of failures have been minimal.
I am still running Ubuntu 8.04 as this is a production system, and
Compiz is at 1:0.7.4.0ubuntu7 according to Synaptic Package Manager.

/s/ Bill Turner, wb4alm

[Dimitrios Symeonidis (azimout)]

switching back to new then...

[Bill Turner, wb4alm (wb4alm)]

This is occurring several times a week now. I think it occurs when the system wants to start a screen saver, and (with my luck) I move the cursor...

[Bill Turner, wb4alm (wb4alm)]

Failed again. Had two windows open with OpenOffice.org 2.4 and was switching back and forth. Also had a number of other windows open.

[Travis Watkins (amaranth)]

Can anyone reproduce this problem with a newer release of Ubuntu?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.