https://bugs.winehq.org/show_bug.cgi?id=50379
Bug ID: 50379
Summary: The Witcher 3 has broken rendering with Vulkan
renderer
Product: Wine
Version: 6.0-rc3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 68984
--> https://bugs.winehq.org/attachment.cgi?id=68984
example
In addition all bright parts are blinking.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50967
Bug ID: 50967
Summary: sc.exe doesn't understand the start command and other
parameters
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: falemagn(a)gmail.com
Distribution: ---
Created attachment 69797
--> https://bugs.winehq.org/attachment.cgi?id=69797
Patch that should fix sc.c's typos
It seems like commit 8e9b9da0f889 included some typos that make sc.exe not
understand
1) the start command
2) the failure command's reboot= parameter
3) the actions of the failure command's actions= parameter
4) the create command's start= parameter.
Attached's a patch that should fix things.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50698
Bug ID: 50698
Summary: ::wcsrtombs does not NULL "const wchar_t ** _PSource"
parameter in Wine.
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: besentv(a)gmail.com
Distribution: ---
Created attachment 69428
--> https://bugs.winehq.org/attachment.cgi?id=69428
Example program to test ::wcsrtombs
Windows NULLs the "_PSource" parameter after executing ::wcsrtombs whereas Wine
does not.
I posted some example code as attachment that shows what exactly is going on.
The following output was generated from an executable using the example code
built with Visual Studio 2019 in Release x86 configuration.
Windows Output:
Values before wcsrtombs: X 001CFAF0 2 001CFAF4
Values after wcsrtombs: 1 00000000 2 001CFAF4
Wine Output:
Values before wcsrtombs: X 0031FED8 2 0031FEDC
Values after wcsrtombs: 1 0031FED8 2 0031FEDC
As you can see, the second parameter is NULL'ed on Windows but not using Wine.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50602
Bug ID: 50602
Summary: Far Manager redraws incorrectly after console window
is resized
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
Far Manager redraws incorrectly after console window is resized.
Steps to reproduce:
1. wineconsole Far.exe
2. Enlarge/shrink window serveral times
3. Far Manager is displayed incorrectly
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50386
Bug ID: 50386
Summary: Sniper Elite V2 some objects aren't rendered with
Vulkan renderer
Product: Wine
Version: 6.0-rc3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 68996
--> https://bugs.winehq.org/attachment.cgi?id=68996
examples
fixme:d3d:wined3d_context_vk_update_descriptors NULL constant buffer views not
implemented.
err:d3d:wined3d_context_vk_apply_draw_state Failed to update shader
descriptors.
err:d3d:adapter_vk_draw_primitive Failed to apply draw state.
wine-6.0-rc3-24-g3d2b4233288
--
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.
https://bugs.winehq.org/show_bug.cgi?id=48618
Bug ID: 48618
Summary: Wargaming.net Game Center shows black screen on launch
since Wine 5.0
Product: Wine
Version: 5.0
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: chris(a)cjwatts.com
Distribution: ---
Created attachment 66463
--> https://bugs.winehq.org/attachment.cgi?id=66463
Wine stdout log
Confirmed on two different Ubuntu 19.10 machines.
Able to launch World of Tanks directly without much issue, but the Game Center
is just a black screen.
Tried wine-stable 5.0 and wine-staging 5.1 with the same results.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50632
Bug ID: 50632
Summary: Neverwinter (Steam): Broken graphics (texturing)
[Regression: wine 6.0->6.1]
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: henczati+bugs.winehq.org(a)gmail.com
Distribution: ---
Created attachment 69335
--> https://bugs.winehq.org/attachment.cgi?id=69335
comparison screenshots (menu, ingame) and console logs (from Steam start to
end) using wine 6.0 (good) vs. 6.1 (broken)
On Ubuntu 18.04 amd64 graphics (texturing definitely) broke (see attached
screenshots) in MMORPG "Neverwinter" (started from Steam) upon updating
`winehq-devel` packages from `6.0.0~bionic-1` to `6.1~bionic-1`.
Screenshots were taken at the lowest graphics settings (GPU slider at min, CPU
slider at min) windows for both wine versions.
Note, Neverwinter is free to play. To reproduce you'll need a free Steam
account and a free Neverwinter account (can be created using the game
launcher). And a significant game download handled by the game launcher (IIRC,
around 12GB with "on-demand patching" launcher option and around 25GB without
--- problem present in both cases).
CONSISTENCY:
When I downgrade back:
```
sudo apt install winehq-devel=6.0.0~bionic-1 wine-devel=6.0.0~bionic-1
wine-devel-i386=6.0.0~bionic-1 wine-devel-amd64=6.0.0~bionic-1
```
it works again.
When I upgrade again, it breaks again.
-------------
SETUP:
* WinePrefix: newly created 64-bit, then `winetricks corefonts tahoma d3dx9
steam`
NOTE: Neverwinter needs 64-bits. Fonts installed for Steam, d3dx9 for
Neverwinter (it installs directx anyways on first start, and the graphics were
broken in wine 6.1 that way, too).
Afterwards, this results in (`winetricks list-installed`):
```
andale
arial
comicsans
courier
georgia
impact
times
trebuchet
verdana
webdings
corefonts
tahoma
w_workaround_wine_bug-22053
w_workaround_wine_bug-44985
steam
d3dx9
```
* winetricks --version: `20201206-next - sha256sum:
26b457d0741b7c36755e49a0ea014b61f35f1fb28997bffec03f59495a4ea128`
* winetricks d3dx9: used directx_Jun2010_redist.exe
* Graphics: Intel HD Graphics 620 (rev 02) (PCI vendor and device codes:
8086:5916) + opensource driver (with HWE stack), e.g.:
```
xserver-xorg-video-intel-hwe-18.04=2:2.99.917+git20171229-1ubuntu1~18.04.1
libegl-mesa0=20.0.8-0ubuntu1~18.04.1
libosmesa6=20.0.8-0ubuntu1~18.04.1
libglu1-mesa=9.0.0-2.1build1
```
* OS: LUbuntu 18.04.5 LTS with HWE stack, dist-upgraded@2021-02-03
```
$ uname -a
Linux lubuntu 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC
2021 x86_64 x86_64 x86_64 GNU/Linux
```
* Neverwinter (Steam)
- in AppDB:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=29913
- on Steam store (free to play):
https://store.steampowered.com/app/109600/Neverwinter/
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50424
Bug ID: 50424
Summary: std::mutex crashes on creation
Product: Wine
Version: 4.12.1
Hardware: arm
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: david.paradis(a)us.abb.com
Distribution: ---
Created attachment 69041
--> https://bugs.winehq.org/attachment.cgi?id=69041
Test Project File
I have spent the better half of the last month tracking down a crash in my
application related to the creation of the std::mutex object in my code. After
putting many debugging messages into the Wine code I have finally found what
the issue is. Here is what I have found:
1) In the dlls/msvcp90/msvcp_main.c:init_cxx_funcs() the code is calling
GetProcAddress() for the critical_section methods for ctor, dtor, lock, ... but
never checks to see if we found a valid address for the functions. Later on in
the _Mtx_init_in_situ() a call is made to the critical section ctor and throws
null pointer exceptions because the function pointer is null.
2) In the dlls/concrt140/concrt140.spec there are NO definitions for any ARM
architecture method exports. In the dlls/msvcp90/msvcp90.spec there are
definitions but they are missing in concrt library.
After playing with the concrt140.spec file I was able add the 5 critical
section method exports to the file and was able to verify that I can now create
a std::mutex object and call lock, unlock and other methods on it successfully.
At this point I have no idea how many other ARM methods are missing from the
concrt140.spec list, but the distribution package does not have ANY ARM
definitions in that file.
I am attaching a very simple test CPP file that I was using to verify that the
code is now working for my usage but not completely fixed. With the test code
and the shipping source code you will not get past the point of seeing the
second printf statement after creating the test class, it will crash on the
"test t1;" line.
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.
https://bugs.winehq.org/show_bug.cgi?id=46709
Bug ID: 46709
Summary: VarFormatCurrency doesn't handle an already formatted
string.
Product: Wine
Version: 4.2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Split off from 46442.
When VarFormatCurrency is passed an already formatted string, eg $9.0, it
returns an error instead of a string.
--
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.