wine-bugs February 2020

wine-bugs@winehq.org

1 participants
7229 discussions

[Bug 44988] New: win86emu says "unable to reserve memory" when i try to run an x86 app on arm
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=44988 Bug ID: 44988 Summary: win86emu says "unable to reserve memory" when i try to run an x86 app on arm Product: Wine Version: 3.6 Hardware: arm OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skompc(a)gmail.com this is actually an old issue that should be brought back up in my opinion since wine now runs on android and win86emu would allow regular windows apps to run. I've uploaded a copy of win86emu onto mega for download https://mega.nz/#F!omABTTwC!aQ4qOIxu1U3aOPge5hj4xw -- 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 47501] New: Toontown Rewritten on Wine 4.12: Unhandled page fault on read access to 0x00000000 at address 0x1fea2b7 ( thread 0064)
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=47501 Bug ID: 47501 Summary: Toontown Rewritten on Wine 4.12: Unhandled page fault on read access to 0x00000000 at address 0x1fea2b7 (thread 0064) Product: Wine Version: 4.12 Hardware: x86 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neel(a)neelc.org Created attachment 64889 --> https://bugs.winehq.org/attachment.cgi?id=64889 Backtrace from TTREngine.exe on Wine While the TTR launcher works and I am able to log in, after logging in when TTR attempts to launch the game, I get this error: Unhandled page fault on read access to 0x00000000 at address 0x1fea2b7 (thread 0064). My computer is a HP Slimline 290-p0014 with an Intel Core i7-8700, 24GB RAM, an nVidia GT 1030 (Zotac), and 64-bit FreeBSD 12.0. I had this issue on other version of Wine on FreeBSD and Linux, both with nVidia and Intel graphics. I am running a 32-bit version of Wine I compiled with the instructions here: https://wiki.winehq.org/FreeBSD -- 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 19775] New: Largo Winch: crash with hardware vertex shader
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=19775 Summary: Largo Winch: crash with hardware vertex shader Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net Created an attachment (id=23166) --> (http://bugs.winehq.org/attachment.cgi?id=23166) Full log +all,-several, stripped from GetTick line noise. With default settings in winecfg, the application crashes immediately before displaying the logos, upon return from d3d8 CreateVertexShader. Disabling the hardware vertex shader in winecfg allows the game to start (but see bug #19773). This is the first application I faced where I had to do this -- can I expect 3D applications to generally work well without hardware VS? The full log (attached) shows a NULL pointer access by the application immediately following return from IDirect3DDevice8Impl_CreateVertexShader. fixme:d3d8:ValidateVertexShader (0x102d278 (nil) (nil) 1 0x33ef20): stub [2x] 0009:trace:d3d8:parse_token 0x40010007 REG(D3DVSDE_TEXCOORD0, D3DVSDT_FLOAT2) 0009:trace:d3d8:IDirect3DDevice8Impl_CreateVertexShader (0x15e4e0) : returning 0x10426f0 (handle 0xf0000021) 0009:trace:seh:raise_exception code=c0000005 flags=0 addr=0x48b24d ip=0048b24d tid=0009 wine: Unhandled page fault on read access to 0x00000000 at address 0x48b24d (thread 001c) =>0 0x0048b24d in largowinch (+0x8b24d) (0x7ee2b010) I'm not aware of a demo of this application. Running Ubuntu Intrepid with Intel i915, but the crash also occurs on MacOS with NVidia 9400M. -- 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 12

[Bug 43949] New: WINEDEBUG=+relay does not work on armv7l (and/ or when CWD is a symlink)
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=43949 Bug ID: 43949 Summary: WINEDEBUG=+relay does not work on armv7l (and/or when CWD is a symlink) Product: Wine Version: 2.19 Hardware: arm OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- While getting logs for bug 43945, I Noticed that WINEDEBUG=relay does not work (+tid,+seh were fine): ../../../tools/runtest -q -P wine -T ../../.. -M d3dx9_36.dll -p d3dx9_36_test.exe.so mesh && touch mesh.ok 0047:trace:relay:load_list L"RelayExclude" = L"ntdll.RtlEnterCriticalSection;ntdll.RtlTryEnterCriticalSection;ntdll.RtlLeaveCriticalSection;kernel32.48;kernel32.49;kernel32.94;kernel32.95;kernel32.96;kernel32.97;kernel32.98;kernel32.TlsGetValue;kernel32.TlsSetValue;kernel32.FlsGetValue;kernel32.FlsSetValue;kernel32.SetLastError" 0047:trace:relay:load_list L"RelayFromExclude" = L"winex11.drv;winemac.drv;user32;gdi32;advapi32;kernel32" 0047:Call KERNEL32.__wine_kernel_init() ret=af0ff758 Warning: could not find DOS drive for current working directory '/var/host/media/removable/SD Card/wine-git/dlls/d3dx9_36/tests', starting in the Windows directory. wine client error:47: write: Invalid argument Makefile:369: recipe for target 'mesh.ok' failed make: *** [mesh.ok] Error 1 If I remove +relay, it's fine. Possibly relevant, CWD is $HOME/wine-git/dlls/d3dx9_36/tests, while $HOME/wine-git is a symlink to /var/host/media/removable/SD Card/. -- 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 7

[Bug 10106] New: Cannot disable cursor blinking in the wine GUI
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=10106 Summary: Cannot disable cursor blinking in the wine GUI Product: Wine Version: 0.9.36. Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: test AssignedTo: wine-bugs(a)winehq.org ReportedBy: zhoujiafan(a)gmail.com I have updated the wine to wine-0.9.36 in my Linux Fedora Core5. Currently the cursor is always blinking. For example, the editplus running in wine. I tried to edit the wine registry as follows: HKEY_CURRENT_USER -> CONTROL PANEL -> Desktop -> CursorBlinkRate = -1 And this does not stop the blinking cursor!!! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 24

[Bug 44129] New: Bayonetta: much slower than Windows
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=44129 Bug ID: 44129 Summary: Bayonetta: much slower than Windows Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: tod.jackson(a)gmail.com Distribution: --- Created attachment 59870 --> https://bugs.winehq.org/attachment.cgi?id=59870 brief fixme I got a chance to test Bayonetta in Window 7 and realized it's much slower in Wine (about half the fps) than Windows, whereas I previously was underestimating my hardware. I recall reading that such a high discrepancy should probably be reported. The game is already difficult to play under Wine because it it requires one of the async read/write patches in bug 42982 to make headway. Also note the game requires CSMT for coherent visuals. Can this fixme cause a major performance problem? fixme:d3d:state_zenable Unrecognized depth buffer type 0xffffffff. The game seems unusual in that it ties all actions to vblank/vsync, if that makes any sense. In Wine terms I guess that means it relies on this function, though as I'm not a developer I'm likely wrong: fixme:d3d9:d3d9_device_SetMaximumFrameLatency iface 0x1574b0, max_latency 1 stub! https://msdn.microsoft.com/en-us/library/windows/desktop/ff471334(v=vs.85).… Anyway, the game already requires a native d3dcompiler_43 to avoid HLSL parsing failure, but any tips/patches/suggestions to improve performance would be much welcomed. I tested a recent Mesa git version that has a GLSL cache but it didn't really help. I understand that I'm already running an Intel potato, but based on my recent Windows experience I think we could get the game to native speed one day. Also, I bet that all of Platinum Games' ports suffer the same engine (for example Nier Automata), though I'm not sure. Full fixmes attached for completeness, also tried a native xinput and d3dx9_43 with no 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.

2 18

[Bug 48555] New: Helm Standalone/VST plugin 32bit version has random content in window, 64bit version works OK
by WineHQ Bugzilla 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=48555 Bug ID: 48555 Summary: Helm Standalone/VST plugin 32bit version has random content in window, 64bit version works OK Product: Wine Version: 5.0 Hardware: x86-64 URL: https://tytel.org/helm/direct_downloads/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: and3md(a)gmail.com Distribution: Mint Created attachment 66367 --> https://bugs.winehq.org/attachment.cgi?id=66367 Screenshot on left 64 bit version, on right 32 bit version. Helm Standalone/VST plugin 32bit version has random content in window, 64bit version works OK Standalone version and VST plugin (tested in LMMS) behaves the same. 32 bit version window content change random, often displaying the contents of other windows running on the system. Setting "Hide wine version" in wine staging does not change the behavior. On screenshot on left 64 bit version (everything OK), on right 32 bit version (gliches, random video memory). Steps to reproduce: 1. Install Helm 32 bit - https://tytel.org/helm/direct_downloads/ 2. Run Helm -- 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 38941] New: Text colors are missing
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=38941 Bug ID: 38941 Summary: Text colors are missing Product: Wine Version: 1.7.30 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arromdee(a)atnex.net Distribution: --- I am running the 64 bit Wine 1.7.30 that comes with Mageia Linux 5.0. I am running Wine on DOSCenter from http://nugnugnug.com/ . (This is a program that catalogs DOS games, but it is itself a Windows program). Download the build 035 or whatever one is on the page, then download the daily .DAT file. Unzip them. Also get a DOS game .zip file. I tested this using a legal Doom shareware at http://www.doomworld.com/pageofdoom/files/doom1_1.zip . Run the DOScenter.exe in Wine, and under Settings and Tools, load the .DAT file. Then in the main screen, select auto scan and scan the doom1_1.zip. The scan results show what files should be in the doom1_1.zip and what are missing. These should be labelled with different colors (indicating that the doom1_1.zip contains 6 correct files and one mismatched file), and so should the doom1_1.zip itself. When I actually run it, the files are shown in black and white. As color is the main way that DOScenter reports information, the program is essentially useless. This DOScenter.exe works fine in Windows 7. -- 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

[Bug 43434] New: StarCraft: Brood War stopped running after 1.19 update
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=43434 Bug ID: 43434 Summary: StarCraft: Brood War stopped running after 1.19 update Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iop_jr(a)yahoo.com Distribution: --- Created attachment 58800 --> https://bugs.winehq.org/attachment.cgi?id=58800 Log when trying to start StarCraft 1.19 After the recent update, there's a similar message to bug #42741. But even using staging ClientSdk.dll fails to initialize. So StarCraft is broken again. Full debug logs: http://www.filedropper.com/log_24 -- 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 39

[Bug 39721] New: Listview custom draw in report mode uses wrong background color
by wine-bugs＠winehq.org 01 Aug '20

01 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=39721 Bug ID: 39721 Summary: Listview custom draw in report mode uses wrong background color Product: Wine Version: 1.8-rc2 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- Created attachment 52969 --> https://bugs.winehq.org/attachment.cgi?id=52969 test application from bug 9491 In attached test application listview rows are not colored properly. Split from bug 9491. -- 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

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