Bug 1250320

Summary: gnome-clocks crashes when is added New York city on ppc64le
Product: Red Hat Enterprise Linux 7 Reporter: Lukas Vacek <lvacek>
Component: gnome-clocksAssignee: Matthias Clasen <mclasen>
Status: CLOSED WORKSFORME QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: thudziec, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-27 10:49:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Vacek 2015-08-05 07:04:19 UTC 
Description of problem:
When user add new york clock then gnome-clocks exits
When gnome-clocks are open again, new york clock is added

Version-Release number of selected component (if applicable):
kernel-3.10.0-300.el7.ppc64le
gnome-clocks-3.14.1-1.el7.ppc64le

How reproducible:
70%

Steps to Reproduce:
1.open gnome-clocks
2.click World and New
3.type New York and select some city from option
(it seems that if for example Niagara Falls is added, then gnome-clocks exits but when gnome-clocks is opened again Niagara Falls are removed and added, then it wont exit)

Actual results:
City is added but gnome-clocks crashes

Expected results:
City is added

Additional info:


#gnome-clocks
** (gnome-clocks:21003): CRITICAL **: file src/geocoding.c: line 1733: unexpected error: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 0 (g-dbus-error-quark, 9)
Segmentation fault
#echo $?
139




System:	ibm-p8-05-lp3.rhts.eng.bos.redhat.com
https://beaker.engineering.redhat.com/jobs/1038366

dmesg:
[66013.521588] gnome-clocks[20817]: unhandled signal 11 at 0000000000000028 nip 00003fffb1bff068 lr 00003fffb1bff05c code 3001
Comment 1 Lukas Vacek 2015-08-05 07:53:17 UTC 
same problem on kernel-3.10.0-300.el7.ppc64