Bug 1250320 - gnome-clocks crashes when is added New York city on ppc64le
gnome-clocks crashes when is added New York city on ppc64le
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-clocks (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Matthias Clasen
Desktop QE
Depends On:
  Show dependency treegraph
Reported: 2015-08-05 03:04 EDT by Lukas Vacek
Modified: 2017-07-27 06:49 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-27 06:49:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lukas Vacek 2015-08-05 03:04:19 EDT
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):

How reproducible:

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: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 $?

System:	ibm-p8-05-lp3.rhts.eng.bos.redhat.com

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

Note You need to log in before you can comment on or make changes to this bug.