compiz.real crashed with SIGSEGV in getWindowIcon()

[vasilis34]

Binary package hint: compiz

Compiz crashed when trying to change the screen brightness. The screen brightness was set to the right level but I couldn't access the desktop at all, although I could see the mouse cursor moving. I logged in a terminal via Ctrl+Alt+F1 and then back with Ctrl+Alt+F7 where I got the warning about the compiz crash. I am using the version Ubuntu 8.04 fully updated.

ProblemType: Crash
Architecture: amd64
Date: Fri Apr 18 19:57:59 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/compiz.real
NonfreeKernelModules: nvidia
Package: compiz-core 1:0.7.4-0ubuntu5
PackageArchitecture: amd64
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=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: compiz
StacktraceTop:
 getWindowIcon ()
 ?? () from /usr/lib/compiz/libscale.so
 ?? () from /usr/lib/compiz/libscaleaddon.so
 ?? () from /usr/lib/compiz/libscale.so
 ?? () from /usr/lib/compiz/libswitcher.so
Title: compiz.real crashed with SIGSEGV in getWindowIcon()
Uname: Linux 2.6.24-16-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:getWindowIcon (w=0x1a38b80, width=96, height=96)
scalePaintDecoration (w=0x1a38b80,
scaleaddonScalePaintDecoration (w=0x1a38b80,
scalePaintWindow (w=0x1a38b80,
switchPaintWindow (w=0x20, attrib=0x18d9358,

[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!

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 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!