My set up:
OS: Zorin OS 17.1 x86_64
Host: 4177A54 ThinkPad T420
Kernel: 6.5.0-44-generic
Uptime: 16 hours, 8 mins
Packages: 2350 (dpkg), 32 (flatpak), 12 (snap)
Shell: bash 5.1.16
Resolution: 1366x768
DE: Xfce
WM: Xfwm4
WM Theme: ZorinPurple-Dark
Theme: ZorinPurple-Dark [GTK2/3]
Icons: ZorinPurple-Dark [GTK2], ZorinBlue-Dark [GTK3]
Terminal: xfce4-terminal
Terminal Font: JetBrains Mono 10
CPU: Intel i5-2520M (4) @ 3.200GHz
GPU: NVIDIA Quadro NVS 4200M
GPU: Intel 2nd Generation Core Processor Family
Memory: 3496MiB / 7709MiB
Trying to tweak Redshift. Redshift was showing the colour temperature as 'OK' not very helpful and location as '0.0.0.' No discernible 'redness' on the display. No 'redshift.conf' in home directory. Tried to tweak and got the following errors. Any suggestions welcome.
Trying location provider geoclue2'... Using provider
geoclue2'.
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
Could not connect to wayland display, exiting.
Failed to start adjustment method wayland.
Trying next method...
Using method `randr'.
Waiting for initial location to become available...
Unable to obtain GeoClue client path: Timeout was reached.
Unable to get location from provider.
You don't need RedShift as Zorin has it's own equivalent:
Page 172 of the Unofficial Manual for Zorin 17 MkIIII - Comic Relief version pdf
Thank you for your reply. I have the Xfce desktop and this does not appear to have this night light feature.
Also I understand that from 12 Jun this year Mozilla shut down their geo location services.
opened 09:48PM - 19 Jun 24 UTC
0.kind: bug
### Describe the bug
Since June 12 Mozilla has shutdown their location service … (see https://gitlab.freedesktop.org/geoclue/geoclue/-/issues/186, https://github.com/mozilla/ichnaea/issues/2065). This means that the nixos geoclue service in its current state does not work anymore.
Quoting the upstream maintainer: "It is up to the distros and individual users to decide what backend they use for wifi and cell location and to get the necessary API keys. MLS already required distro-specific keys."
### Steps To Reproduce
Steps to reproduce the behavior:
1. set `services.geoclue2.enable = true;`
### Expected behavior
Geoclue service working out of the box.
### Additional information
Geoclue service logs:
```
Jun 19 23:34:26 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:35:31 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:36:44 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Could not connect to location.services.mozilla.com: No route to host
Jun 19 23:36:49 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:38:56 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:41:02 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:41:34 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:41:52 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:42:55 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
Jun 19 23:46:20 leon-inspiron .geoclue-wrappe[294835]: Failed to query location: Query location SOUP error: Not Found
```
### Notify maintainers
@davidak @bobby285271 @lovesegfault @peterhoeg @worldofpeace
<!--
Please @ people who are in the `meta.maintainers` list of the offending package or module.
If in doubt, check `git blame` for whoever last touched something.
-->
---
Add a :+1: [reaction] to [issues you find important].
[reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/
[issues you find important]: https://github.com/NixOS/nixpkgs/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc
If I'm mistaken please advise.
Thanks.
Try to set a schedule manually, in which case the geolocation service becomes irrelevantl; does this work at all?
Thanks. SCT works fine. I'll use that on a per session basis.
1 Like
Thanks for the reply. I'll try that
system
Closed
21 October 2024 12:05
8
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.