wine-bugs

wine-bugs@winehq.org

1 participants
158740 discussions

[Bug 5163] Microsoft Office XP 2002 installer reports error 25003 (installation source corrupted), custom action 'CADpc' returns 1603
by WineHQ Bugzilla 31 Jul '21

31 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=5163 Mark <themh(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |themh(a)gmx.de --- Comment #104 from Mark <themh(a)gmx.de> --- @Anastasius Focht: This analysis from 2008 was a blast to read. Very educational. Meanwhile, since the fix to this bug is in staging, I managed to install Office 2002 almost completely working with this method. I thought I might share it for others who stumble upon this, even though Office 2002 today has probably rather niche usecases. 1. I used a 32bit wineprefix with Wine 6.11-staging, without installing mono or gecko. I used PlayOnLinux for easy installation, but you could probably compile it yourself, too. 2. Install Access, Word, Excel and Powerpoint with the installer. De-select all autocorrection options in the installer. They won't install properly (probably another bug) and if you don't de-select them, Office keeps asking to insert the installation medium at every start. 3. I then copied the prefix in my default wine environment, which is currently 5.0-stable, ran winecfg and changed the mode to Windows XP. It probably runs in Windows 7 mode, to, but since it's Office XP you might as well put it to the proper OS version. 4. The installation is now complete. Finally, I manually created 4 launchers for the progams via alacarte (you can google that if you're unfamiliar with menu editing) The launchers have to look similar to that: env WINEPREFIX="/home/username/.wine-mso" wine-stable /home/username/.wine-mso/drive_c/Program\ Files/Microsoft\ Office/Office10/WINWORD.EXE -- 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 0

[Bug 51523] New: Batman Arkham Knight - crashes on unimplemented functions cuD3D11GetDevice and cuGraphicsD3D11RegisterResource
by WineHQ Bugzilla 31 Jul '21

31 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51523 Bug ID: 51523 Summary: Batman Arkham Knight - crashes on unimplemented functions cuD3D11GetDevice and cuGraphicsD3D11RegisterResource Product: Wine-staging Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cybermax(a)dexter.no CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70364 --> https://bugs.winehq.org/attachment.cgi?id=70364 Implement cuD3D11GetDevice and cuGraphicsD3D11RegisterResource I am attaching a patch that will implement a semi-stub for cuD3D11GetDevice and cuGraphicsD3D11RegisterResource in wine-staging. Since wine does not have the nvapi/nvcuda libraries included this patch can currently ONLY be used for WINE-STAGING. I tested this with: wine-staging-6.13 Steamclient run from wineprefix nVidia PhysX software 9.19 (latest). Batman Arkham Knight Using the winetricks PhysX version - 9.14 - is too old to implement Interactive smoke/fog. The included patch makes you able to enable "Interactive smoke/fog" and "Interactive paper debris". Currently wine implementation of D3D11 is not working too well, even tho the smoke/paper worked fine. Using this together with DXVK and DXVK-NVAPI makes this work pretty good. I have also tested this with Steam/Proton, but this requires an additional patch for the lib to load libcuda.so.1 instead of libcuda.so (Due to steam runtime-soldier). I will leave that patch out for now, as it might not be appropriate for wine-staging (although would still work). -- 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 46882] New: Recent World of Warcraft patch broke vkd3d
by wine-bugs＠winehq.org 31 Jul '21

31 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=46882 Bug ID: 46882 Summary: Recent World of Warcraft patch broke vkd3d Product: vkd3d Version: 1.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: cybermax(a)dexter.no Distribution: --- Created attachment 63952 --> https://bugs.winehq.org/attachment.cgi?id=63952 trace.log There was a patch today (friday 22 march 2019) that broke vkd3d and d3d12. It worked fine earlier today, but upon logging on this evening there was a update, and all i get is a black screen and the mousepointer. WoW works fine with DXVK and d3d11. WoW version is: 8.1.5.29814. I did not find a particular patchnote for this yet. Attaching trace.log with WINEDEBUG=+vkd3d , and VKD3D_DEBUG="trace". -- 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 21

[Bug 51542] New: How do I download Norton on my laptop through norton.com/setup?
by WineHQ Bugzilla 31 Jul '21

31 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51542 Bug ID: 51542 Summary: How do I download Norton on my laptop through norton.com/setup? Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: butlerkaci12(a)gmail.com Distribution: --- If you want to download Norton then you have to go to norton.com/setup then you have to follow the below mentioned step. Download Norton device security 1. Login to your account. 2. Enter your email address along with the password for Norton, and click the login option. 3. In the My Norton portal, click Download. 4. Move to the Get Started page, Select agree and Download. If you are unable to do it on your own then you can connect to us, we have an expert team with us that can fix all your issues in just one phone call. https://www.howdoisetup.com/norton-setup -- 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 51453] New: oleaut32:vartype fails on Windows 10 1909+
by WineHQ Bugzilla 30 Jul '21

30 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51453 Bug ID: 51453 Summary: oleaut32:vartype fails on Windows 10 1909+ Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com oleaut32:vartype has the same set of failures on all the Windows 10 1909+ TestBot VMs: https://test.winehq.org/data/patterns.html#oleaut32:vartype vartype.c:3047: Test failed: expected 10990, got 47515; hres=0x00000000 vartype.c:3048: Test failed: expected 10990, got 47515; hres=0x00000000 vartype.c:3055: Test failed: expected 12785, got 49310; hres=0x00000000 vartype.c:3056: Test failed: expected 12785, got 49310; hres=0x00000000 vartype.c:3057: Test failed: expected 12785, got 49310; hres=0x00000000 vartype.c:3058: Test failed: expected 12785, got 49310; hres=0x00000000 vartype.c:3059: Test failed: expected 12785, got 49310; hres=0x00000000 vartype.c:3060: Test failed: expected 12785, got 49310; hres=0x00000000 vartype.c:3070: Test failed: expected 11722, got 48247; hres=0x00000000 vartype.c:3071: Test failed: expected 11722, got 48247; hres=0x00000000 vartype.c:3074: Test failed: expected 10960, got 47485; hres=0x00000000 vartype.c:3075: Test failed: expected 11325, got 47850; hres=0x00000000 It turns out that this happens because the Y2K cutoff date has changed in Windows 10 1903: * Earlier Windows versions used 29, that is two digit years 0-29 mapped to 2000-2029 while years 30-99 mapped to 1930-1999. * But Windows 10 1903+ use 49 by default so that two digit years 0-49 map to 2000-2049 while years 50-99 map to 1950-1999. oleaut32:vartype expects the old 29 cutoff when it tests how VarDateFromStr() parses dates such as "2 30" which is what causes the failures. Wine's VarDateFromStr() implementation should also be updated to match the current Windows versions. -- 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 51493] New: WXDrive.exe from WeCom failed to startup.
by WineHQ Bugzilla 30 Jul '21

30 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51493 Bug ID: 51493 Summary: WXDrive.exe from WeCom failed to startup. Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com Distribution: --- Created attachment 70328 --> https://bugs.winehq.org/attachment.cgi?id=70328 The expected white dialog. Steps to reproduce: 1. `winetricks -q arial` for work around a CEF crash. 2. Download and install WeCom. 3. `cd ~/.wine/drive_c/Program Files (x86)/WXDrive` 4. `wine WXDrive.exe --disable-gpu --wxdrive-setting=0 --disable-gpu --disable-software-rasterizer --enable-features=NetworkServiceInProcess "wedocs://public.action/openmain?from=winwxwork"` Expected: The program startup and there is a white dialog. Actually: The program doesn't startup. -- 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 6

[Bug 51410] New: mlang:mlang fails on the Hindi test configuration
by WineHQ Bugzilla 30 Jul '21

30 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51410 Bug ID: 51410 Summary: mlang:mlang fails on the Hindi test configuration Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mlang Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 70266 --> https://bugs.winehq.org/attachment.cgi?id=70266 mlang/tests: Fix the check for non-English locales in test_GetCodePageInfo(). mlang:mlang fails on the Hindi test configuration: https://test.winehq.org/data/patterns.html#mlang:mlang The 36 systematic failures all happen on lines 2572 to 2580 in test_GetCodePageInfo(). For instance: mlang.c:2572: Test failed: 9: got wrong wszDescription expected L"Baltic (Windows)" return L"\092c\093e\0932\094d\091f\093f\0915 (Windows)". mlang.c:2576: Test failed: 9: got wrong wszFixedWidthFont expected L"Courier New" return L"Nirmala UI". mlang.c:2580: Test failed: 9: got wrong wszProportionalFont expected L"Arial" return L"Nirmala UI". These checks are meant to be skipped on non-English locales but the test checks the wrong Windows locale and gets confused because the Hindi test configuration still has some English locales (notably the system locale, see WineTest's locale information dump). The attached patch should fix this. -- 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 51185] New: Windows fails to load the minimal PE image in kenel32:loader
by WineHQ Bugzilla 30 Jul '21

30 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51185 Bug ID: 51185 Summary: Windows fails to load the minimal PE image in kenel32:loader Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_Loader() claims that Windows 7 is able to load this minimal PE image: /* Minimal PE image that Windows7 is able to load: 268 bytes */ { 0x04, 0, 0xf0, /* optional header size just forces 0xf0 bytes to be written, 0 or another number don't change the behaviour, what really matters is file size regardless of values in the headers */ 0x04 /* also serves as e_lfanew in the truncated MZ header */, 0x04, 0x40, /* minimal image size that Windows7 accepts */ 0, { ERROR_SUCCESS } }, But in fact this fails on all Windows version from Windows 7 to Windows 10 20H2... except in the early Windows 10 versions (1507 to 1809): https://test.winehq.org/data/patterns.html#kernel32:loader loader.c:1140: Test failed: 16: unexpected error 193 The failing test was introduced by this commit: commit 1a7dd7cdbe184ff3fdf2781e9a2222872bacee2c Author: Dmitry Timoshkov <dmitry(a)baikal.ru> AuthorDate: Wed May 6 15:16:01 2020 +0800 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Fri May 15 11:42:28 2020 +0200 kernel32/tests: Add a PE test image that resembles format of some of 8k demos. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> 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.

1 8

[Bug 51346] New: x264guiEx partly shows white box characters when using Wine-Mono (default encoding issue with C++/CLI).
by WineHQ Bugzilla 30 Jul '21

30 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51346 Bug ID: 51346 Summary: x264guiEx partly shows white box characters when using Wine-Mono (default encoding issue with C++/CLI). Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu Created attachment 70202 --> https://bugs.winehq.org/attachment.cgi?id=70202 x264guiEx configuration window x264guiEx[1] is a famous output plugin for AviUtl, Japanese video editing software[2]. When running it with AviUtl 1.10 and Wine-Mono 6.20, its configuration window partly shows white box characters instead of Japanese characters. See attached image for details. It's not typeface issue. For the attachment case, it shows three white boxes for two Japanese characters, なし. If we had have a missing typeface, it should be two. I guess Wine-Mono's default encoding incompatibility causes this issue. This plugin uses System::String without the encoding parameter in frmConfig.cpp[3]. That means constructor's argument is interpreted using default encoding[4]. [1] https://github.com/rigaya/x264guiEx [2] http://spring-fragrance.mints.ne.jp/aviutl/ [3] https://github.com/rigaya/x264guiEx/blob/9f1abe0f44be3c602ffa938e2ca7d80cea… [4] https://docs.microsoft.com/en-us/dotnet/api/system.string.-ctor?view=net-5.… -- 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

[Bug 51334] New: Microsoft Xbox Live Developer Tool XblTestAccountGui crashes
by WineHQ Bugzilla 30 Jul '21

30 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51334 Bug ID: 51334 Summary: Microsoft Xbox Live Developer Tool XblTestAccountGui crashes Product: Wine Version: 6.11 Hardware: x86-64 URL: https://web.archive.org/web/20210625235311/https://git hub.com/microsoft/xbox-live-developer-tools/releases/d ownload/2106/XboxLiveTools-2106-20210624.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: the.ideals(a)gmail.com Distribution: --- Created attachment 70197 --> https://bugs.winehq.org/attachment.cgi?id=70197 crash log XblTestAccountGui clicking on the front screen buttons leads to the crash (Unhandled page fault). 1. Run XblTestAccountGui 2. Click Login 1. Run XblTestAccountGui 2. Click Clear cached login Potential separate bug for filing (System.EntryPointNotFoundException): 1. Run XblTestAccountGui 2. Click About Source: https://github.com/microsoft/xbox-live-developer-tools sha1sum XboxLiveTools-2106-20210624.zip aa601549455365f4e94ede40ea7dce07d7f93239 XboxLiveTools-2106-20210624.zip du -sh XboxLiveTools-2106-20210624.zip 6.5M XboxLiveTools-2106-20210624.zip -- 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 8

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