metacity crashed with SIGSEGV in g_timeout_dispatch()

Bug #188798 reported by Chris Halse Rogers
26
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: metacity

Metacity crashes repeatably when toggling the "composite_manager" gconf key on and off, with this error.

ProblemType: Crash
Architecture: amd64
Date: Mon Feb 4 11:07:32 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/metacity
NonfreeKernelModules: cdrom
Package: metacity 1:2.21.5-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/bin/metacity --sm-client-id=default0
ProcCwd: /home/raof
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/zsh
Signal: 11
SourcePackage: metacity
StacktraceTop:
 ?? ()
 g_timeout_dispatch (source=0x8f0950,
 IA__g_main_context_dispatch (context=0x693cf0)
 g_main_context_iterate (context=0x693cf0, block=1,
 IA__g_main_loop_run (loop=0x693f20)
Title: metacity crashed with SIGSEGV in g_timeout_dispatch()
Uname: Linux CowboyLaputopu 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm lpadmin netdev plugdev powerdev pulse-rt sambashare scanner src tape video
SegvAnalysis:
 Segfault happened at: 0x413652 <gdk_rectangle_intersect@plt+15810>: mov 0x28(%rax),%edi
 PC (0x00413652) ok
 source "0x28(%rax)" (0x00000049) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA

Tags: apport-crash
Revision history for this message
Chris Halse Rogers (raof) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:compositor_idle_cb (data=0x71c9b0) at compositor.c:1223
g_timeout_dispatch (source=0x8f0950, callback=0x413630 <compositor_idle_cb>,
IA__g_main_context_dispatch (context=0x693cf0)
g_main_context_iterate (context=0x693cf0, block=1, dispatch=1,
IA__g_main_loop_run (loop=0x693f20)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in metacity:
importance: Undecided → Medium
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Confirmed. From my duplicate:

"I had the compositor enabled. Have disabled it with gconf-editor and metacity has crashed. It has disabled it though."

Changed in metacity:
status: New → Confirmed
Kees Cook (kees)
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report Chris Halse Rogers , It has been a long time without any comment or a duplicate in this bug report and It is possible that the bug has been fixed. May you please try to reproduce it with the latest Stable Release of Ubuntu the Natty Narwhal and add the respective comments to the report? You can learn how to get that release at http://www.ubuntu.com/download . Thanks again and we appreciate your help.

Changed in metacity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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