Using Xubuntu 16.04 and default-jre from the repositories.
I can connect to my blue tooth adapter if i run the program as Sudo otherwise no matter what permissions or groups i add my regular user to i can not get TS to detect my ecu via bluetooth
this is what i get when i run as regular user:
RXTX fhs_lock() Error: creating lock file: /var/lock/LCK..OM1: File exists
I have tried chmod 777 to /var/lock as well as /run/lock with no luck
I have seen this issue for other people as well but never saw a fix. Do i just have to always run TS as using SUDO?
LOCK file error
Moderator: LT401Vette
-
- Super MS/Extra'er
- Posts: 12732
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: LOCK file error
Sounds like a typical permissions issue.
What groups have you added your user to?
uucp, lock, dialout
Also worth noting, with the beta TS you should need to add the user to a group.
What groups have you added your user to?
uucp, lock, dialout
Also worth noting, with the beta TS you should need to add the user to a group.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
Re: LOCK file error
output of groups of username
adm uucp dialout cdrom sudo dip plugdev netdev lpadmin sambashare
i though the same thing but rfcomm is part of the dialout group so i don't believe that is the issues, i think the issue lies in creating the lock file in /var/lock but no matter what i do i cant control it outside of invoking sudo.
adm uucp dialout cdrom sudo dip plugdev netdev lpadmin sambashare
i though the same thing but rfcomm is part of the dialout group so i don't believe that is the issues, i think the issue lies in creating the lock file in /var/lock but no matter what i do i cant control it outside of invoking sudo.