redshift crashed with SIGSEGV in geoclue_provider_get_provider_info()

[LeandroDoctors]

I don't knw what to put here

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: redshift 1.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Mar 25 22:43:20 2014
ExecutablePath: /usr/bin/redshift
InstallationDate: Installed on 2014-02-20 (33 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140121.1)
ProcCmdline: /usr/bin/redshift
SegvAnalysis:
 Segfault happened at: 0x7fbe9efb31a6 <geoclue_provider_get_provider_info+38>: mov (%rax),%rdi
 PC (0x7fbe9efb31a6) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: redshift
StacktraceTop:
 geoclue_provider_get_provider_info () from /usr/lib/x86_64-linux-gnu/libgeoclue.so.0
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x402540, argc=1, argv=0x7fff28a4cee8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff28a4ced8) at libc-start.c:287
Title: redshift crashed with SIGSEGV in geoclue_provider_get_provider_info()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 geoclue_provider_get_provider_info (provider=0x0, name=name@entry=0x7fff28a4cb58, description=description@entry=0x0, error=error@entry=0x0) at geoclue-provider.c:492
 location_geoclue_start (state=0x7fff28a4cc60) at location-geoclue.c:91
 provider_try_start (provider=provider@entry=0x407da0 <location_providers>, state=state@entry=0x7fff28a4cc60, config=config@entry=0x7fff28a4cc40, args=<optimized out>, args@entry=0x0) at redshift.c:464
 main (argc=<optimized out>, argv=<optimized out>) at redshift.c:940

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.