Description of problem: gnome-maps reference to undefined property "state" Version-Release number of selected component (if applicable): 3.30.2.1 How reproducible: always Steps to Reproduce: 1. execute gnome-maps 2. move around 3. Actual results: Gjs-Message: 10:02:41.103: JS WARNING: [resource:///org/gnome/Maps/js/application.js 192]: reference to undefined property "state" Expected results: no error, the code should reference to defined properties only Additional info:
Can you file this upstream at https://gitlab.gnome.org/GNOME/gnome-maps please? We don't have anyone working on gnome-maps code in Fedora, just packaging up what upstream releases.
(In reply to Kalev Lember from comment #1) > Can you file this upstream at https://gitlab.gnome.org/GNOME/gnome-maps > please? We don't have anyone working on gnome-maps code in Fedora, just > packaging up what upstream releases. done: https://gitlab.gnome.org/GNOME/gnome-maps/issues/140
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
seems fixed