gnome-clocks crashed with SIGSEGV in gweather_location_serialize()

[tclovis]

1)
clovis@tclovis:~$ lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18
.04

2)
clovis@tclovis:~$ apt-cache policy gnome-clocks
gnome-clocks:
  Instalado: 3.27.1-1
  Candidato: 3.27.1-1
  Tabela de versão:
 *** 3.27.1-1 500
        500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
        100 /var/lib/dpkg/status

3) Solved

4) Crash gnome-clocks.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-clocks 3.27.1-1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 18 21:36:10 2018
ExecutablePath: /usr/bin/gnome-clocks
InstallationDate: Installed on 2014-01-10 (1500 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
ProcCmdline: /usr/bin/gnome-clocks --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f65c5b333cf <gweather_location_serialize+79>: mov (%rax),%rbx
 PC (0x7f65c5b333cf) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-clocks
StacktraceTop:
 gweather_location_serialize () from /usr/lib/x86_64-linux-gnu/libgweather-3.so.15
 ?? ()
 g_ptr_array_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-clocks crashed with SIGSEGV in gweather_location_serialize()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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