compiz crashed with signal 5 in g_type_create_instance()

[jerrylamos]

Booted utopic updated to -8 limux image level, wallpaper no unity panels, so did Ctrl-Alt-F1 and sudo unity. Ctrl-Alt-F7 to get back to graphics screen.

Utopic then reported internal error in a normal drop down window.

Utopic brought up firefox O.K. and reported error. Firefox window running just fine, still no panels.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20140811-0ubuntu1
Uname: Linux 3.16.0-031600rc6-generic x86_64
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 16 13:23:12 2014
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2014-07-20 (27 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140720)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libbamf3.so.2
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with signal 5 in g_type_create_instance()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? () from /tmp/apport_sandbox_XYncV8/usr/lib/x86_64-linux-gnu/libbamf3.so.2
 g_type_create_instance (type=<optimized out>) at /build/buildd/glib2.0-2.41.2/./gobject/gtype.c:1865
 g_object_new_internal (class=0x0, class@entry=0x1220ee0, params=0xffffffff, params@entry=0x0, n_params=0) at /build/buildd/glib2.0-2.41.2/./gobject/gobject.c:1774
 g_object_newv (object_type=object_type@entry=14290816, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at /build/buildd/glib2.0-2.41.2/./gobject/gobject.c:1922
 g_object_new (object_type=14290816, first_property_name=0x0) at /build/buildd/glib2.0-2.41.2/./gobject/gobject.c:1614

[jerrylamos (jerrylamos)]

Did Ctrl-Alt-F1 and saw a whole pile of messages from unity trying to start.

Earliest error message:

"unity is not supported by your hardware"

Hello? Unity runs fine with utopic linux-image -5 level and -6 level.

How come utopic unity at -8 level has decided that "unity is not supported by your hardware"?

VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz

Has bee running unity all along until linux image -7 level. At linux -5 level unity is supported by this Lenovo 6234 ThinkCentre, suddenly -7 and -8 decide unity is not supported by this same hardware that has been running unity fine?

Thanks, Jerry

[jerrylamos (jerrylamos)]

Did Ctrl-Alt-F1 and saw a whole pile of messages from unity trying to start.

Earliest error message:

"unity is not supported by your hardware"

Hello? Unity runs fine with utopic linux-image -5 level and -6 level.

How come utopic unity at -8 level has decided that "unity is not supported by your hardware"?

VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz

Has bee running unity all along until linux image -7 level. At linux -5 level unity is supported by this Lenovo 6234 ThinkCentre, suddenly -7 and -8 decide unity is not supported by this same hardware that has been running unity fine?

Thanks, Jerry

Bug #1357746 is in the same area. Compiz and unity fail to start on later kernels while the -5 kernel on the same utopic runs.

[jerrylamos (jerrylamos)]

This bug may be related:
https://bugs.launchpad.net/bugs/1359299

nomodeset on the linux boot line allows unity to run with low res mode. Not useful except for trying bug fixes.

[jerrylamos (jerrylamos)]

linux-image-3.16.0-12 booted O.K. several times this morning.
I wouldn't know whether there is actually a fix for compiz or just whether the timing race of compiz/x is better.....

So as of 3.16.0-12 this problem has not reproduced over several boots.....

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Will Cooke (willcooke)]

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.