Open amo13 opened 2 years ago
Also:
ADB command kill-server gave an unexpected error: stdout: ; stderr: Password: **** is not in the sudoers file. This incident will be reported.
Though this error actually could be caught and reported to the user. This is probably simply a linux (or bsd?) system without sudo.
Not sure if this error is related
Bug: sudo password prompt instead of command output. Killing adb server and retrying kill-server
Stderr contains [sudo]
but running the command with sudo
works fine, (not sure why the need to provide the sudo pass in the dialog if the command is running with sudo anyway)
Providing the sudo password in the dialog is preferred rather than running the whole application with sudo. This way, if the application has a bug, it will not misbehave with sudo-rights on your system. The even more preferred way is to configure udev rules for your device (on archlinux, this is done by simply installing the package android-udev
).
I used it on Ubuntu 20.04, without sudo the application would just throw endless errors as above, with sudo it worked fine so the error above should be some indication as to why that is.
in
adb.State()
(and:
Unknown ADB error: [sudo] password for amo:
inadb.unavailable()
)