March 2023 - Wine-bugs - list.winehq.org

[Bug 52162] New: Ubuntu windows program has com1 the PIC micro programmer has usb device shows on /dev/ttyUSB0
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52162 Bug ID: 52162 Summary: Ubuntu windows program has com1 the PIC micro programmer has usb device shows on /dev/ttyUSB0 Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: usb Assignee: wine-bugs(a)winehq.org Reporter: mw0sbx(a)hotmail.com Distribution: --- marc(a)SPUPERMICRO-X9DRH-iF:~/.wine/drive_c/windows$ wine --version wine-5.0 (Ubuntu 5.0-3ubuntu1) Ubuntu - windows program has COM1 the PIC micro programmer has usb leed the device shows up using dmesg -w as /dev/ttyUSB0 program is called MicroPro.exe tried editing the wine registry as stated online by adding HKEY local machine >>> software >> wine >> ports string value COM1 >> DATA /dev/ttyUSB0 dmesg -w [ 2059.674461] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2059.674466] usb 2-1.2: Product: USB <-> Serial [ 2059.674469] usb 2-1.2: Manufacturer: FTDI [ 2059.675373] ftdi_sio 2-1.2:1.0: FTDI USB Serial Device converter detected [ 2059.675448] usb 2-1.2: Detected FT232BM [ 2059.675906] usb 2-1.2: FTDI USB Serial Device converter now attached to ttyUSB0 Still doesn't work no matter what i try program keeps reporting problem with coms port. -- 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 13

[Bug 52081] New: usbip: error: vhci driver is not loaded
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52081 Bug ID: 52081 Summary: usbip: error: vhci driver is not loaded Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- When trying to install and use the usbip-win client https://github.com/cezanne/usbip-win/releases/download/v0.3.5/usbip-win-0.3… trying to attach a remote usb device fails with the usbip: error: vhci driver is not loaded This happens with the released version of usbip-win v0.3.5 as well as with a self-compiled version of usbip-win where the has_certificate function is disabled. Below are the steps to reproduce. In order to test this, are usbip server (in my case this is on "donglerasp") where "usbipd -D" is running and a usb device is exported with usbip bind --busid=1-1.2.3 $ wine usbip.exe install -w usbip: error: root driver already exist 0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FC20 $ wine usbip.exe list -r donglerasp Exportable USB devices ====================== - donglerasp 1-1.2.3: unknown vendor : unknown product (0529:0001) : /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2.3 : unknown class / unknown subclass / unknown protocol (ff/00/00) : 0 - unknown class / unknown subclass / unknown protocol (ff/00/00) 0100:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FC20 $ wine usbip.exe attach -r donglerasp -b "1-1.2.3" usbip: error: vhci driver is not loaded 0118:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FC20 -- 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 19

[Bug 34497] New: ProAIS2 Serial Port enumeration requires Registry Local_Machine/…/Enum/SERIAL/COM1/COM1/*
by wine-bugs＠winehq.org 25 Jul '23

25 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=34497 Bug #: 34497 Summary: ProAIS2 Serial Port enumeration requires Registry Local_Machine/…/Enum/SERIAL/COM1/COM1/* Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winehq(a)paul.sladen.org Classification: Unclassified ProAIS2 (Marine AIS software from SRT in the UK, and re-badged by large numbers of OEMs) performs Serial Port detection by enumerating the registry. The following keys need to be added: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\SERIAL\COM1\COM1] "ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}" "FriendlyName"="Serial Port (COM1)" "PortName"="COM1" in addition to the matching ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1 If only the ClassGUID/FriendlyName are set, then the port will be found, but immediately switched to in-case. PortName is being prefixed with "\\.\" ("\\\\.\\") to form "\\.\COM1". Kudos to Doug Brown for tracking down most of the issue: http://www.downtowndougbrown.com/2013/03/getting-x-ctu-in-wine-to-detect-yo… -- 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 8

[Bug 49972] New: Termie 1.0 crashes after selecting a serial port.
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49972 Bug ID: 49972 Summary: Termie 1.0 crashes after selecting a serial port. Product: Wine Version: 5.18 Hardware: x86-64 URL: http://termie.sourceforge.net/#downloads OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: ArchLinux Created attachment 68373 --> https://bugs.winehq.org/attachment.cgi?id=68373 Console messages Summary Termie 1.0 crashes after selecting a serial port. Download location http://termie.sourceforge.net/#downloads http://termie.sourceforge.net/Termie-1.0-Binary.zip $ sha256sum Termie-1.0-Binary.zip 53469ffdb38058b985482cbfac3f4c0575eeafa4e1b766b5f0c2af43acb7cba6 Termie-1.0-Binary.zip $ unzip Termie-1.0-Binary.zip Steps to reproduce: 1)Start the program: $ wine Termie.exe After a long time (+- 20 seconds) the program opens. 2) Select one of the comm port. Now the program crashes. 3) Press ctrl-c in the console to kill wine. 4) restart Termie. $ wine Termie.exe Now wine gives this error. "[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.IOException: Broken pipe." Every time Termie is restarted via step 3, it crashes the same way. My versions $ wine --version wine-5.18 (Staging) $ pacman -Q wine wine-staging 5.18-1 uname -a Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000 x86_64 GNU/Linux -- 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 2

[Bug 49974] New: termite-3.4 can't connect to com5 -> /dev/ttyACM0
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49974 Bug ID: 49974 Summary: termite-3.4 can't connect to com5 -> /dev/ttyACM0 Product: Wine Version: 5.18 Hardware: x86-64 URL: https://www.compuphase.com/software_termite.htm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: ArchLinux Created attachment 68375 --> https://bugs.winehq.org/attachment.cgi?id=68375 console messages Summary termite-3.4 can't connect to com5 -> /dev/ttyACM0 Prepare wine: $ rm -rf ~/.wine/ $ wineserver -k $ wineboot Download location https://www.compuphase.com/software_termite.htm https://www.compuphase.com/software/termite-3.4.exe $ sha256sum termite-3.4.exe ca440b6c7f6eaa812ba5f8bf42aed86e02022ca50a1c72585168c9b671d0fe19 termite-3.4.exe Steps to reproduce: 1) Install the program: $ wine termite-3.4.exe Accept the defaults. Now termite starts. 2) Press settings. The dropdown box only shows COM1. Choose baud rate 9600 and press OK. Now termite reports "Failed to initialize the port. Please verify the COM port settings." 3) Press "Connect". Now that termite reports "Waiting for port" 4) Press close. Now termite closes. As a sanity test, I open moserial, choose /dev/ttyACM0 9600,8N1, press connect, and I see the messages my MCP2221 serial to USB converter is sending to me. /dev/ttyACM0 is detected by wine: $ ls -l ~/.wine/dosdevices/ total 0 lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:25 c: -> ../drive_c lrwxrwxrwx 1 cedric cedric 10 Oct 10 19:35 com1 -> /dev/ttyS0 lrwxrwxrwx 1 cedric cedric 12 Oct 10 19:35 com5 -> /dev/ttyACM0 lrwxrwxrwx 1 cedric cedric 8 Oct 10 19:26 d:: -> /dev/sr0 lrwxrwxrwx 1 cedric cedric 1 Oct 10 19:25 z: -> / My versions $ wine --version wine-5.18 (Staging) $ pacman -Q wine wine-staging 5.18-1 uname -a Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000 x86_64 GNU/Linux -- 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 2

[Bug 49752] New: Mikster MPC4 System: 'Selected serial port not exist'
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=49752 Bug ID: 49752 Summary: Mikster MPC4 System: 'Selected serial port not exist' Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: amad4wine2020(a)gmail.com Distribution: --- Log in as 'Adm' user, go to the 'Controllers list', press the 'Add' button, select the appropriate 'Port COM' and 'Baud rate', press the 'Test' button, you will probably get an error message containing the phrase 'Selected serial port not exist'. I have tried the following registry keys: [System\\CurrentControlSet\\Enum\\SERIAL\\COM2\\COM2] 1598720497 #time=1d67e260ec36dbc "ClassGUID"="{4D36E978-E325-11CE-BFC1-08002BE10318}" "FriendlyName Value"="Serial Port (COM2)" [Software\\Wine\\Ports] 1598713705 #time=1d67e163e9541c4 "COM2"="/dev/ttyS1" Unfortunately, it makes no difference. Download links from the software's website: https://mikster.eu/en/download-center/ https://mikster.eu/wp-content/uploads/2019/03/installmpc482ENG.zip P.S. The installer will silently install FirebirdSQL 1.5 and enable Firebird Guardian, it does not work well with winehq-devel. Unpack the installmpc482ENG.exe and rename the included installmpc482ENG/firebird/FirebirdWin32.exe before continuing with the installation. Install the renamed FirebirdWin32.exe manually (uncheck the 'Use the Guardian to control the server?' option during the installation). -- 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 26

[Bug 39810] New: Office 2010 Pro Plus uninstallation fails
by wine-bugs＠winehq.org 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=39810 Bug ID: 39810 Summary: Office 2010 Pro Plus uninstallation fails Product: Wine Version: 1.7.55 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isiraseneviratne(a)yahoo.com Distribution: --- After launching the uninstaller (through either the CD Setup or Wine Uninstaller), selecting the Remove option and then selecting Continue results in a message saying that setup was unable to finish successfully. -- 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 12

[Bug 52899] New: gdi32:font - test_fullname2() fails in non-English Windows 7 locales
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52899 Bug ID: 52899 Summary: gdi32:font - test_fullname2() fails in non-English Windows 7 locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_fullname2() fails in non-English Windows 7 locales. For instance in German (I removed duplicate lines): font.c:5710: Test failed: Arial: style names don't match: returned Regular, expect Standard [...] font.c:5700: Test failed: Arial: font face names don't match: returned Arial Italic, expect Arial Kursiv font.c:5710: Test failed: Arial: style names don't match: returned Italic, expect Kursiv [...] font.c:5700: Test failed: Arial: font face names don't match: returned Arial Bold, expect Arial Fett font.c:5710: Test failed: Arial: style names don't match: returned Bold, expect Fett [...] font.c:5700: Test failed: Arial: font face names don't match: returned Arial Bold Italic, expect Arial Fett Kursiv font.c:5710: Test failed: Arial: style names don't match: returned Bold Italic, expect Fett Kursiv font.c:5710: Test failed: Tahoma: style names don't match: returned Regular, expect Standard [...] font.c:5700: Test failed: Tahoma: font face names don't match: returned Tahoma Bold, expect Tahoma Fett font.c:5710: Test failed: Tahoma: style names don't match: returned Bold, expect Fett [...] font.c:5710: Test failed: Webdings: style names don't match: returned Regular, expect Standard font.c:5710: Test failed: Wingdings: style names don't match: returned Regular, expect Standard https://test.winehq.org/data/patterns.html#gdi32:font Spanish and Portuguese (pt_PT) get the same set of errors but with their own localized names. Mark these tests as broken on Windows 7? win_skip() them? -- 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 51391] New: On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog, breaks user32:win
by WineHQ Bugzilla 25 Jul '23

25 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=51391 Bug ID: 51391 Summary: On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog, breaks user32:win Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com On Windows 7 and 8.1 ntoskrnl.exe:ntoskrnl triggers a network firewall dialog (see the screenshots for the TestBot WineTest runs on w7u_2qxl and w8). Despite that ntoskrnl.exe:ntoskrnl succeeds. However it leaves that dialog open which then causes two failures in user32:win: https://test.winehq.org/data/patterns.html#user32:win win.c:3394: Test failed: GetActiveWindow() = 00000000 win.c:3394: Test failed: GetFocus() = 00000000 Notes: * These are the same failures as in bug 51390. If it is decided that user32:win is the test that needs fixing then this bug could be merged. * But if the decision is that ntoskrnl.exe:ntoskrnl should either not trigger such a dialog or close it, then this bug should remain separate. * Most of ntoskrnl.exe:ntoskrnl is skipped on Wow64 so this issue does not happen in newtb-w864-32. * The 64-bit ntoskrnl.exe:ntoskrnl test also does not trigger that dialog for some reason. -- 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 5

[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