Closed nebhead closed 2 years ago
It's probably because the service can't be started in user space and is already running at system level, I'll see if I can suppress the message and disable the switch if this is detected, stay tuned
Thanks for looking into this. So if I already have the service running using another method, will this indicator daemon still work?
Probably not, even if I would just leave the systemd controls disabled the config is most likely not located in your user folder, the indicator currently checks for it there to determine how to connect to the daemon. If you can think of a solid way to determine any other locations for it I'll be happy to look into it to help you out.
edit: The passwords shouldn't be a problem, it uses the API key
Probably not, even if I would just leave the systemd controls disabled the config is most likely not located in your user folder, the indicator currently checks for it there to determine how to connect to the daemon.
Ah... got it. OK. I can't offer any clever solutions on this one unfortunately.
edit: The passwords shouldn't be a problem, it uses the API key
Great. OK. So perhaps I need remove my current install and then enable this method instead. Thanks! I will got ahead and close this issue. Thanks again for looking into it.
The service is running, which I can access via my browser, but I'm wondering if it's because I have it password protected that the indicator daemon cannot access it?