-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need sudo on Fedora #106
Comments
Try adding yourself to the |
Piotr Zaborowski <notifications@github.com> writes:
Try adding yourself to `plugrev` and retest.
this group doesn't exist, should I create it?
…--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
|
|
Piotr Zaborowski <notifications@github.com> writes:
`plugdev` that is (edited comment on GH but it was to late and
the notification already went out).
doesn't exist either.
…--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
|
Just googled it out. I don't have a Fedrora install to test (nor any friends that would use it). Please run:
Paste in here in a code block or on a pastebin service you prefer. |
|
OK, I tried to replicate it with the OnePlus One we have at the office and failed. I'm pretty sure that either the rules file was not parsed by your udev and/or you'll have to add yourself to the Note that on Fedora there's no default So to ensure that everything is in order we'll follow most of the advise in that thread using
|
|
I just had a similar issue. I found out that I had multiple versions of adb, and the version avaliable on PATH wasn't the right one. May be |
@RSFalcon7 Thanks for the suggestion. I don't think I'm in a similar situation because (1) I just reinstalled my whole system, (2) I installed adb/fastboot from the fedora package manager and from nowhere else, and (3) |
ADB and fastboot are different binaries usually shipped in the same package
(Android SDK has the latest one, use it if you have a USB-C phone).
If you fix the path export for the binaries' directory both ADB and
fastboot should be from there.
…On Wed, Mar 29, 2017, 8:58 PM Rafael Silva ***@***.***> wrote:
I just had a similar issue. I found out that I had multiple versions of
adb, and the version avaliable on PATH wasn't the right one. May be
fastboot is calling a different adb
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAiACpCT8Ok9726_cY0C9yHMrJ7QJ42eks5rqTykgaJpZM4MjhzB>
.
|
Still having this issue on Fedora 34 |
Having same issue on Fedora 35/ Rawhide |
Some differences to note: With Redhat aligned distros - example...Fedora,Centos,Mageia,SuSE, ...try use group "usb". Command 'which' can also help you find which version of adb you are actually using, example: |
I have a bacon phone and a Fedora 25 laptop. I think I did what was required but I still need
sudo
to list devices:I rebooted my laptop but still:
The text was updated successfully, but these errors were encountered: