June 2016 - Wine-bugs - list.winehq.org

[Bug 10744] New: Robot Arena main menu is extremely slow
by wine-bugs＠winehq.org 16 Mar '18

16 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=10744 Summary: Robot Arena main menu is extremely slow Product: Wine Version: 0.9.50. Platform: PC URL: http://www.topdownloads.net/games/view.php?id=4536 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: echidnaman(a)gmail.com The main menu for this game is very, very slow. Sound seems to be okay though. The Direct3D menu/cursor are lagged to hell though. This also makes it very hard to click stuff. Fixme's present: fixme:win:EnumDisplayDevicesW ((null),0,0x34f5d8,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 fixme:d3d:IWineD3DClipperImpl_SetClipList (0x215cc0,0x8c32f0,0),stub! fixme:dsound:mmErr Unknown MMSYS error 2 fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(640,480) Demo available at url. (Finally, an application with a bug that actually has a *demo*...) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 19

[Bug 40121] New: serial port issues with .NET applications
by wine-bugs＠winehq.org 16 Mar '18

16 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=40121 Bug ID: 40121 Summary: serial port issues with .NET applications Product: Wine Version: 1.9.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugzilla(a)k2c42.dy.fi Distribution: --- Created attachment 53604 --> https://bugs.winehq.org/attachment.cgi?id=53604 Output of NovaLCT Mars and MiniComPort I tried to run NovaLCT Mars in wine (added it to appdb). http://novastar-led.com/down/software/Sync/NovaLCT-MarsV4.4.0Setup.zip It didn't find any serial ports. I was using dotnet20 and dotnet40 from winetricks. Then I tried this: https://code.msdn.microsoft.com/windowsapps/SerialPort-Sample-in-VBNET-fb04… When starting the serial port sample (MiniComPort.exe) it throws IndexOutOfRangeException. By looking at the source code it seems that System.IO.Ports.SerialPort.GetPortNames returns an empty list. If I ignore the exception, the rest of the MiniComPort program works. It can send and receive some bytes. Inotifywait revealed that NovaLCT Mars doesn't open the ttyUSB device like the MiniComPort.exe does. I also tried with wine-mono-4.5.6 but neither of those programs starts that way. -- 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 11

[Bug 11811] New: App sees no COM ports although COM1... 5 defined in dosdevices
by wine-bugs＠winehq.org 14 Mar '18

14 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=11811 Summary: App sees no COM ports although COM1...5 defined in dosdevices Product: Wine Version: 0.9.56. Platform: PC URL: http://rosepointnav.com/CoastalExplorer/Trial/default.ht m OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: n5470(a)pinefields.com Created an attachment (id=11072) --> (http://bugs.winehq.org/attachment.cgi?id=11072) Screen shot w/ error message Coastal Explorer has an Options section for connecting the app to COM ports for I/O (Tools -> Options -> Instruments -> Port Settings). All available COM ports are listed when running under Windows. Under Wine, none are found (see attached screen shot). Defined COM1...4 (/dev/ttyS0...3) and COM5 (/dev/ttyUSB0) were all chmod to 666 to ensure permissions weren't a problem; the problem remains. Without serial I/O, the app's function of reading a GPS' serial stream and writing commands to an autopilot controller (also via serial stream) is lost. Without it CE functions only as a trip planner and tide predictor. -- 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.

1 79

[Bug 22078] New: Icon error in tree windows of CSPRO 4.0 using wine 1.1.40
by wine-bugs＠winehq.org 07 Mar '18

07 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=22078 Summary: Icon error in tree windows of CSPRO 4.0 using wine 1.1.40 Product: Wine Version: 1.1.40 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: iip.umar.rifai(a)gmail.com CC: iip.umar.rifai(a)gmail.com How to see/test: 1. download cspro here http://www.census.gov/ipc/www/cspro/ 2. Run Cspro 4.0 program 3. Open file/application, goto examples/capi (under cspro 4.0 subdir), open file "capi.ent". 4. You will see that the icon in the tree window on the left side are black. Different when you see it in native windows. Screenshot is here http://sites.google.com/site/iipumarrifai2/wine-cspro-error0.jpg Thanks, -iip- -- 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.

1 18

[Bug 26749] New: in cmd, PATH=FOO should set PATH to FOO
by wine-bugs＠winehq.org 07 Mar '18

07 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=26749 Summary: in cmd, PATH=FOO should set PATH to FOO Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com This affects the "C:\\Program Files\\Mono-2.10.1\\bin\\setmonopath.bat" batch file bundled with Mono. To repeat, do echo path=foo > foo.bat echo path >> foo.bat then run wine cmd /c foo.bat expected output: PATH=foo Observed output: PATH=C:\PROG~FBU\MONO~KUH.1\bin;C:\windows\system32;C:\windows;C:\windows\system32\wbem -- 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.

1 13

[Bug 40375] New: CSPro 6.2 CAPI mode has different window/keystroke behaviour between native windows and wine
by wine-bugs＠winehq.org 07 Mar '18

07 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=40375 Bug ID: 40375 Summary: CSPro 6.2 CAPI mode has different window/keystroke behaviour between native windows and wine Product: Wine Version: 1.9.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iip.umar.rifai(a)gmail.com Distribution: --- When running CSPro 6.2 in CAPI mode, during popup answer appeared and focus, wine cannot catch any keystrokes (tab, shift-tab, number etc.), except I change the focus to main entry windows. In native Windows OS keystrokes (tab, shift-tab, number etc.) accept normaly in both popup or main window focus. How to test: 1. Download and install CSPro 6.2 here https://www.census.gov/population/international/files/cspro/cspro62.exe 2. Run CSPro application (listed "CSPro 6.2" in menu) 3. Open existing application (other files) 4. Goto to folder Examples\1 - Data Entry\Simple CAPI 5. Open Simple CAPI.ent 6. When Simple CAPI application opened, run it by pressing CTRL+R 7. in file dialog, Let's default data to "Simple CAPI Data.dat" and press OPEN 8. Enter any number in Household ID, press ENTER 9. Press any name in Name field and press ENTER 10. Now the popup windows appeared [HERE IS THE POINT OF THE PROBLEM] In native Windows windows OS, I can press 1 or 2 to answer popup windows, but in Wine I must click main windows first to allow entering 1 or 2, if the focus still in popup windows it's not accept any keystrokes. Best regards, -iip- -- 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 1

[Bug 18368] New: D3D errors when trying to run Panzer General II. Problem has occured on all releases since ~0.8
by wine-bugs＠winehq.org 07 Mar '18

07 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=18368 Summary: D3D errors when trying to run Panzer General II. Problem has occured on all releases since ~0.8 Product: Wine Version: 1.1.20 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: critical Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: homiad(a)alum.rpi.edu Created an attachment (id=20931) --> (http://bugs.winehq.org/attachment.cgi?id=20931) Console Output Since installing 1.20 some new errors have cropped up, but the d3d errors still persist. Basically some people claim this game works out of the box while I have never been successful across different machines and using different installations. The error I get is below: fixme:d3d:IWineD3DImpl_FillGLCaps OpenGL implementation supports 32 vertex samplers and 32 total samplers fixme:d3d:IWineD3DImpl_FillGLCaps Expected vertex samplers + MAX_TEXTURES(=8) > combined_samplers fixme:win:EnumDisplayDevicesW ((null),0,0x32f77c,0x00000000), stub! fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 8 fixme:d3d:IWineD3DDeviceImpl_Release (0x141d98) Device released with resources still bound, acceptable but unexpected fixme:d3d:dumpResources Leftover resource 0x14a148 with type 1,WINED3DRTYPE_SURFACE I have also included a screen shot of what the game does. The background should be showing a hex map but instead it retains the image of the previous menu screen. Nothing will work to make the image go away. I am running a stock installation of wine on Ubuntu Jaunty 64bit. I am not using any "enhancement" dll's and I do not have a Windows partition. Thank you. -- 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.

1 20

[Bug 25631] New: Visio 2007 Pro: "Page Setup" dialog is broken
by wine-bugs＠winehq.org 06 Mar '18

06 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=25631 Summary: Visio 2007 Pro: "Page Setup" dialog is broken Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: igor.demyanov(a)gmail.com Open Vision File-Page Setup. See attached files -- 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.

1 17

[Bug 38298] New: TTN_SHOW is not implemented correctly
by wine-bugs＠winehq.org 05 Mar '18

05 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=38298 Bug ID: 38298 Summary: TTN_SHOW is not implemented correctly Product: Wine Version: 1.7.34 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: pietro10(a)mac.com Distribution: --- According to MSDN (https://msdn.microsoft.com/en-us/library/windows/desktop/bb760314%28v=vs.85…) TTN_SHOW in comctl32.dll >= 4.70 has special logic for allowing customization of tooltip size and position: Version 4.70. To display the tooltip in its default location, return zero. To customize the tooltip position, reposition the tooltip window with the SetWindowPos function and return TRUE. Note: For versions earlier than 4.70, there is no return value. This is needed to implement in-place tooltips, such as the ones you get when you hover the mouse over a listview in report mode (with LVS_EX_LABELTIP) or a tree view (by default, it seems), or in this picture: https://i-msdn.sec.s-msft.com/dynimg/IC510747.png. However, wine currently does not follow these rules. According to http://source.winehq.org/source/dlls/comctl32/tooltips.c?!v=wine-1.7.39#0621, it just sends the TTN_SHOW notification, ignoring the return value entirely, then proceeds to set the default window position anyway. As such, in-place tooltips will simply appear where they would if they were regular tooltips (underneath the mouse cursor). I personally tested with wine 1.7.34 (or some commit around that one) from source and Windows XP and Windows 7 with my own in-place tooltips as part of a table control of my own creation. On real Windows, Common Controls 5 and 6 both have TTN_SHOW working properly (but given it says 4.70 I'm not surprised). I'm not the first to notice wrong tooltip behavior. Someone (I don't know if it's just a user or one of the authors of Cardbox) noticed that Cardbox relied on another aspect of TTN_SHOW that wine doesn't imitate: real Windows computes the default tooltip position before sending the notification, not after (as wine still does). In fact, he noticed this back in 2007! I'm not sure why a bug here was never filed... https://cardboxeverywhere.wordpress.com/2007/12/11/programming-note-tooltip… I don't have a minimal test program on hand (the source speaks for itself) but here's something Raymond Chen wrote on the subject that can be constructed into one: http://blogs.msdn.com/b/oldnewthing/archive/2006/06/26/647365.aspx Thanks. -- 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 4

[Bug 35592] New: Chinese input encoding error in multi-byte character set exe with mac driver
by wine-bugs＠winehq.org 05 Mar '18

05 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=35592 Bug ID: 35592 Summary: Chinese input encoding error in multi-byte character set exe with mac driver Product: Wine Version: 1.7.12 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: hwei.sy(a)gmail.com Classification: Unclassified The exe is compiled in multi-byte character set (not Unicode). When input Chinese, the characters become corrupted. I looked into this problem, and found that it is due to dlls/user32/message.c(a)get_input_codepage The "GetKeyboardLayout" returns a wrong language identifier 0x0404 (Chinese Traditional), but it should be 0x0804 (Chinese Simplified). This may be mac driver's problem. And I don't think the 1st parameter of "GetLocaleInfoW" should be the language identifier of the keyboard (returned from "GetKeyboardLayout"). It should be constant "LOCAL_USER_DEFAULT". The keyboard language identifier does not always match the code page of a program. The keyboard language identifier can be changed by switching input method, but code page of a program can not change. -- 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 9