compiz crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()

Bug #1366342 reported by Togo28
80
This bug affects 7 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

After Upgrade on Ubuntu 14.10 beta the compiz crashed at start

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
Uname: Linux 3.16.0-13-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Sep 6 17:23:04 2014
Disassembly: => 0x0: Cannot access memory at address 0x0
DistUpgraded: 2014-09-06 17:21:24,280 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
InstallationDate: Installed on 2014-03-30 (159 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
MachineType: ASUS All Series
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=de_DE
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=039b4125-475e-4025-9f6a-12217b0eaf13 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in g_cclosure_marshal_VOID__PARAM()
UpgradeStatus: Upgraded to utopic on 2014-09-06 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0703
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/29/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Sep 6 15:22:28 2014
xserver.configfile: default
xserver.errors:
 intel: Failed to load module "dri3" (module does not exist, 0)
 intel: Failed to load module "present" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 210
 vendor ACR
xserver.version: 2:1.15.1-0ubuntu9

Revision history for this message
Togo28 (togo28) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__PARAM (closure=0x8e3d620, return_value=0x0, n_param_values=2, param_values=0xbfffc130, invocation_hint=0xbfffc0e8, marshal_data=0x0) at /build/buildd/glib2.0-2.41.3/./gobject/gmarshal.c:1042
 g_closure_invoke (closure=0x8e3d620, return_value=0x0, n_param_values=2, param_values=0xbfffc130, invocation_hint=0xbfffc0e8) at /build/buildd/glib2.0-2.41.3/./gobject/gclosure.c:768
 signal_emit_unlocked_R (node=0x0, node@entry=0x8391dc8, detail=143144888, detail@entry=1277, instance=0x8876090, emission_return=0x0, instance_and_params=0xbfffc130) at /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3553
 g_signal_emit_valist (instance=0x8876090, signal_id=1, detail=1277, var_args=0xbfffc290 "t\031\037\261;") at /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3309

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Togo28 (togo28) wrote :

It happened once again after a restart

Revision history for this message
Togo28 (togo28) wrote :

It is not reproduceable, but it appears to evolve regurlarly

Revision history for this message
Togo28 (togo28) wrote :

The bug does not appear, if I start with another flavor of Ubuntu like Lubuntu

Stephen M. Webb (bregma)
information type: Private → Public
Changed in compiz (Ubuntu):
status: New → Triaged
importance: Medium → High
Revision history for this message
Will Cooke (willcooke) wrote :

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.

Changed in compiz (Ubuntu):
status: Triaged → Won't Fix
tags: added: desktop-bugscrub-autoclosed
To post a comment you must log in.