| Summary: | Automatically detect location: Dear KDE developers, please write a detailed description of what this service will do | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | postix <postix> |
| Component: | kcm_nighttime | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | chris-hartmann, kde, vlad.zahorodnii |
| Priority: | HI | ||
| Version First Reported In: | 6.5.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
|
Description
postix
2025-11-02 17:55:35 UTC
`The service` it should be `The foobar service`, which probably implies that something's misconfigured on your system. (In reply to Vlad Zahorodnii from comment #1) > `The service` it should be `The foobar service`, which probably implies that > something's misconfigured on your system. geoclue2 is installed, the service is not running. When I start the service and re-open the SystemSettings the text doesn't change. Would you consider this a Tumbleweed bug? I've verified that the same happens with a new user account. ```
systemctl enable --now geoclue
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ 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.
```
```
systemctl status geoclue
● geoclue.service - Location Lookup Service
Loaded: loaded (/usr/lib/systemd/system/geoclue.service; static)
Active: active (running) since Mon 2025-11-03 13:03:21 CET; 3s ago
Invocation: d8d7a9908dac4ec789f2df6ea43683ba
Main PID: 7260 (geoclue)
Tasks: 11 (limit: 38232)
CPU: 48ms
CGroup: /system.slice/geoclue.service
└─7260 /usr/libexec/geoclue
```
This might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=497099 I'm also on openSUSE Tumbleweed. Geoclue2 is working with the demo-agent and where-am-i, however the day-night-cycle doesn't recognize the location and I entered the coords manually for now. *** This bug has been marked as a duplicate of bug 497099 *** |