netbook-launcher crashed with SIGFPE in clutter_actor_allocate()

[Frej]

,

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 9 00:32:59 2010
DistroRelease: Ubuntu 10.04
DkmsStatus:

ExecutablePath: /usr/bin/netbook-launcher
GConfNonDefault:
 /apps/netbook-launcher/disable_single_instance=false
 /apps/netbook-launcher/force_low_graphics=false
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
MachineType: ASUSTeK Computer INC. 1005HA
Package: netbook-launcher 1:2.1.14-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-16-generic root=UUID=04c27e64-68b8-4935-a58b-e52a7c2cd41f ro quiet splash
ProcCmdline: netbook-launcher
ProcEnviron:
 LANG=sv_SE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
Signal: 8
SourcePackage: nvidia-graphics-drivers
StacktraceTop:
 ?? () from /usr/lib/libclutk-0.2.so.0
 clutter_actor_allocate ()
 ?? ()
 clutter_actor_allocate ()
 ?? () from /usr/lib/libclutk-0.2.so.0
Title: netbook-launcher crashed with SIGFPE in clutter_actor_allocate()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/18/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd06/18/2009:svnASUSTeKComputerINC.:pn1005HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1005HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
system:
 distro: Ubuntu
 codename: lucidarchitecture: i686kernel: 2.6.32-16-generic

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #445995, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.