https://bugs.winehq.org/show_bug.cgi?id=50641
Bug ID: 50641
Summary: Wine cmd handles incorrectly if-for on a single line
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
Wine cmd handles incorrectly expression with if and for on a single line if the
condition is not met such as:
if not ""=="" for %%i IN (A) DO (echo %%i)
Can't recognize 'DO ' as an internal or external command, or batch script.
See attached test case.
--
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=50486
Bug ID: 50486
Summary: The Sims 3 launcher hangs
Product: Wine
Version: 6.0-rc5
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: patch
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Created attachment 69130
--> https://bugs.winehq.org/attachment.cgi?id=69130
gdi32: Do not compare face file names in insert_face_in_family_list() if either
is NULL.
When run from steam (win32 version; needs workarounds for bugs 32342 and
44985). The terminal shows a thread deadlocked on font_cs. Actually this is a
crash in disguise—one thread passes NULL to msvcrt wcsicmp, which raises an
exception, which is caught by the program but leaves font_cs acquired.
The attached patch fixes it.
I haven't checked whether this is a regression. It's not obvious to me why it
would be, but on the other hand I've seen bug reports for The Sims 3 that would
preclude this bug...
--
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=50123
Bug ID: 50123
Summary: The Elder Scrolls V: Skyrim SE has rendering glitches
with vulkan renderer
Product: Wine
Version: 5.21
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 68617
--> https://bugs.winehq.org/attachment.cgi?id=68617
screenshot
0348:fixme:d3d:wined3d_texture_vk_download_data Unhandled multi-aspect format
WINED3DFMT_R24G8_TYPELESS.
0348:fixme:d3d:wined3d_texture_vk_upload_data Unhandled multi-aspect format
WINED3DFMT_R24G8_TYPELESS.
0348:err:d3d:wined3d_context_vk_allocate_vram_chunk_memory Failed to allocate
memory, vr VK_ERROR_OUT_OF_DEVICE_MEMORY.
0348:err:d3d:wined3d_context_vk_create_bo Failed to allocate buffer memory.
0348:err:d3d:adapter_vk_map_bo_address Failed to create new buffer object.
wine-5.21-69-gb940c5e7c91
--
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=44629
Bug ID: 44629
Summary: Process Hacker can't enumerate handles
Product: Wine
Version: 3.2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
Easily reproducible: go to any process, right-click and select "Properties",
open the "Handles" tab. Running under Wine yields "Unable to query handle
information: Unknown error."
--
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=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=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.
http://bugs.winehq.org/show_bug.cgi?id=30062
Bug #: 30062
Summary: Deer Hunter demo: unable to start a new game (map view
unusable)
Product: Wine
Version: 1.3.18
Platform: x86
URL: http://www.fileplanet.com/28105/20000/fileinfo/Deer-Hu
nter
OS/Version: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
CC: hverbeet(a)gmail.com
Classification: Unclassified
Regression SHA1: 926dfc5c49dde8401732a943c1055ba6631bcc5c
Created attachment 39166
--> http://bugs.winehq.org/attachment.cgi?id=39166
terminal output
This bug applies to the first Deer Hunter game in the series, released in 1997.
The game requires Win98 mode to start, and I had to set up virtual desktop
mode.
Steps to reproduce the problem with the demo:
1. Install the demo.
2. Set Windows version to Win98 before launching the game. Start the demo with
DhDemo.exe.
3. In the menu click on <Start New Hunt>, <OK>, <Hunt Here>. Here comes the
problem:
- a map is shown with a crosshair in it. You should be able to change locations
by left-clicking anywhere on the map. This doesn't work: the mouse pointer
disappears when you click on the map.
- the lower part of the screen is missing (showing only a black bar). This is
where certain buttons are located (Hunt, Quit, Help).
- although the buttons at the bottom are missing, you can start a game by
pressing <Enter>. A loading screen is displayed, but the game never loads, it
is freezing with the loading screen.
The problem appeared in 1.3.18 and is still present in 1.4-rc6.
The result of the regression test:
926dfc5c49dde8401732a943c1055ba6631bcc5c is the first bad commit
commit 926dfc5c49dde8401732a943c1055ba6631bcc5c
Author: Henri Verbeet <hverbeet(a)codeweavers.com>
Date: Tue Apr 12 18:28:41 2011 +0200
wined3d: Merge the IWineD3DSwapChain::SetDestWindowOverride()
implementations.
:040000 040000 12437b369aadbbeb6de72ed285f2ced64a7c26b1
025f1e0265b689bf82dd954e1ceb33216af77386 M dlls
Fedora 16
Nvidia 250 / driver 290.10
X.Org X Server 1.11.4
--
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.
https://bugs.winehq.org/show_bug.cgi?id=47915
Bug ID: 47915
Summary: League of Legends 9.20: Crash after champ select
Product: Wine
Version: 4.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail+wine(a)m-reimer.de
Distribution: ---
Created attachment 65411
--> https://bugs.winehq.org/attachment.cgi?id=65411
Crash dump
Since updating to LoL 9.20 there is a new "crash after champ select" issue.
Probably this is the anticheat, again.
Would be great if some experienced developer could have a look at this.
I've attached my crash dump but the bug is really easy to reproduce. Just try
to open the "practice tool". Will crash immediately when the switch from client
to actual game should happen.
Maybe Andrew Wesie could have a look at this one? He did an remarkably great
job with fixing such things in the past!
--
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=50708
Bug ID: 50708
Summary: Assassin's Creed I can't select controller
Product: Wine
Version: 6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: atillolann-1815(a)yopmail.com
Distribution: ---
Created attachment 69444
--> https://bugs.winehq.org/attachment.cgi?id=69444
Terminal output
I can't select a controller, when I configure the controller, it immediately
changes to keyboard again.
Arch: x86_64
Wine: wine-staging6.2
Distro: Linux Mint 20.1 Cinnamon 64 bits.
--
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=50664
Bug ID: 50664
Summary: Assassin's Creed II can't select controller
Product: Wine
Version: 6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: atillolann-1815(a)yopmail.com
Distribution: ---
Created attachment 69368
--> https://bugs.winehq.org/attachment.cgi?id=69368
Log
I can't select a controller in Assassin's Creed II. I am using a Xbox Series
X/S controller.
Using Wine 6.1-developer
Tried using Wine 6.2 no luck.
Distro: Linux Mint 19.0 Cinnamon 64 bit
Arch: x86_64
--
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=50117
Bug ID: 50117
Summary: winedbg --gdb doesn't work
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: tomsod-m(a)ya.ru
Distribution: ---
After updating wine, winedbg's GDB mode stopped working for me. Instead of
attaching to a program, it starts the program, then terminates itself. The
latest unaffected version is 5.17; 5.18 to 5.21 all have this bug. The default
mode of winedbg (without --gdb) works as expected, however.
Steps to reproduce: run e.g. "winedbg --gdb notepad.exe".
Expected behavior: winedbg stops at notepad's entry point and prompts for
commands.
Observed behavior: winedbg quits almost immediately, notepad runs freely.
--
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=50594
Bug ID: 50594
Summary: Surge 1.6.6 VST works but shows only blank window
Product: Wine
Version: 6.1
Hardware: x86-64
URL: https://github.com/surge-synthesizer/releases/releases
/download/1.6.6/Surge-1.6.6-Setup.exe
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: and3md(a)gmail.com
Distribution: ---
Created attachment 69279
--> https://bugs.winehq.org/attachment.cgi?id=69279
Wine log
Steps to reproduce:
1. Install LMMS -
https://github.com/LMMS/lmms/releases/download/v1.2.1/lmms-1.2.1-win64.exe
2. Download and install Surge -
https://github.com/surge-synthesizer/releases/releases/download/1.6.6/Surge…
3. Open LMMS
4. Change plugin embedding in Settings to No embedding (this is workaround of
https://bugs.winehq.org/show_bug.cgi?id=48527).
5. Restart LMMS
4. Open the instruments plugins tab
5. Drag VeSTige to Song Editor window
6. Click Vestige in Song editor to show Vestige GUI
7. In Vestige Window click green folder icon
8. Go to Surge.dll
9. Click Open
10. Empty window appears
On Windows 10 works ok.
There are in log a lot of lines like:
017c:fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (0x1): monitor
setting ignored
0188:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
0188:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#3:
0188:fixme:d3d_shader:print_glsl_info_log Vertex info
0188:fixme:d3d_shader:print_glsl_info_log -----------
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[0].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[2].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[3].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[5]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[6]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[7]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[8]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[9]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[10]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[11]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[12]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[13]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[14]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[15]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log
0188:fixme:d3d_shader:print_glsl_info_log Fragment info
0188:fixme:d3d_shader:print_glsl_info_log -------------
0188:fixme:d3d_shader:print_glsl_info_log 0(37) : warning C7050: "R1.yzw"
might be used before being initialized
--
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=49905
Bug ID: 49905
Summary: VbsEdit runs wscript.exe with unsupported switches /d
and /u
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wscript
Assignee: wine-bugs(a)winehq.org
Reporter: sloper42(a)yahoo.com
Distribution: ---
Created attachment 68266
--> https://bugs.winehq.org/attachment.cgi?id=68266
patch for wscript
In VbsEdit version 9.2139 from https://www.vbsedit.com/, when choosing "Start
Debugging with wscript", wscript.exe is called with unsupported options /d
(debug) and /u (unicode).
Therefore wscripts bail out and script is not executed.
Solution is to ignore these options.
--
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=50613
Bug ID: 50613
Summary: several Wine Mono tests fail to load a referenced
assembly on x86_64
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
When running the x86_64.bug-324535 testcase from Wine Mono, it fails with this
exception:
Unhandled Exception:
System.IO.FileNotFoundException: Could not load file or assembly
'bug-324535-il, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one
of its dependencies.
File name: 'bug-324535-il, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null'
[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not
load file or assembly 'bug-324535-il, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null' or one of its dependencies.
Test failed(1): x86_64.bug-324535
0 tests passed, 1 tests failed
This can easily be checked by downloading the wine-mono tests zip file and
running:
$ wine run-tests.exe x86_64.bug-324535
Other testcases fail in a similar way, but only when run in a 64-bit process.
For example, x86.bug-324535 passes.
Bisect result:
7203ad0ecd06b451116fcfe3b08e4d620e853bd5 is the first bad commit
commit 7203ad0ecd06b451116fcfe3b08e4d620e853bd5
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Thu Jan 21 12:31:34 2021 +0100
ntdll: Load the COR header directly from the file handle.
--
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=48043
Bug ID: 48043
Summary: user32:dce has a pair of random failures
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 65584
--> https://bugs.winehq.org/attachment.cgi?id=65584
user32:dce: Loop over the test_destroyed_window() for 2 random failures.
user32:dce has a pair of random failures in test_destroyed_window():
dce.c:648: Test failed: wrong window
dce.c:658: Test failed: DC for destroyed window not reused
One either gets the first one alone or both together.
See https://test.winehq.org/data/tests/user32:dce.html
These happen at random on a wide range of Windows versions: wxppro, w2003std,
w2008s64, fg-win7u64-*, w1064v1507, w1064v1607.
On Windows 10 the same type of error sometimes happens in test_dc_attributes()
on line 127 which is another "wrong window\n" check.
The attached patch loops over test_destroyed_window() which is sufficient to
make these failures systematic. This can hopefully help debug the issue and
make sure these are fixed.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=15781
Summary: Can't run AllInOne-Office 5
Product: Wine
Version: 1.1.7
Platform: Other
URL: http://www.allinone-office.de/
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
A user asked for this package here:
http://www.linux-forum.de/warenwirtschaft-allione-5-0-a-20117.html
so I tried installing it.
First, you have to set your language to German, e.g.
LANG=DE_de.UTF-8
or it commplains about a language mismatch.
Then, you have to set your Windows version to NT 4 with winecfg, else
it complains that it needs Windows NT 4 or higher.
Then it installs. The font in the installer is almost too tiny
to read, even with corefonts installed.
It first silently installs the Access 2002 runtime
libraries and Jet 40, and those subinstallers aren't particularly
happy; they both end with
err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned
1627
but the main installer continues blindly.
It asks if you want to keep the existing version of some wine dll; I said yes.
It installs a menu item showing that the way to run the app is
wine "C:\\Program Files\\Common Files\\Microsoft Shared\\Access
Runtime\\Office10\\MSAccess.exe" /Runtime "C:\\Program
Files\\AllInOne-Office\\AllInOne-Office.mde"
but that fails with file not found... maybe because of the
access runtime installation problem?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50224
Bug ID: 50224
Summary: Grand Theft Auto 4: Crashes when starting the game
Product: Wine
Version: 5.8
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sterum77(a)gmail.com
Created attachment 68729
--> https://bugs.winehq.org/attachment.cgi?id=68729
backtrace of GTA IV
After starting the game it immediately crashes and generates the attached
output.
As with wine version 4.X the game runs fine, so it looks like something is
broken in version 5.X.
--
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.