https://bugs.winehq.org/show_bug.cgi?id=51233
Bug ID: 51233
Summary: Blacksad crashes when Textures set higher than Medium
with Vulkan renderer
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
0ac8:fixme:d3d:wined3d_swapchain_vk_set_swap_interval Unsupported swap interval
2.
0ac8:err:d3d:wined3d_context_vk_allocate_vram_chunk_memory Failed to allocate
memory, vr VK_ERROR_OUT_OF_DEVICE_MEMORY.
0ac8:err:d3d:wined3d_context_vk_create_image Failed to allocate image memory.
0ac8:err:seh:call_stack_handlers invalid frame 00007F304CE3AEE2
(0000000007832000-0000000007930000)
0ac8:err:seh:NtRaiseException Exception frame is not in stack limits => unable
to dispatch exception.
vkd3d-1.2-280-g100c65c
--
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.