https://bugs.winehq.org/show_bug.cgi?id=55323
Bug ID: 55323
Summary: Windows Program Can not find USB Device
Product: Wine
Version: 8.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: usb
Assignee: wine-bugs(a)winehq.org
Reporter: 372909853(a)qq.com
Distribution: ---
Created attachment 74918
--> https://bugs.winehq.org/attachment.cgi?id=74918
wineusb trace log
lsusb:
Bus 003 Device 008: ID 0403:6011 Future Technology Devices International,
Ltd FT4232H Quad HS USB-UART/FIFO IC
Key parts of the log:
0088:trace:wineusb:add_usb_device Adding new device 0x7f738800a810, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F738801FAF0, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F738801F9E0, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F7388014EF0, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F7388014E50, vendor
0403, product 6011.
0088:trace:wineusb:add_unix_device Adding new device 00007F7388014190, vendor
0403, product 6011.
I did not find any error message about my usb device.
But when I click connect button the windows program report can not find the usb
device.
--
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=54822
Bug ID: 54822
Summary: ddraw:visual - createObjects() crashes on fg-deb64
(Intel GPU)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 74321
--> https://bugs.winehq.org/attachment.cgi?id=74321
ddraw/tests: Prevent the visual tests from crashing the X server on Intel GPUs.
ddraw:visual - createObjects() crashes on fg-deb64 (Intel GPU[1]):
ddraw:visual start dlls/ddraw/tests/visual.c
ddraw:visual:06d0 done (0) in 2s 0B
See https://test.winehq.org/data/patterns.html#ddraw:visual
So this is a case of premature exit. A look at the logs immediately reveals the
cause of the silent crash:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 7 (RRSetScreenSize)
Value in failed request: 0x0
Serial number of failed request: 35
Current serial number in output stream: 36
Running the test with WINETEST_REPORT_SUCCESS=1 and adding some traces shows
the X error happens on this createObjects() line:
112 hr = IDirectDraw7_SetDisplayMode(DirectDraw, 640, 480, 32, 0, 0);
Replacing the 32 bit depth with 24 results in the call returning 0x80004001
(E_NOTIMPL) instead of crashing (that's an odd error code btw). So an easy
workaround would be to use the attached patch.
However:
* This causes most (if not all) of the tests to be skipped.
* My GPU and screen do support 640x480.
* Also running ddraw:visual from my development tree results in 0 skips and 0
failures!
So getting successful runs should be possible (just not in the 3 clean
out-of-tree builds I use to run WineTest :-( ). It's either a matter of
figuring out which is the miraculous patch or where the memory corruption comes
from.
[1] This is an Intel HD Graphics 4600 GPU (comes in the i7-4790K CPU).
--
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=55349
Bug ID: 55349
Summary: ddraw:ddraw7 - test_window_position() sometimes fails
in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ddraw:ddraw7 - test_window_position() sometimes fails in Wine:
ddraw7.c:18843: Test failed: Expect window rect (0,0)-(800,600), got
(0,0)-(1024,768).
ddraw7.c:18899: Test failed: Expect window rect (0,0)-(800,600), got
(0,0)-(1023,767).
ddraw7.c:18906: Test failed: Expect window rect (0,0)-(800,600), got
(0,0)-(1023,767).
See https://test.winehq.org/data/patterns.html#ddraw:ddraw7
This is was pretty common until 2023-01-10 but then it stopped and only
happened a couple of times recently on the GitLab CI:
* 2023-07-26 MR!3413
* 2023-07-20 gitlab-debian-32
--
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=52065
Bug ID: 52065
Summary: Rockstar Games Launcher Installer is leaking memory
Product: Wine
Version: 6.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
Distribution: ---
When installing Rockstar Games Launcher via its installer, the installer never
quits and is shown to be stuck on the loading bar. During that, the app is
leaking memory really fast, filling up my 32GBs of ram in approximately 1
minute.
I can only track the issue down to 6.20 since that's the version the installer
started working at, but it's present in 6.22 too.
Strangely enough, after you kill its process, the installer actually succeeds
at its jos and successfully installs the launcher.
I don't know what I can provide to help with this, apart from the link to the
installer, so let me know.
--
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=54885
Bug ID: 54885
Summary: The child window flickers after using SetParent API to
set parent-child window between windows from different
processes.
Product: Wine
Version: 8.6
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bcjon07(a)gmail.com
Distribution: ---
After using the SetParent API to set parent-child window relationship between
windows from different processes, the child window flickers heavily. This issue
seriously affects the user experience of applications that has any different
processes parent-child window. For convenience, I have created a simple demo
program that can reproduce this issue and attached the download link.
Steps to Reproduce:
1.Download the demo program that can reproduce this issue and open it
(SetParentDemo.exe inside) with Wine tool.
2.Click the first button in the program window (the program may crash
occasionally, but it is not the focus of this bug report, just retry the
operation).
3.Drag child window or switch to activate parent child windows, or move mouse
to hover buttons, observe the display of the child window.
Download link of the demo program:
https://drive.google.com/file/d/1MCrnb1N6cLUzVoX_vO4tFO4qlS_qhAwi/view?usp=…
Other clues: After testing, this issue will occur in WPF form programs packaged
using. NET 6 standalone mode, but it does not occur in programs packaged under
the .NET Framework project (will run on wine mono). Unfortunately, many
applications released using Dotnet standalone mode will only run on their
built-in NET runtime and not on Wine Mono.
System architecture:
x86_64
Ubuntu 20.04
wine 8.6
I appreciate your attention to this matter. If you need further cooperation or
assistance, please feel free to contact me.
--
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=55320
Bug ID: 55320
Summary: Multiple games require vertex buffer output not lower
than 32.
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: patch
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 74914
--> https://bugs.winehq.org/attachment.cgi?id=74914
patch
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
16.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
17.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
18.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
19.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
20.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
21.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
22.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
23.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
24.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
25.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
26.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
27.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
28.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
29.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
30.
fixme:d3d11:d3d11_device_context_IAGetVertexBuffers Failed to get vertex buffer
31.
The following games are affected:
ACE COMBAT 7: SKIES UNKNOWN
Fallout 4
Grand Theft Auto V
Halo: The Master Chief Collection
Hellblade: Senua’s Sacrifice
State of Decay 2: Juggernaut Edition
Stray
The Dark Pictures Anthology: House of Ashes
The Dark Pictures Anthology: Little Hope
The Dark Pictures Anthology: Man of Medan
The Quarry
--
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=54189
Bug ID: 54189
Summary: Fail in SetupDiEnumDeviceInfo: err=259: No more data
available.
Product: Wine
Version: 8.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alois.schloegl(a)gmail.com
Distribution: ---
Created attachment 73724
--> https://bugs.winehq.org/attachment.cgi?id=73724
winedebug logfile trying to install winsupp.exe/ced1401 drivers under
wine/8.0rc1
Trying to install ced1401 drivers [1,2] fails with the attached debug log.
The attached log was generated with WINEARCH=win32, when using WINEARCH=win64
the same error is shown, only the 64bit driver is mentioned in the log file.
[1] https://ced.co.uk/files/winsupp.exe
[2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=41230
--
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=38101
Bug ID: 38101
Summary: Devil May Cry 4 flickering/texture tearing to eventual
white screen
Product: Wine
Version: 1.7.34
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shomari.sharpe(a)gmail.com
Distribution: ---
on starting the game (Directx 9c version) there is lots of flicker present.
Upon turning "ON" the VSYNC option in the game the flicker is reduced. The
title screen will display until it eventually turns to a black and white
alternating flickering.
--
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=39806
Bug ID: 39806
Summary: Devil May Cry 4 Frozen Screen Glitch
Product: Wine
Version: unspecified
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: dijscales(a)gmail.com
Created attachment 53141
--> https://bugs.winehq.org/attachment.cgi?id=53141
Details of the Problem
The screen will randomly freeze while I am playing the game. I can't even play
for very long before it freezes. I tried to fix it by changing the config.ini,
but that did nothing.
--
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=45711
Bug ID: 45711
Summary: Devil May Cry 4 DX10: Transparent sections of textures
rendered as solid black or grey
Product: Wine
Version: 3.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx10
Assignee: wine-bugs(a)winehq.org
Reporter: nenxvrr4.tgj(a)20mail.it
Distribution: ---
Created attachment 62142
--> https://bugs.winehq.org/attachment.cgi?id=62142
Forest level in Devil May Cry 4 illustrating problem.
Transparent sections of textures are rendered as solid black or grey e.g a leaf
appears as a leaf on a black rectangle. This also affects other assets such as
paintings.
--
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.