Issue with permissions to /dev/ttyUSB0, yes I'm in the group

[clytle374]

Problem only exists when not logged in as root. I'm trying to run a program called uTmax that interfaces with a curve tracer board for vacuum tubes called a utracer.
I've had such problems before with not being in the correct group. Or a driver issue which being root doesn't fix. Any suggestions?

Code: Select all

ls -la /dev/ttyU*
crw-rw----+ 1 root plugdev 188, 0 May  9 17:07 /dev/ttyUSB0

Code: Select all

cory@workbench ~ $ groups
wheel audio video docker usb portage plugdev vboxusers cory

I'm using a USB to RS232 converter I've used a lot on other devices, it's not a cheap clone.

Code: Select all

Bus 002 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC

The program does rely on the package dev-qt/qtserialport-6.8.3 if that matters. Lots of references to rfcomm which I can't find data on.

Here is the output of the program

Code: Select all

Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_TLsort_changed()
SerialPortDiscovery: comport= "rfcomm0" available= "ttyUSB0"
SerialPortDiscovery: comport= "rfcomm0" available= "ttyS0"
SerialPortDiscovery: comport= "rfcomm0" available= "ttyS1"
SerialPortDiscovery: comport= "rfcomm0" available= "ttyS2"
SerialPortDiscovery: comport= "rfcomm0" available= "ttyS3"
setting serPortInfo, comport: "ttyUSB0" "rfcomm0"
setting serPortInfo, comport: "ttyS0" "rfcomm0"
setting serPortInfo, comport: "ttyS1" "rfcomm0"
setting serPortInfo, comport: "ttyS2" "rfcomm0"
setting serPortInfo, comport: "ttyS3" "rfcomm0"

When ran as root, I get the same thing that ends with connected.

Code: Select all

Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
qt.core.qmetaobject.connectslotsbyname: QMetaObject::connectSlotsByName: No matching signal for on_TLsort_changed()
QIODevice::write (QFile, "/root/uTmax_files/cal.txt"): device not open
SerialPortDiscovery: comport= "" available= "ttyUSB0"
SerialPortDiscovery: comport= "" available= "ttyS0"
SerialPortDiscovery: comport= "" available= "ttyS1"
SerialPortDiscovery: comport= "" available= "ttyS2"
SerialPortDiscovery: comport= "" available= "ttyS3"
setting serPortInfo, comport: "ttyUSB0" ""
setting serPortInfo, comport: "ttyS0" ""
setting serPortInfo, comport: "ttyS1" ""
setting serPortInfo, comport: "ttyS2" ""
setting serPortInfo, comport: "ttyS3" ""
Open "ttyUSB0"

[bstaletic]

Were you in the plugdev group before you logged into your computer?
If not, you'll have to log out everywhere and log in again, or restart.

[GDH-gentoo]

Code: Select all

ls -la /dev/ttyU*
crw-rw----+ 1 root plugdev 188, 0 May  9 17:07 /dev/ttyUSB0

Note that there is a "+" in the output. There's probably an access control list (ACL), so ls is not telling the full story. Post the output of getfacl /dev/ttyUSB0.

[clytle374]

Were you in the plugdev group before you logged into your computer?
If not, you'll have to log out everywhere and log in again, or restart.

Yes, I even rebooted to be sure.

Code: Select all

ls -la /dev/ttyU*
crw-rw----+ 1 root plugdev 188, 0 May  9 17:07 /dev/ttyUSB0

Note that there is a "+" in the output. There's probably an access control list (ACL), so ls is not telling the full story. Post the output of getfacl /dev/ttyUSB0.

Interesting, that's new territory to me. Here's the output

Code: Select all

 getfacl /dev/ttyUSB0
getfacl: Removing leading '/' from absolute path names
# file: dev/ttyUSB0
# owner: root
# group: plugdev
user::rw-
user:cory:rw-
group::rw-
mask::rw-
other::---

[Hu]

What does strace report to be failing? If we knew specifically which system call fails for your user, we might better understand what to fix.

[clytle374]

What does strace report to be failing? If we knew specifically which system call fails for your user, we might better understand what to fix.

I'm not knowledgeable in the use of strace. It completely overruns the 10000 lines in the buffer in seconds. After a quick search I tried the following options without effect.

Code: Select all

strace ./do_not_run_uTmax -e trace=/dev/ttyUSB0

Code: Select all

strace ./do_not_run_uTmax -P /dev/ttyUSB0

Obviously I don't know what I'm doing there.

[bstaletic]

Try

Code: Select all

strace -o output.log ./do_not_run_uTmax -e trace=/dev/ttyUSB0

and then upload the output.log somewhere for us.

[clytle374]

Try

Code: Select all

strace -o output.log ./do_not_run_uTmax -e trace=/dev/ttyUSB0

and then upload the output.log somewhere for us.

https://drive.google.com/file/d/1ZzCn73 ... sp=sharing

I might really have a problem here. I didn't realize that using the do_not_run was skipping setting a path to local libs. It will not run using them at all. I found the source code to the program and will try that later if all else fails