Are there any known side affects of disabling


As I continue to tune my Gnome Endeavor machine I noticed a service which I feel is unnecessary (the ‘geoclue.service’). I’ve been searching the various wiki’s and arch forums to see if I could find anything. So I thought I would handshake with our community to see if there is any advice.

I’ve also stolen\re-written some notes on how to do this just in case someone asks the same question as myself. Thank you.

Linux | How to disable geoclue.service in Gnome Arch Linux

On a Linux Gnome you can safely neuter geoclue.service by disabling the service and masking it.

Do the following:

(1) Elevate your system privileges via ‘sudo’ command and run the following commands in Terminal:

sudo systemctl disable geoclue.service
sudo systemctl mask geoclue.service

(2) Reboot you system and use the following commands in terminal to make sure service is disabled:

sudo systemctl status geoclue.service

Expected Output:

$ sudo systemctl status geoclue.service
● geoclue.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)


You can disable such services such as geoclue, bluetooth etc if you are not going to use them. Just remember that you have done so in case you need them in the future. Please be careful not to disable any services that are critical to your system. In other words read carefully before doing so! :slightly_smiling_face:

Thanks for your feedback.

Do you have a recommendation on where I can get a list of various system services in EOS\Arch Linux and what they do? I’m trying to avoid searching across the internet to find a consolidated opinion.

I known I can run ‘systemctl’ from terminal to list the services I have installed.

That’s beyond my knowledge. I just turn off the obvious ones from starting up eg. the ones I know I’m not going to be using. As far as going really minimal that would depend on the setup of your own system and what you intend to be using it for. I don’t think it is possible to be completely specific, there are no definite rules for that. You need to research and draw your own conclusions to what is right for you. Like in life itself: nothing is certain. Anyone who tells you otherwise is either a fool or a liar. :wink:

1 Like

No problem (thank you). When I work in the Windows Server are we have documentation to reference to look up the various servce and what they do and what they are for. This is how I figure out what I might shut off after researching the dependencies.

BTW I am not targeting my boot time, just trying to stay lean. If I was targetting boot time then I would use:

(1) To get the actual boot time:

(2) Find out the time for each service:
systemd-analyze blame


You are on the right track. Keeping it lean and approaching the issue in a logical and considered manner. It’s the right way and I am sure you will draw the correct conclusions for your specific case. Number one rule of course: before you do anything major, Backup! :laughing:

This should cover most bases:


And then there is always:
man systemctl