is it geoclue?

sudo systemctl status geoclue.service
○ geoclue.service - Location Lookup Service
     Loaded: loaded (/usr/lib/systemd/system/geoclue.service; static)
    Drop-In: /usr/lib64/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

I mean I don't use google services or personalized anything etc so I usually leave this turned off.

I have nightlight set for 24 hr coverage. 5am to 5 am. 5am to 4:59am. I've tried every permutation with failure...

but if geolocation is the reason my night light does not autostart....
then how come geolocation is not a dep or rundep for:
budgie-desktop
budgie-desktop-settings
gnome-control-center?

thanks

    OK, I've ruled out geoclue, it's irrelevant.

    The manual setting negates needing it.

    So...how do I get budgie night light to launch every time I boot up?

    edit:
    anyone have an autostart command?
    or do I have to write some cron confthingy?
    or append a .conf?
    or append a .service?

    OK I'm not crazy:
    MANUAL budgie night light settings was never meant to work automatically.

    (at least according to ubu github and budgie boards; one, to wit: https://github.com/solus-project/budgie-desktop/issues/1817)


    followed by:

    Now my question is changed to "is this 2019 information from Josh still correct?"
    Or can budgie night light be made to auto launch in manual mode now?

    graci

      ReillyBrogan filed at BoB as a request (since I have no idea if autostarting nightlight is feasible per this thread) so will check back and mark solved when I get a response. Dig it.