Bug 2021257 - geoclue cannot be enabled
Summary: geoclue cannot be enabled
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: geoclue2
Version: 35
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Zeeshan Ali
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-08 16:56 UTC by Alexandre Ducastaing
Modified: 2021-11-24 14:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Alexandre Ducastaing 2021-11-08 16:56:19 UTC
Description of problem:
geoclue doesn't start on boot.

Version-Release number of selected component (if applicable):
$ rpm -qa | grep geoclue2
geoclue2-2.5.7-6.fc35.x86_64
geoclue2-libs-2.5.7-6.fc35.x86_64
$ 

How reproducible:
# systemctl enable geoclue
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
 
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
# 

Steps to Reproduce:
1.# systemctl enable geoclue
2.reboot
3.$ redshift
Essai du fournisseur de localisation « geoclue2 »...
Utilisation du fournisseur « geoclue2 ».
Utilisation de la méthode « randr ».
En attente de localisation initiale...
Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' disallowed, no agent for UID 1000.
Access to the current location was denied by GeoClue!
Make sure that location services are enabled and that Redshift is permitted
to use location services. See https://github.com/jonls/redshift#faq for more
information.
Impossible d'obtenir une localisation du fournisseur.
$ 

Actual results:
$ systemctl status geoclue
○ geoclue.service - Location Lookup Service
     Loaded: loaded (/usr/lib/systemd/system/geoclue.service; static)
     Active: inactive (dead)
$ 

Expected results:
geoclue should be activated on boot.

Additional info:
"# systemctl start geoclue" works.

Comment 1 Alexandre Ducastaing 2021-11-24 14:21:31 UTC
Nothing has changed yet. Could you please have a look ?


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