On Wed, Jan 23, 2019 at 12:01 AM Jeffrey Nichols wrote:
>
> Isuue 1: This is normal for python scripts. You can easily uninstall and
> reinstall the package to revert your changes.
Just to add to what Jeff wrote: The library files can be -rw-r--r--
which means they are writeable for owner (root in
Isuue 1: This is normal for python scripts. You can easily uninstall and
reinstall the package to revert your changes.
Issue 2: The permission errors have nothing to with the script or
library permissions, only the USB device. You cannot fix the /dev/
permissions through chmod, so don't try.
W
ok, I took on board your comment about install python3-usb which includes
pyusb.
I reinstalled the raspbian OS and installed python3-usb ... it puts the
files in quite different places, but the same files.
Issue 1) again a number of files (e.g.
'usr/lib/python3.5/dist-packages/usb/backend/libusb1
On Tue, Jan 22, 2019 at 12:11 AM charles wilson wrote:
> Looks we are the same page ... yes I will tidy up permissions later ... and
> the issue relates to the python version. I downloaded pyusb not python-usb"or
> "python3-usb.
>
Unless you know exactly what you are doing, or really need a newe
Hi Tormod & others
Looks we are the same page ... yes I will tidy up permissions later ... and
the issue relates to the python version. I downloaded pyusb not
python-usb"or "python3-usb.
But I am winning! yes although still need help.
My process has been as follows (bear in mind I have the sa
Looks to me like a device permission issue. I suspect that chmod on
/dev/usb won't do what you want. Some distros have a usb group that you
can add your user to. I usually end up setting up a udev rule, though.
My best guess on the root/sudo thing is your user's site-packages aren't
being read
On Mon, Jan 21, 2019 at 5:28 AM charles wilson wrote:
> On permissions, I had checked/changed permissions previously but re-checked
> and found a missed one in /python3.5/site-packages/usb/backend- happened to
> be libusb1.pywhich was flagged - all fixed now
> I had also not checked the /dev/*US
Hi Jacques, the type of device makes no difference I have tried with range
of devices, keyboard, usb HDD, robotic interface all with the same
results
Cheers
Charles
On Mon, 21 Jan 2019 at 19:34, Jacques-D. Piguet
wrote:
> Hi Charles,
>
> What kind of device are you trying to communicate wi
Hi Charles,
What kind of device are you trying to communicate with?
Regards, Jacques-D.
On 21.01.19 05:23, charles wilson wrote:
Hi Guys,
Thanks for your time and feedback; it's taken awhile to get back to this.
On permissions, I had checked/changed permissions previously but
re-checked and
Hi Guys,
Thanks for your time and feedback; it's taken awhile to get back to this.
On permissions, I had checked/changed permissions previously but re-checked
and found a missed one in /python3.5/site-packages/usb/backend- happened to
be libusb1.pywhich was flagged - all fixed now
I had also not ch
i saw this message:
usb.core.USBError: [Errno 13] Access denied (insufficient permissions)
when i was using a wrong driver in Windows 10. I could also see the whole
usb device descriptor, just could not interact with it.
my suggestion is to try to re install or update the libusb driver
On Thu,
>usb.core.USBError: [Errno 13] Access denied (insufficient permissions)
Run your script with sudo? Or add a udev rule so your regular user
also has access.
On Fri, Jan 18, 2019 at 5:01 AM charles wilson wrote:
>
> Hi,
> I usually manage to solve my problems by hitting my head against them until I
12 matches
Mail list logo
