compiz crashed with SIGSEGV in g_main_context_check() from g_main_context_iterate() from g_main_loop_run() from gdbus_shared_thread_func() from g_thread_proxy() from start_thread()

Bug #1039200 reported by Sven.Frings
84
This bug affects 15 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Expired
Medium
Unassigned

Bug Description

this bug appeared after i work´d with ubuntu Tweak i use Ubuntu 12.10 Alpha 3 64Bit

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+bzr3249-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.4-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 20 21:57:08 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.3)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f140bc969e3 <g_main_context_check+83>: cmpw $0x0,0x4(%rdi)
 PC (0x7f140bc969e3) ok
 source "$0x0" ok
 destination "0x4(%rdi)" (0x200000006) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in g_main_context_check()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 gnome-session[4924]: WARNING: Application 'compiz.desktop' killed by signal 11
 gnome-session[4924]: WARNING: App 'compiz.desktop' respawning too quickly
 gnome-session[4924]: CRITICAL: We failed, but the fail whale is dead. Sorry....

Revision history for this message
Sven.Frings (svenkirk) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_main_context_check (context=context@entry=0xbdba80, max_priority=2147483647, fds=fds@entry=0x7f13ec009d60, n_fds=n_fds@entry=9) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:3136
 g_main_context_iterate (context=0xbdba80, block=block@entry=1, dispatch=dispatch@entry=1, self=<error reading variable: Unhandled dwarf expression opcode 0xfa>) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:3279
 g_main_loop_run (loop=0xbdba10) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:3476
 gdbus_shared_thread_func (user_data=0xbdba50) at /build/buildd/glib2.0-2.33.8/./gio/gdbusprivate.c:277
 g_thread_proxy (data=0xc218f0) at /build/buildd/glib2.0-2.33.8/./glib/gthread.c:801

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-amd64-retrace
tags: added: compiz-0.9
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: compiz crashed with SIGSEGV in g_main_context_check()

This is odd. It's in a thread and compiz does not explicitly create threads. Also, there is no compiz code in the stack trace. But it is the compiz process.

visibility: private → public
summary: - compiz crashed with SIGSEGV in g_main_context_check()
+ compiz crashed with SIGSEGV in g_main_context_check() from
+ g_main_context_iterate() from g_main_loop_run() from
+ gdbus_shared_thread_func() from g_thread_proxy() from start_thread()
affects: compiz (Ubuntu) → unity (Ubuntu)
affects: unity (Ubuntu) → compiz (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in compiz (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is incomplete because we don't have enough details to work with. Only if someone can figure out a reliable test case will this change.

Changed in compiz (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.