gnome-terminal crashed with SIGSEGV in g_object_notify()

[Pedro Villavicencio]

Gnome terminal crashes when I try to detach a tab... yes it does it everytime and its 100% reproducible, if you need some extra info, please let me know.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-terminal 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic i686
ApportVersion: 2.6.1-0ubuntu9
Architecture: i386
Date: Wed Jan 16 09:39:37 2013
ExecutablePath: /usr/bin/gnome-terminal
InstallationDate: Installed on 2012-08-28 (140 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
ProcCmdline: gnome-terminal
ProcEnviron:
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6f16858 <g_object_notify+40>: cmpl $0x50,(%eax)
 PC (0xb6f16858) ok
 source "$0x50" ok
 destination "(%eax)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 g_object_notify () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 g_cclosure_marshal_VOID__VOID () 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
Title: gnome-terminal crashed with SIGSEGV in g_object_notify()
UpgradeStatus: Upgraded to quantal on 2012-10-10 (97 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #864813, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.