https://bugs.kde.org/show_bug.cgi?id=493699
TraceyC <kde...@tlcnet.info> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |CONFIRMED
CC| |kde...@tlcnet.info
--- Comment #7 from TraceyC <kde...@tlcnet.info> ---
I am able to reproduce this on git-master, fully rebuilt with kde-builder
workspace and restarted
Night Light does not retrieve the current location, causing it to use Lat: 0
Long: 0 as the location. This causes Night Light to turn on and off at the
wrong times.
STEPS TO REPRODUCE
1. Set Night Light to Sunset and sunrise at current location, Apply
OBSERVED RESULT
The status animation under "Locating..." stays animated until some timeout is
reached
The current location is not detected
Night light turns night mode on at the wrong time, even though GeoIP.com
correctly detects my location based on the machine's IP.
After some time, the current location shown in the kcm is Lat: 0 Long: 0
EXPECTED RESULT
Location is detected
Additional note:
If the location lookup fails, there should be an error presented to the user to
let them know what happened and what steps, if any, they can take
SOFTWARE/OS VERSIONS - reproduced on
git-master (re-ran kde-builder workspace)
also on
KDE Neon (Uses GeoClue2, no animation representing location query)
KDE Neon Testing
Kubuntu (still says its using Mozilla Location Service - which returns US as my
country, verified by clicking the link) - one older VM, one freshly installed
VM
also on
Operating System: Solus 4.6
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.7.3
Kernel Version: 6.11.7-309.current (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
geoip.com correctly detects my machine's IP address and location based on that
Another user that has Solus Plasma sees the same issue (located in Canada, we
are both in Central Time)
>From git-master:
~ systemsettings kcm_nightlight
qml: Pushed pages do not conform to the rules. Please check the documentation.
qt.positioning.geoclue2: Unable to obtain the client:
"org.freedesktop.DBus.Error.ServiceUnknown" "The name is not activatable"
I'm wondering if queries to the APIs fail from certain locations but not
others?
--
You are receiving this mail because:
You are watching all bug changes.
