-
Notifications
You must be signed in to change notification settings - Fork 82
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
Module not working! #15
Comments
Well this is rather a system python environment configuration issue. |
Well, it's true, but editing that line you avoid this problem on any system... |
Is that a fact? And what about fresh systems that have python3 as default? Now that I look at your first message, it's not 100% clear what the exact change is. I cannot be sure I'm reading the situation correctly. |
Well... If you have both python and python2 installed on your system python (3) will be chosen. If you edit the line /usr/bin/env python to /usr/bin/env python2 the script will choose python2 and works fine. |
Same situation here on a Ubuntu running 3.8.0 linux kernel |
I don't think setting that line to "python2" could ever be interpreted as using python3. |
Hi, yesterday I tried to use the pam module but nothing was working :/
So I decided to edit the config file /usr/bin/pamusb-conf to try to solve the error.
And .... Error solved! Simply edit the first line to make the script to use python2, instead of python.
I hope you can fix this project in a short time.
Bye
Amedeo
The text was updated successfully, but these errors were encountered: