netbook-launcher crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()

[Jose Maria Degreef]

Binary package hint: netbook-launcher

ubuntu-netbook-remix 9 10

This happened shortly after updating and restarting

ProblemType: Crash
Architecture: i386
Date: Fri Aug 7 20:36:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/netbook-launcher
Package: netbook-launcher 2.1.1-0ubuntu1
ProcCmdline: netbook-launcher
ProcEnviron:
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x95f73f: testb $0x1,0x39(%edx)
 PC (0x0095f73f) ok
 source "$0x1" ok
 destination "0x39(%edx)" (0xaaaaaae3) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: netbook-launcher
StacktraceTop:
 ?? () from /usr/lib/libclutter-glx-1.0.so.0
 g_cclosure_marshal_VOID__OBJECT ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Tags: ubuntu-unr
Title: netbook-launcher crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/libclutter-glx-1.0.so.0
IA__g_cclosure_marshal_VOID__OBJECT (closure=0x977f3d0,
g_type_class_meta_marshal (closure=0x977f3d0,
IA__g_closure_invoke (closure=0x977f3d0, return_value=0x0,
signal_emit_unlocked_R (node=<value optimized out>,

[Michał Mrówczyński (ups5)]

ACER Aspire One 150 b/w

[gfang (gdfangerow)]

Acer Aspire One D250

[PatrickSCarrroll (patrickscarroll-hotmail)]

Eee PC 1000h

[Bruce Wolk (bawolk)]

Eee PC 1005ha

[Broomer68 (jbezemer)]

msi Wind U90

[Jose Maria Degreef (degreef64)]

Acer aspire one

[don hardaway (don-hardaway)]

Macbook Pro (Santa Rosa)

[Paul Larson (pwlars)]

Thanks for taking the time to report this bug and help make Ubuntu better. It seems this bug has also been reported and triaged in bug #411091 so I am duping it to that one. Also, thanks to all who are confirming that they have the problem as well, however it is not necessary to update with every model this has been tested on. In this case, it doesn't seem related to a specific piece of hardware, so it's enough to just subscribe yourself to the bug. Thanks!