Red Hat Bugzilla – Bug 1309177
redshift doesn't start because of Geoclue error
Last modified: 2016-12-20 13:46:47 EST
Description of problem: After installing from the software center, Redshift will not run due to a lack of permissions in Geoclue.conf Version-Release number of selected component (if applicable): redshift-gtk-1.11-1.fc23.x86_64 How reproducible: Always since yesterday. Steps to Reproduce: 1. Install redshift-gtk 2. Run redshift-gtk Actual results: Prints to stderr: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Then displays an error dialog: Failed to run Redshift Trying location provider `geoclue2'... Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 1000. Unable to connect to GeoClue. Unable to get location from provider. Then exits. Expected results: Redshift runs. Additional info: This looks somehow related to #1214978. However both desktop files are now available: $ rpm -qf /usr/share/applications/redshift-gtk.desktop redshift-gtk-1.11-1.fc23.x86_64 $ rpm -qf /usr/share/applications/redshift.desktop redshift-1.11-1.fc23.x86_64 $ As usual adding a few lines to /etc/geoclue/geoclue.conf solves the problem, but I understand this is not the proper way to fix this: [redshift] allowed=true system=false users=
Actually geoclue was disabled. Enabling it fixes redshift. Still, redhsift should display a better error message and perhaps open up a dialog to set the location manually.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.