wine-bugs February 2020

wine-bugs@winehq.org

1 participants
7232 discussions

[Bug 19713] New: Some serial port communication functions behave differently in Wine and Windows.
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=19713 Summary: Some serial port communication functions behave differently in Wine and Windows. Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fenixk19(a)mail.ru Created an attachment (id=23025) --> (http://bugs.winehq.org/attachment.cgi?id=23025) Test program This makes test program to hang in Wine, but in MS it is ok. Test program attached. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 43

[Bug 37846] New: Communication broken using FTDI USB Serial Device converter (FT232RL) / Mostly send using CS-51PLUS
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=37846 Bug ID: 37846 Summary: Communication broken using FTDI USB Serial Device converter (FT232RL) / Mostly send using CS-51PLUS Product: Wine Version: 1.7.30 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lgeorgieff(a)gmail.com Distribution: --- Created attachment 50402 --> https://bugs.winehq.org/attachment.cgi?id=50402 WINEDEBUG="+comm" wine .wine/drive_c/Program\ Files\ $x86$/Icom/CS-51PLUS/CS51PLUS.exe log Hi, I am using FTDI USB Serial Device converter to program ham radio. Cable have FT232RL chip and software is CS-51PLUS. Reading from radio is OK but when I try to write (send) configuration to the radio communication is broken after while and I get error message. The same cable and software on the same machine runs without problems on QEMM's virtual windows. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 13296] New: regression problem in upgrade to Ubuntu Hardy/1.0-rc1: Palm Hotsync over serial Segmentation Fault
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=13296 Summary: regression problem in upgrade to Ubuntu Hardy/1.0-rc1: Palm Hotsync over serial Segmentation Fault Product: Wine Version: 1.0-rc1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jan-winehq(a)h-i-s.nl Created an attachment (id=13150) --> (http://bugs.winehq.org/attachment.cgi?id=13150) Logging output I upgraded to Ubuntu Hardy, and wine 1.0-rc1. Hotsync manager 1.0 for Palm Pilot worked fine before. http://appdb.winehq.org/objectManager.php?sClass=version&iId=10362 Now it crashes half-way synchronising over the serial port, sometimes after a few seconds, sometimes much later in the process. These crashes reproduce well, and yield a segmentation fault without further information $ wine hotsync.exe Segmentation fault $ I do not know if this means that a part of Wine crashes, or just the application. I added logging, where it seems that the problem lies within the call below: 0009:CallTo16(func=111f:072a,ds=1087,118f,7404,0000,0006) ss:sp=1087:ffd0 I am not sure if the problem lies with wine, or that other problems with Ubuntu Hardy may relate to this. It is disappointing that an application that used to work fine, and I came to depend on, is now broken. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 19

[Bug 25083] New: HyperTerminal unable to loop back on COM1 (RS-232)
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=25083 Summary: HyperTerminal unable to loop back on COM1 (RS-232) Product: Wine Version: 1.3.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: graham(a)nerve.org.za On a machine with an on-board RS-232 port at COM1, HyperTerminal (as shipped with Windows XP) is firstly unable to detect the port until changes are made in the WINE registry, thereafter, after attaching a simple loopback adapter (pins 2 and 3 of a DB9F shorted) no characters are echoed to the screen. Obtaining the software: >From a Windows XP installation, copy the files hypertrm.exe and htrn_jis.dll from 'C:\Program Files\Windows NT' and hticons.dll and hypertrm.dll from C:\Windows\System32' into a suitable directory below .wine/drive_c or Download a free 30 day trial of HyperTerminal Private Edition 7.0 from http://www.hilgraeve.com/hyperterminal/ Create a symbolic link for COM1, documented here: http://www.winehq.org/docs/wineusr-guide/misc-things-to-configure ln -s /dev/ttyS0 ~/.wine/dosdevices/com1 At this point, starting HyperTerminal will result in no serial ports being shown. Now, create a registry entry in WINE for the serial port, mentioned in this bug report: http://bugs.winehq.org/show_bug.cgi?id=4282 Add the following lines to .wine/system.reg [Hardware\\Devicemap\\SerialComm] "Serial0"="COM1" Now HyperTerminal can be started, COM1 can be selected and configured, but no characters are echoed to the screen. However, the free terminal program, simply named 'Terminal' and available here: https://sites.google.com/site/terminalbpp/ Does echo characters to the screen. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 23

[Bug 47873] New: kernel32:comm fails randomly
by WineHQ Bugzilla 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=47873 Bug ID: 47873 Summary: kernel32:comm fails randomly Product: Wine Version: 4.17 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:comm fails randomly on multiple Windows versions: comm.c:708: Found Com port COM1. Connected devices may disturb results comm.c:859: Test failed: WaitCommEvent failed with a timeout comm.c:870: recovering after WAIT_TIMEOUT... comm.c:880: Test failed: WaitCommEvent error 0 comm.c:881: Test failed: WaitCommEvent: expected EV_TXEMPTY, got 0 comm.c:885: WaitCommEvent for EV_TXEMPTY took 1500 ms (timeout 1500) comm.c:886: Test failed: WaitCommEvent used 1500 ms for waiting https://test.winehq.org/data/tests/kernel32:comm.html These failures are random and have been seen on the following TestBot VM4 configurations: wxppro w2003std w7pro64-32 w1064v1507-32 w1064v1607-32 w1064v1607-64 w1064v1709-64 w1064v1607-64 w1064v1809-32 w1064v1809-32 w1064v1809-64 w1064v1809-2scr-32 w1064v1809-fr-64 w1064v1809-ja-32 w1064v1809-ja-64 So it does not depend on the Windows version, bitness of the test, or locale. However it only happens on QEmu VMs: it never happened on the fg-win7u64 VMware VMs or on the real hardware machines, cw-rx460 and cw2-gtx560. Yet the VMware VMs have two serial COM ports, and, according to dmesg | grep tty, the real hardware machines do have a serial port too. QEmu bug? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 46676] New: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=46676 Bug ID: 46676 Summary: Serial port enumeration (get device description) on Mac OS/X 10.9, 10.13 Product: Wine Version: 4.0 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: martin(a)hinner.info Created attachment 63628 --> https://bugs.winehq.org/attachment.cgi?id=63628 suspected problematic function Tested on: Mac OS/X 10.9, 10.13 WineBottler (Wine 1.8) works fine; Wine 4.0 (from .pkg) does not work Our application is trying to enumerate serial ports by using setupapi functions. I have not checked where exactly is the problem as debugging on OS/X is a bit difficult for me, however suspected function is attached (it's goal is to get device description). The affected apps are http://obdtester.com/ficom , http://obdtester.com/bimcom , http://obdtester.com/fcom ; I have tried to create symlink in dosdevices (required for WineBottler to get it working), one OS/X 10.13 my link got deleted everytime I ran the app; on OS/X 10.9 link persisted, but not possible to enumerate any serial port(s). I can provide login for download by personal e-mail (not to be disclosed). I have talked about this on wine mailing list a long time ago, it would be super easy if Wine-enabled application can have a way to load system native .so to talk directly to the host system, I have many examples of device drivers that would be super easy to implement. FYI I have already written "winegate.dll.so" which solves this real world problem, but it was rejected for submission to Wine because of "Wine must be 100% transparent" ideology. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 9

[Bug 10051] New: Parallax SX Key IDE cannot detect serial port under WINE
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=10051 Summary: Parallax SX Key IDE cannot detect serial port under WINE Product: Wine Version: 0.9.46. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-setupapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: ultimatedevr(a)yahoo.com Created an attachment (id=8599) --> (http://bugs.winehq.org/attachment.cgi?id=8599) Result of running SXKey.exe in wine with the +setupapi debug flag. I am trying to run the Parallax SX Key IDE through WINE, however the IDE does not detect any of my serial ports. I have symlinked them to ~/.wine/dosdevices/ and added them to my registry, however the IDE still cannot detect my serial ports. I am currently running WINE v.0.9.46 (the same problem exists in the CVS version as well). (BTW, I have heard of others getting this to work, yet others who couldn't: http://forums.parallax.com/forums/default.aspx?f=15&m=217429&g=221692) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 23

[Bug 23326] New: Cannot change printer settings, Family Tree 7
by wine-bugs＠winehq.org 24 Jul '23

24 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=23326 Summary: Cannot change printer settings, Family Tree 7 Product: Wine Version: 1.2-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jamesl(a)bestweb.net Created an attachment (id=29072) --> (http://bugs.winehq.org/attachment.cgi?id=29072) FTW7 print dialogue, compare Wine to XP Cannot select printer/change print settings with Family Tree Maker 7. Dialogue box comes up, drop-down boxes are working, but radio buttons for switching between "default printer" and an alternate printer are not selectable. Have compared the print dialogue between Wine vs a native install under Windows XP (SP3) and notice some text from the Windows install does not show up under Wine. Also tried the same thing with the "free" version of FTM2005se available at http://past.familytreemaker.com/download/starter.aspx and found it's behavior is the same. So I will describe steps from there, since it would be eaier for someone to get that to test against. STEPS TO RECREATE: 1: Set up wine profile with "WINEPREFIX=/home/jelabarre/wine-apps/ftw2005 winecfg"; set winver to "Windows XP", point the Documents directory under Desktop Integration to my own Documents directory 2: install FTW2005 by running "WINEPREFIX=/home/jelabaWINEPREFIX=/home/jelabarre/wine-apps/ftw2005 wine ./FamilyTreeMaker2005se.exe", accept all defaults. 3: open FTW 2005 from "Wine" menu entry on Gnome menu. Selected "Buy Later" from popup window (does not affect outcome, as same print problem occurrs in a regular retail version of FTM7) 4: create new file, or use existing file (same result either way) 5: select "File | Print Setup", then try to select radio button for either "Default Printer" or "Specific Printer". Neither can be selected 6: try selecting a "specific printer" from drop-down box. Printer can be selected, but radio buttons still not functional. 7: after selecting a printer other than the default (such as print-to-PDF) and then try printing. Output will still go to the Linux default printer, no edits of the print settings will take effect. The "Family Archive Viewer v6.0" at http://familytreemaker.genealogy.com/abtffiv.html and "Family Archive Viewer v11.0" at http://www.genealogy.com/abtffiv.html are other variants that exhibits this behavior. Have attached sample screenshots of Wine vs WinXP versions of the print dialogue. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 15

[Bug 30155] New: secdrv.sys from SafeDisc v2.05.030 does not work
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=30155 Bug #: 30155 Summary: secdrv.sys from SafeDisc v2.05.030 does not work Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: stefan(a)codeweavers.com Classification: Unclassified Created attachment 39336 --> http://bugs.winehq.org/attachment.cgi?id=39336 service,relay,winedevice,ntoskrnl log SafeDisc 2.05.030 does not work out of the box. The user-visible symptom is that the application exits with exit code 0 without any output. This affects for example the Command and Conquer Red Alert 2 installer, which is safedisc protected for some reason. The problem seems to be related to the specific secdrv.sys version. If I take a secdrv.sys from a newer safedisc version(e.g. 2.40.010 from the RA2 Yuri's revenge expansion) and put it in C:\windows\system32\drivers, the installer works. ProtectId says: Scanning -> D:\Setup\Setup.exe File Type : 32-Bit Exe (Subsystem : Win GUI / 2), Size : 1308863 (013F8BFh) Byte(s) -> File has 733375 (0B30BFh) bytes of appended data starting at offset 08C800h [File Heuristics] -> Flag : 00000000000000000100000000100111 (0x00004027) [!] Safedisc v2.05.030 detected ! [i] Appended data contents.... [.] o: 0x0008C828 / t: <0x00000001> <0x00000000> <0x00000001> / s: 00194947 byte(s) -> ~de7bc4.tmp [.] o: 0x000BC1D2 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00030208 byte(s) -> clcd32.dll [.] o: 0x000C37F9 / t: <0x00000001> <0x00000000> <0x0000044C> / s: 00006784 byte(s) -> clcd16.dll [.] o: 0x000C529D / t: <0x00000001> <0x00000000> <0x0000044D> / s: 00067584 byte(s) -> mcp.dll [.] o: 0x000D5AC5 / t: <0x00000001> <0x00000000> <0x00000000> / s: 00327220 byte(s) -> ~df394b.tmp [.] o: 0x00125920 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00034304 byte(s) -> drvmgt.dll [.] o: 0x0012DF47 / t: <0x00000001> <0x00000000> <0x00000002> / s: 00018768 byte(s) -> secdrv.sys [.] o: 0x001328BF / t: <0x00000001> <0x00000000> <0x00000000> / s: 00053248 byte(s) -> ~ef7194.tmp [CompilerDetect] -> Visual C++ 6.0 - Scan Took : 0.640 Second(s) The md5sum of the broken secdrv.sys is XXX. The md5sum of the working 2.40.010 driver is f376a1580204e47f37a721e1cbc5582a. I am attaching a +relay,+service,+winedevice+ntoskrnl log of a failed run of the setup tool. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 32

[Bug 44823] New: Steam doesn' t close on exit. Will continue running in background.
by wine-bugs＠winehq.org 23 Jul '23

23 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=44823 Bug ID: 44823 Summary: Steam doesn't close on exit. Will continue running in background. Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Created attachment 60857 --> https://bugs.winehq.org/attachment.cgi?id=60857 Steam system information and version Running the latest Steam client, I find that Steam doesn't actually close entirely after I exit normally with Steam>Exit. I have to open System Monitor and kill all steam and wine related processes. I can't open steam again until I do so, and the Steam.exe and wineserver processes chew 17% of my CPU each in the background until I do so. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs February 2020