September 2022 - Wine-Bugs - list.winehq.org

[Bug 52983] New: d3d8:device - test_wndproc() fails systematically on Wine
by WineHQ Bugzilla March 6, 2023

March 6, 2023

https://bugs.winehq.org/show_bug.cgi?id=52983 Bug ID: 52983 Summary: d3d8:device - test_wndproc() fails systematically on Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d8:device - test_wndproc() fails systematically on Wine: device.c:3212: Test failed: Expected message 0x3 for window 0, but didn't receive it, i=49. device.c:3359: Test failed: Expected message 0x3 for window 0x1, but didn't receive it. https://test.winehq.org/data/patterns.html#d3d8:device As far as I can tell the missing "message 0x3 for window 0x1" is present every time, while the one for "window 0" is only present most of the time but not necessarily on the same iteration. -- 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 33069] New: Visual Basic 6 can't load any component
by wine-bugs＠winehq.org March 6, 2023

March 6, 2023

http://bugs.winehq.org/show_bug.cgi?id=33069 Bug #: 33069 Summary: Visual Basic 6 can't load any component Product: Wine Version: 1.5.24 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: german_ant_82(a)yahoo.com Classification: Unclassified Created attachment 43719 --> http://bugs.winehq.org/attachment.cgi?id=43719 Fixme errors list for the components that can't be loaded Visual Basic comes with a set of preloaded standard components and a set of loadable extra components. These extra components can't be loaded. List of components that can't be loaded: AxBrowser Cdlg Microsoft ADO Data Control 6.0 (OLEDB) Microsoft Calendar Control 8.0 Microsoft Chart Control 6.0 (OLEDB) Microsoft Comm Control 6.0 Microsoft Common Dialog Control 6.0 Microsoft Data Bound Grid Control 5.0 (SP3) Microsoft Data Bound List Controls 6.0 Microsoft DataGrid Control 6.0 (OLEDB) Microsoft DataList Controls 6.0 (OLEDB) Microsoft DataRepeater Control 6.0 (OLEDB) Microsoft FlexGrid Control 6.0 Microsoft Hierarchical FlexGrid Control 6.0 (OLEDB) Microsoft Internet Transfer Control 6.0 Microsoft MAPI Controls 6.0 Microsoft Masked Edit Control 6.0 Microsoft Multimedia Control 6.0 Microsoft PictureClip Control 6.0 Microsoft RemoteData Control 6.0 Microsoft Rich Textbox Control 6.0 Microsoft Script Control 1.0 Microsoft SysInfo Control 6.0 Microsoft Tabbed Dialog Control 6.0 Microsoft Windows Common Controls 5.0 (SP2) Microsoft Windows Common Controls 6.0 Microsoft Windows Common Controls-2 5.0 (SP2) Microsoft Windows Common Controls-2 6.0 Microsoft Windows Common Controls-3 6.0 Microsoft Winsock Control 6.0 MSFlexGrid Wizard 6.0 Package and Deployment Wizard VB6 Application Wizard VB6 Data Form Wizard 6.0 VB6 MSChart Wizard 6.0 VisModelBrowser -- 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 13

[Bug 41013] New: Sourceinsight: the 'Window' menu click no response
by wine-bugs＠winehq.org March 6, 2023

March 6, 2023

https://bugs.winehq.org/show_bug.cgi?id=41013 Bug ID: 41013 Summary: Sourceinsight: the 'Window' menu click no response Product: Wine Version: 1.8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robert.hu(a)intel.com Distribution: --- Created attachment 55180 --> https://bugs.winehq.org/attachment.cgi?id=55180 'Window' menu list jump to top left The menu of 'Window' click has no responses. But other menu can work. My workaround is to click its adjacent menu item then arrow key to move to 'Window' menu. But even so, it appears to left top of the window. See attachment. -- 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 2

[Bug 23064] New: Sourceinsight: no response clicking menu, untill firstly right-click in main window area
by wine-bugs＠winehq.org March 6, 2023

March 6, 2023

http://bugs.winehq.org/show_bug.cgi?id=23064 Summary: Sourceinsight: no response clicking menu, untill firstly right-click in main window area Product: Wine Version: 1.2-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dwwwww(a)hotmail.com OS: RHEL 4 Wine, 1.2-rc2 Open sourceinsight, click the menus, no response. But it works after right click in main window area. -- 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 11

[Bug 50281] New: fsync patch for wine 6.0-rc1 (without staging)
by WineHQ Bugzilla March 6, 2023

March 6, 2023

https://bugs.winehq.org/show_bug.cgi?id=50281 Bug ID: 50281 Summary: fsync patch for wine 6.0-rc1 (without staging) Product: Wine Version: 6.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: michael.scott(a)quest-arts.co.uk Distribution: --- Created attachment 68830 --> https://bugs.winehq.org/attachment.cgi?id=68830 fsync patch that applies to vanilla wine 6.0-rc1 I have created a new fsync patch that can apply directly to wine 6.0-rc1 without needing esync from staging. I have tested this patch applied to the latest wine sources (6.0-rc1) as of 7th December 2020 using Star Citizen 3.11. I have included it here for you to review for your convenience to review whether to include it in a future wine version. Current testing from myself and others in the Star Citizen LUG org when using fsync enabled wine and kernels are resulting in a much smoother experience. -- 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 27

[Bug 15480] New: Saving files in Word/Excel creates useless .lnk files
by wine-bugs＠winehq.org March 4, 2023

March 4, 2023

http://bugs.winehq.org/show_bug.cgi?id=15480 Summary: Saving files in Word/Excel creates useless .lnk files Product: Wine Version: 1.1.5 Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrew(a)etc.gen.nz Hi, In Word and Excel 2003 when we save files then a .lnk file is created in the same directory as the source file. These files are useless for two reasons: 1) They're in the same directory as the original .doc or .xls files which have Word and Excel associated with them respectively. 2) On a standard Debian Lenny machine running Gnome the .lnk files aren't recognised by any apps and won't cause Word or Excel to run. I've searched around the place to see if we can turn this "feature" off, but haven't found anything. Is this possible? If not, could this please be added. -- 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 31

[Bug 53501] New: Test Drive Unlimited not working
by WineHQ Bugzilla March 4, 2023

March 4, 2023

https://bugs.winehq.org/show_bug.cgi?id=53501 Bug ID: 53501 Summary: Test Drive Unlimited not working Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ds000001(a)outlook.de Distribution: --- Created attachment 72860 --> https://bugs.winehq.org/attachment.cgi?id=72860 Lutris and Wine Hello, I try to run Test Drive Unlimited DVD 1.66 version with Wine. My system: CPU: 3700X GPU: 6700XT RAM: 32 GB Wine: 7.15 installed through pacman and using Lutris 0.5.10.1-2 for easier management of all WINEPREFIX's WINEPREFIX: - 32 Bit and complete new - Through winecfg set as Win XP - No additional packages installed - ESync, Fsync and DXVK not enabled - Virtual window mode enabled with 1080p resolution, that way it is easier for me to see, if something happens or not - no additional modules installed with Winetricks If I try to start the game, the configured Wine desktop appears, the disc drive starts to spin and after that nothing happens. Output from "lutris -d" and enabled diagnostics for the WINEPREFIX gave me the output from tdudebug1.txt. Enabled debug with "WINEDEBUG=warn+all" and tried to start the game through the wine command. Got the log tdudebug2.txt out of this. Any ideas what I am doing wrong? -- 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 45756] New: Button not clickable when dpi setting changed in Office 2007 Installer
by wine-bugs＠winehq.org March 3, 2023

March 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=45756 Bug ID: 45756 Summary: Button not clickable when dpi setting changed in Office 2007 Installer Product: Wine Version: 3.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- After upgrading from wine 3.14 to wine 3.15 (self-compiled, 32-bit-only) the push buttons in the office 2007 installer are no longer "clickable". When pushing them with the mouse, nothing happens. Using the keyboard to "push" the buttons works as before. Sometimes the mouse pointer is not even visible inside the installer window. This only happens when changing the screen resolution in winecfg (i.e. to 168 dpi). The windows version is set to Windows XP A bisect shows this commit as the first bad commit: commit 2068b73db5e19e1ce3b54b2a8ecb5a5b99ea19b5 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Aug 27 14:02:43 2018 +0200 user32: Process hardware messages in physical coordinates. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 10

[Bug 39113] New: SimplePC_SC.exe does not work
by wine-bugs＠winehq.org March 3, 2023

March 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=39113 Bug ID: 39113 Summary: SimplePC_SC.exe does not work Product: Wine Version: unspecified Hardware: x86 URL: http://downloads.acs.com.hk/utility-tools/en/TOL-PCSC. zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winscard Assignee: wine-bugs(a)winehq.org Reporter: vincent.hardy.be(a)gmail.com Distribution: --- Created attachment 52115 --> https://bugs.winehq.org/attachment.cgi?id=52115 screenshot SimplePC_SC is a programme that tests easily the basic functions of winscard with any smartcard. I file this bug in the hope that a friendly developer starts a real implementation of winscard. -- 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 53728] New: "Escape from Tarkov" requires "DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" in "DisplayConfigGetDeviceInfo" stub
by WineHQ Bugzilla March 3, 2023

March 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=53728 Bug ID: 53728 Summary: "Escape from Tarkov" requires "DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" in "DisplayConfigGetDeviceInfo" stub Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: vinni5.2001(a)web.de Distribution: --- Created attachment 73161 --> https://bugs.winehq.org/attachment.cgi?id=73161 Attachments for this report. The video game "Escape from Tarkov" requires the "DISPLAYCONFIG_DEVICE_INFO_GET_TARGET_NAME" type to be implemented in the "DisplayConfigGetDeviceInfo" function (dlls/user32/sysparams.c). The game uses that to determine monitor names to list in the ingame settings menu. When it first introduced the use of that function, the lack of it in wine made the whole menu freeze, forcing you to kill the game. That freeze was worked around by the game developers on their end, since it also affected some Windows users, but parts of the issue still remain when running the game in wine. Monitor names in the monitor list in the settings menu are simply blank, making it hard to figure out which entry in the list corresponds to which monitor. See "eft_monitors_blank.png" in "attachments.tar.gz" for reference. Creating a quick and dirty patch to make wine return a string and pretend the function was executed successfully confirms it is using that function to get monitor names and the returned string shows up in the list. See "eft_monitors_names.png" and "dirty-monitor-name-workaround.patch" in "attachments.tar.gz" for reference. I should mention that in case other people wanna test the game, it is not free and makes use of the BattlEye anticheat software, so in order to launch the game with wine, it requires staging, a patch to load the Proton BattlEye Runtime (found here, for example: https://github.com/Frogging-Family/wine-tkg-git/tree/master/wine-tkg-git/wi…) as well as the Proton BattlEye Runtime itself (can be found and installed via Steam by Valve) and the necessary environment variable that points to the Proton BattlEye Runtime ("PROTON_BATTLEYE_RUNTIME"="/path/to/runtime"). It also needs "corefonts", "vcrun2019" and "dotnet48" installed via winetricks. I hope those requirements won't prevent this issue from being looked into, but if they do, I apologize. I was able to put together the quick and dirty patch to confirm it is indeed just a missing or incomplete function, however I lack the programming skills and low-level wine/windows knowledge to implement it properly. Thank you! -- 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