gnome-terminal-server crashed with SIGSEGV in gtk_application_impl_window_added()

[Roger]

This happened on a fully up-to-date Ubuntu Gnome 15.04, with Gnome Shell 3.16 from the gnome3-staging PPA. It occured in the background, after having started (and crashed) gnome-maps from the cli. It appears there's a conlict between totem/gnome-maps, on the one hand, and the nvidia prorpietary drivers on the other. But I suspect this gnome-terminal bug is wholly unrelated.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-terminal 3.16.1-0ubuntu1~vivid1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 19 10:12:38 2015
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2015-04-17 (1 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150416)
ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
SegvAnalysis:
 Segfault happened at: 0x7fd211a13100: mov (%rdi),%rax
 PC (0x7fd211a13100) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_cclosure_marshal_VOID__OBJECTv () 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
Title: gnome-terminal-server crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Tim Lunn (darkxst)]

The Totem/Maps crash is https://bugzilla.gnome.org/show_bug.cgi?id=743897, it seems to be a bug in the propriety NVIDIA drivers, that however is in no way related to this crash