0,0 is not an "invalid location", it's in the Atlantic ocean, somewhere off the coast of Africa.
If you want to disable location-based changes, remove the location from the configuration.
WhyNotHugo (8a20355c) at 05 Feb 09:09
Fix detection of executable bit for scripts
Jarrett Boersen https://gitlab.com/jarboer commented #96 (comment 2999966500):
Disabling darkman's portal support does stop the icons from changing, it also prevents darkmode for working obviously as well.
The conclusion from this is that when the portal mode changes to dark, nautilus automatically changes your icon theme.
Yes, disabling it is not a solution, it was only meant to get a clearer understanding of the situation.
Is this maybe happening because I don't have my portals setup correctly? I have both xdg-desktop-portal-hyprland.service and xdg-desktop-portal.service running, but from my reading I may need another portal which implements more interfaces like the one for gtk. Notification message regarding #96 (comment 2999966500) at 1768241403
Nothing seems to be set up incorrectly, the behaviour your seeing seems to be intentional in nautilus. Perhaps they have some additional toggle to disable this feature?
There’s nothing that darkman can do to change it. It’s just announcing “the mode is now dark”, and nautilus reacts by changing the icon theme.
WhyNotHugo (b7c84de3) at 12 Jan 18:13
Fix detection of executable bit for scripts
WhyNotHugo (dc9bfe5d) at 12 Jan 18:10
Fix detection of executable bit for scripts
Darkman doesn’t do anything with regards to icon theme.
My guess is that nautilus is changing the icon theme based on the light/dark mode (probably the one set by the portal).
Try disabling darkman’s portal support and see if the same thing happens. This will indicate if my guess is correct or not.
WhyNotHugo (19e17375) at 07 Jan 16:32
Re-use dir entry; avoid stat
WhyNotHugo (58356091) at 26 Dec 22:51
Re-use dir entry; avoid stat
WhyNotHugo (8ad2a2ad) at 26 Dec 00:54
Split docs for configuration into darkman.conf.5