Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Weird user permission problem using client on Linux #159
From #133 (comment):
It seems to be something else over here.
I have a new machine, so I reinstalled KUbuntu and also the OlsClient from scratch.
For normal users I get a
When I do a
I can use the device as a normal user again.
I used to point the OlsClient to a symlink to my device that I create with a simple udev rule
setting the ComboBox to
One of the weird features of udev rules is that
When I use
... the OLS client accepts
But this issue here can be closed as invalid I think.
I am using this and it works for root and that username... usually.
The interesting behavior starts when i reset the OLS while (non-root) capturing (to be more precise: while the clients waits while the trigger condition has not happened yet). After that it is no longer possible to access the OLS with the non-root user. Not even after resetting the OLS and restarting the client! I get the following when trying to fetch the metadata in the begin capturing dialog:
Most interestingly: when I launch the client as root afterwards and fetch the metadata once it starts working for the non-root user too! So it seems like the root access sanitizes some part of the stack again which does not work without root rights (bug in purejavacomm?). The behavior is not completely consistent and reproducible for me yet. I am using linux 3.8 ATM.
That is true for the the first (faulty) version of the udev rule using
The corrected version
works only for root on my system:
i have not investigated further, but i just found this purejavacomm issue fix which remotely looks interesting. nyholku/purejavacomm#10
also, with the current code (206d4fa) my workaround of running it as root does no long work because of a NPE:
@stefanct : it appears that your mentioned fix was already incorporated in an earlier release of PureJavaComm. Fortunately, there's a new version just released, which at least has fixed some of the issues on Linux. I want to give it a test-drive myself soon, in which I'll try to reproduce the behaviour of this issue again as well...
Same Prob. on a new installed Ubuntu 12.04!
$ ll /dev/ttyACM0
Seems that latest version of PureJavacomm helps...
Many Thanks, ToM