gnome-clocks crashed with SIGSEGV in gweather_location_serialize()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-clocks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
While upgrading Ubuntu 18.04 alpha 2 packages it just popped up. I didn't even notice anything crashing.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-clocks 3.27.1-1
ProcVersionSign
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Feb 24 22:25:50 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2015-09-04 (904 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150904)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f3860e523cf <gweather_
PC (0x7f3860e523cf) 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_
()
g_ptr_
()
() at /usr/lib/
Title: gnome-clocks crashed with SIGSEGV in gweather_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
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.