gnome-clocks crashed with SIGSEGV in gweather_location_serialize()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-clocks (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
-
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-clocks 3.27.1-1
ProcVersionSign
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Feb 24 00:44:47 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-09-11 (165 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/bin/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, user)
LANG=cs_CZ.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f6fba2c83cf <gweather_
PC (0x7f6fba2c83cf) 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_
?? ()
?? () from /usr/lib/
Title: gnome-clocks crashed with SIGSEGV in gweather_
UpgradeStatus: Upgraded to bionic on 2018-02-23 (0 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video
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.