diff.py crashed with SIGSEGV in gdk_window_set_geometry_hints()

[Matthew Jaggard]

I regularly get crashes using RabbitVCS - I think the problem might be related to my NVidia graphics card though?

ProblemType: Crash
DistroRelease: Ubuntu 15.10
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 30 16:37:57 2015
ExecutablePath: /usr/lib/python2.7/dist-packages/rabbitvcs/ui/diff.py
InstallationDate: Installed on 2015-07-15 (137 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/python2.7/dist-packages/rabbitvcs/ui/diff.py -s /home/username/dev/viewone/docbuilder_simplerest/projects/DocBuilder/.project@base /home/username/dev/viewone/docbuilder_simplerest/projects/DocBuilder/.project@working
SegvAnalysis:
 Segfault happened at: 0x7fe862446794 <gdk_window_set_geometry_hints+20>: testb $0x30,0x84(%rdi)
 PC (0x7fe862446794) ok
 source "$0x30" ok
 destination "0x84(%rdi)" (0x00000084) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rabbitvcs
StacktraceTop:
 gdk_window_set_geometry_hints () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-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: diff.py crashed with SIGSEGV in gdk_window_set_geometry_hints()
UpgradeStatus: Upgraded to wily on 2015-11-02 (28 days ago)
UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo wireshark

[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 #1430287, 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.