compiz.real crashed with SIGSEGV when switching tasks and pressing ALT+F4

[João Rocha]

Binary package hint: compiz

I was switching tasks with Alt+Tab, and immediately after pressing this combination, and before the window transition effect was over, I pressed Alt+F4, hoping to close the window I was switching to. Instead, compiz crashed.

I'm using Ubuntu 8.04 beta, compiz 1:0.7.4-0ubuntu5 and NVidia 173.08 beta drivers on a GF 9600GT VGA adapter.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Apr 18 18:51:25 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.7.4-0ubuntu5
PackageArchitecture: i386
ProcCmdline: /usr/bin/compiz.real --ignore-desktop-hints --replace --loose-binding --sm-client-id default0 core ccp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_PT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0xb5b17733 in ?? () from /usr/lib/compiz/libwobbly.so
 #1 0x08113990 in ?? ()
 #2 0x081120a0 in ?? ()
 #3 0x08113600 in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/compiz/libwobbly.so
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: compiz.real crashed with SIGSEGV
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:shiftPaintOutput (s=0x80c45c0, sAttrib=0x807a680,
wobblyPaintOutput (s=0x80c45c0, sAttrib=0x807a680,
paintScreen (s=0x80c45c0, outputs=0x814a530, numOutput=1,
wallPaintScreen (s=0x80c45c0, outputs=0x814a530,
expoPaintScreen (s=0x80c45c0, outputs=0x814a530,

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 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.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Robert Ancell (robert-ancell)]

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!