Linux: selecting tty device fails | auto open does work
Maintainers usually reply within 7 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- operating-systems
Research direction
Start with configure.py and reproduce the difference between selecting ttyACM0 and auto-detection, which returns /dev/ttyACM0. Trace the selected value into serial-port opening and verify that saving a selected device preserves the correct path and allows the screen to start.
Written by the indexing model from the issue text.
Description
Describe the bug
Selecting a specific tty device fails to open. Auto-open does work
To Reproduce
Steps to reproduce the behavior:
- run
python3 configure.py - selct the tty device
- save and run
Expected behavior
Open the tty device with the correct path.
Logs
(.venv)user@host turing-smart-screen-python][(HEAD 3.9.6)]$ 08.11.2025 19:48:06 [INFO] Loading theme Digital_CPU_0.96Inch from res/themes/Digital_CPU_0.96Inch/theme.yaml
08.11.2025 19:48:06 [DEBUG] Static COM port: ttyACM0
08.11.2025 19:48:06 [ERROR] Cannot open COM port ttyACM0: [Errno 2] could not open port ttyACM0
^C
(.venv)user@host turing-smart-screen-python][(HEAD 3.9.6)]$ python3 configure.py
(.venv)user@host turing-smart-screen-python][(HEAD 3.9.6)]$ 08.11.2025 19:48:26 [INFO] Loading theme Digital_CPU_0.96Inch from res/themes/Digital_CPU_0.96Inch/theme.yaml
08.11.2025 19:48:26 [DEBUG] Auto detected COM port: /dev/ttyACM0
Environment:
- Smart screen model [e.g. Turing 5", XuanFang 3.5”]
- Revision of this project: 3.9.6
- OS with version: Archlinux
- Python version [e.g. Python 3.10]
- Hardware: x86
Additional context
The path handling is not correct. The drop down menu misses the /dev/ path in front.
- Dominant language
- Rich Text Format
- Stars
- 2.3k
- Forks
- 419
- Avg merge
- 4d 35m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mathoudebine/turing-smart-screen-python
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mathoudebine/turing-smart-screen-python#1048 ·
Maintainers usually reply within 7 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mathoudebine/turing-smart-screen-python#1031 ·
Maintainers usually reply within 7 days
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
mathoudebine/turing-smart-screen-python#557 · 2 comments · 3 reactions ·
Maintainers usually reply within 7 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
mathoudebine/turing-smart-screen-python#1093 ·
Maintainers usually reply within 7 days
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
mathoudebine/turing-smart-screen-python#1090 · 2 comments ·
Maintainers usually reply within 7 days
All issues in mathoudebine/turing-smart-screen-python
Similar issues
-
component:skillfs
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
agentic-os-org/ANOLISA#4609 · 1 comment ·
Maintainers usually reply within 1 day
-
Improve Task Cache Windows Registry events to carry the task subkey's last written time and key pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
log2timeline/plaso#5299 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
ubuntu/Tiling-Assistant#481 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day