gnome-terminal crashed with SIGSEGV in g_object_notify()

[Zygmunt Krynicki]

My terminal crashed while I was dragging some tabs around

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-terminal 3.6.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
Date: Wed Mar 20 12:10:05 2013
ExecutablePath: /usr/bin/gnome-terminal
InstallationDate: Installed on 2013-02-12 (35 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130210)
MarkForUpload: True
ProcCmdline: gnome-terminal
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f68c970eb96 <g_object_notify+38>: cmpq $0x50,(%rax)
 PC (0x7f68c970eb96) ok
 source "$0x50" ok
 destination "(%rax)" (0x0000001d) 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/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-terminal crashed with SIGSEGV in g_object_notify()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sbuild 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 #860330, 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.