Question

1

Why did systemd decide to start adb

rated 0 times [ 1] [ 0] / answers: 1 / hits: 1131 / 1 Year ago, sun, may 28, 2023, 3:52:17

I have an Ubuntu 20.04.1 LTS system.

This system, has NEVER had an Android device connected to it, via USB.

Still, to my surprise, I see that adb is running:

# ps -efa | grep adb

bram       72062    1421  0 Oct29 ?        00:04:07 adb -L tcp:5037 fork-server server --reply-fd 7

And the PPID is the systemd process.

Now... why did systemd decide to fire up a server for adb? I never asked for this to happen?

(Kudos to powertop, btw, for highlighting adb, which shows up as an energy waster, to boot!)

Does Ubunutu LTS have adb enabled as a server, by default? I find that hard to believe? Why? Just in case the user has an Android phone?

How can I disable adb from getting launched automatically?

UPDATE:

$ systemctl status adb.service

Unit adb.service could not be found.

After a reboot, the adb process did not come back.

Further examination revealed that adb was started by systemd on behalf of renderdoc and renderdoc leaves it running after exit.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

whipstder

Add To Favorites

Follow

Total Points: 189

Total Questions: 110

Total Answers: 99

Location: Uzbekistan

Member since Sat, Feb 27, 2021

3 Years ago

whipstder questions

1 Ubuntu 22.04 not booting after I installed nvidia drivers

Wed, Nov 9, 22, 09:45, 2 Years ago

1 bad cmake executable vscode

Tue, Sep 14, 21, 10:54, 3 Years ago

1 Cannot install pip module because there is 'no space' left on device

Wed, Feb 2, 22, 01:41, 2 Years ago

1 Cannot save files in Kdenlive snap, why not?

Sat, Jul 17, 21, 07:10, 3 Years ago

1 Merlin U740 USB 2.0 camera not working

Thu, Sep 2, 21, 07:15, 3 Years ago

View All

answered 1 Year ago antorchestr · Accepted Answer

It turns out that adb, even though started by systemd, was started by a request from the renderdoc tool.

I had an old copy of adb in my user's bin directory, where it got picked up by renderdoc.

After exiting renderdoc, the adb server is left up.

So adb is not brought up at boot time, but at renderdoc's request. This is because the tool can capture both local GPU streams as well as remote ones from Android devices.