http://bugs.winehq.org/show_bug.cgi?id=58594
Bug ID: 58594 Summary: Teraterm 5.4.1 / Serial communication not functional Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: janne.kekkonen@gmail.com Distribution: ---
Tested with Wine 10.12 on Ubuntu 22.04 running on VMware.
When data is sent to serial port teraterm GUI become sluggish/unusable. Menu's do not work and data sent to serial port is not shown. When data sending is stopped GUI starts to work normally and data is shown on terminal.
Functionality is pretty much the same as in bug-58142
Tests steps: - Connect USB-serial port to system. - Open serial port with teraterm & set settings(baud,stop bits...) - Start sending data to serial port. - Try to open menus.
Not sure is this possible to reproduce with virtual serialport(s)
Download link: https://github.com/TeraTermProject/teraterm/releases/download/v5.4.1/terater...
http://bugs.winehq.org/show_bug.cgi?id=58594
Janne janne.kekkonen@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://github.com/TeraTerm | |Project/teraterm/releases/d | |ownload/v5.4.1/teraterm-5.4 | |.1.exe
http://bugs.winehq.org/show_bug.cgi?id=58594
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |serial Keywords| |download
http://bugs.winehq.org/show_bug.cgi?id=58594
--- Comment #1 from Janne janne.kekkonen@gmail.com --- Created attachment 79130 --> http://bugs.winehq.org/attachment.cgi?id=79130 script that writes to serialport
It seems to be possible to reproduce issue with virtual serial port.
I created two virtual ports with command:
socat -d -d pty,raw,echo=0 pty,raw,echo=0
I added COM3 as dev/pts/2 to wine registry. Opened com3 with teraterm and used script to write to port /dev/pts/1 with 1 second interval.
While script is running GUI is somewhat sluggish and data is seen on terminal with 1-3s intervals.
http://bugs.winehq.org/show_bug.cgi?id=58594
--- Comment #2 from Ken Sharp imwellcushtymelike@gmail.com --- Is there a reason you have opened a duplicate bug report? Is this fundamentally different from Bug 58142?
http://bugs.winehq.org/show_bug.cgi?id=58594
--- Comment #3 from Janne janne.kekkonen@gmail.com --- Based on tests both versions seem to behave in similarly. I thought that i open bug for this version also. Maybe this can be closed as duplicate.
http://bugs.winehq.org/show_bug.cgi?id=58594
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
--- Comment #4 from Ken Sharp imwellcushtymelike@gmail.com --- Indeed there is no need to open separate bug reports for applications that experience the same issue.
*** This bug has been marked as a duplicate of bug 58142 ***
http://bugs.winehq.org/show_bug.cgi?id=58594
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #5 from Zeb Figura z.figura12@gmail.com --- (In reply to Ken Sharp from comment #4)
Indeed there is no need to open separate bug reports for applications that experience the same issue.
*** This bug has been marked as a duplicate of bug 58142 ***
To be fair, the "same issue" is not always clear. Two unrelated games that both launch to a black screen are almost never the same issue. Two versions of the same program that fail in the same way probably are. There's a lot of middle ground.