redshift-gtk crashed with SIGSEGV in start_thread()

[henry adler]

Tried to run Redshift when switching between Nouveau and NVIDIA binary 331.89 from nvidia-331 (proprietary, tested):

Gamma ramp size too small: 0
Failed to start adjustment method randr.
Trying next method...
Using method `vidmode'.
^CSegmentation fault (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: redshift-gtk 1.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
Uname: Linux 3.16.0-21-generic x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Oct 8 20:17:09 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/redshift-gtk
InstallationDate: Installed on 2012-04-02 (919 days ago)
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/redshift-gtk
SegvAnalysis:
 Segfault happened at: 0x50d4ab: subq $0x1,(%rcx)
 PC (0x0050d4ab) ok
 source "$0x1" ok
 destination "(%rcx)" (0x00000000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: redshift
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7fa5d8bfc700) at pthread_create.c:309
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Title: redshift-gtk crashed with SIGSEGV in start_thread()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

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