metacity crashed with SIGSEGV in g_main_context_dispatch()

Bug #212382 reported by pasqoo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: metacity

In gconf-editor I've enabled the compositing (/apps/metacity/general/compositing_manager), and all worked. Even in the same window (I didn't close it)... I decided to switch it off, and then metacity crashed (and restarted automatically, with compositing_manager correctly disabled)

ProblemType: Crash
Architecture: amd64
Date: Sat Apr 5 18:42:48 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/metacity
NonfreeKernelModules: nvidia
Package: metacity 1:2.22.0-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: /usr/bin/metacity --sm-client-id=default0
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: metacity
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
Title: metacity crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.24-15-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner vboxusers video

Tags: apport-crash
Revision history for this message
pasqoo (pasqoo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_timeout_dispatch (source=0x9894f0,
IA__g_main_context_dispatch (context=0x693d40)
g_main_context_iterate (context=0x693d40, block=1,
IA__g_main_loop_run (loop=0x693f70)
main (argc=1, argv=0x7fffea688548) at core/main.c:476

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in metacity:
importance: Undecided → Medium
pasqoo (pasqoo)
description: updated
description: updated
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in metacity:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
pasqoo (pasqoo) wrote :

yes, the problem still exists for me, i don't know if other users has the same problem.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

could you try the same with intrepid or jaunty? i cannot reproduce this issue there, thanks.

Revision history for this message
pasqoo (pasqoo) wrote :

With Intrepid the bug doesn't exist for me. No more crash :)
Good work, bye.

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing since that works correctly in intrepid

Changed in metacity (Ubuntu):
status: Incomplete → Fix Released
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.