redshift crashed with SIGSEGV in geoclue_master_client_set_requirements()

[Daniel Hahler]

Likely a duplicate of bug 888661, but maybe it will contain more information.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: redshift 1.7-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic-pae 3.0.6
Uname: Linux 3.0.0-13-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Fri Nov 11 09:09:48 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/redshift
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: redshift
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0xb749e3b6 <geoclue_master_client_set_requirements+134>: mov (%eax),%eax
 PC (0xb749e3b6) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: redshift
StacktraceTop:
 geoclue_master_client_set_requirements () from /usr/lib/libgeoclue.so.0
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
Title: redshift crashed with SIGSEGV in geoclue_master_client_set_requirements()
UpgradeStatus: Upgraded to oneiric on 2011-09-29 (42 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers
XsessionErrors:
 (nautilus:3144): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (nautilus:3144): Gtk-CRITICAL **: gtk_action_set_visible: assertion `GTK_IS_ACTION (action)' failed
 (gwibber-service:3824): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #888661, 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.