https://bugs.winehq.org/show_bug.cgi?id=55345
Bug ID: 55345
Summary: WRC 4 changing audio volume level has no effect
Product: Wine
Version: 8.13
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: xactengine
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
08f8:fixme:xaudio2:IXACT3CueImpl_SetOutputVoiceMatrix (48AA3F18)->(052BA034 1 2
4AC3D778): stub!
And also there is missing one more parameter.
8.13-43-gb5e19a33c93
--
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=52242
Bug ID: 52242
Summary: Mouse cursor disappears in GTA V when Social Club
overlay is on
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vutov.martin97(a)gmail.com
Distribution: ---
Whenever you try to open the Social Club overlay, the cursor disappears. If you
manage to press something with it, it works, it just can't be seen.
Sometimes it works, but very rarely. Haven't figured why it works in said
cases.
To reproduce:
Start GTA V
Wait for it to load to home screen
Press "Home" button for Social Club overlay to appear
No mouse
I am new when it comes to Linux so I've no idea where to get a log from. If
someone tells me how I'll be more than glad to do so. I am launching the game
via Lutris with the Rockstar Games Launcher installer.
--
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=55358
Bug ID: 55358
Summary: user32:sysparams - Unexpected value for SM_C*MENUCHECK
on Windows for mixed locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams - Unexpected value for SM_C*MENUCHECK on Windows for mixed
locale:
sysparams.c:2877: Test failed: GetSystemMetrics(SM_CXMENUCHECK): expected 11
actual 15
sysparams.c:2879: Test failed: GetSystemMetrics(SM_CYMENUCHECK): expected 11
actual 15
See https://test.winehq.org/data/patterns.html#gdi32:font
This test succeeds in the other locales which means it fails because the values
it compares depend on two different Windows locales. For reference,
w10pro64-mx-MX is configured with the following locales:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
--
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=55337
Bug ID: 55337
Summary: user32:sysparams - Some fonts are not enumerated in
test_GetSystemMetrics() for the mixed locale
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:sysparams - Some fonts are not enumerated in test_GetSystemMetrics() for
the mixed locale:
sysparams.c:2733: Test failed: font ?? ?? should be enumerated
sysparams.c:2734: Test failed: font ?? ?? should be enumerated
sysparams.c:2735: Test failed: font ?? ?? should be enumerated
sysparams.c:2736: Test failed: font ?? ?? should be enumerated
sysparams.c:2737: Test failed: font ?? ?? should be enumerated
sysparams.c:2877: Test failed: GetSystemMetrics(SM_CXMENUCHECK): expected 11
actual 15
sysparams.c:2879: Test failed: GetSystemMetrics(SM_CYMENUCHECK): expected 11
actual 15
[...]
See https://test.winehq.org/data/patterns.html#gdi32:font
This test succeeds in the other locales which means it fails because the values
it compares depend on two different Windows locales. For reference,
w10pro64-mx-MX is configured with the following locales:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
--
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=55299
Bug ID: 55299
Summary: gdi32:font - test_stock_fonts() gets unexpected
heights in Arabic en Hebrew locales in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
gdi32:font - test_stock_fonts() gets unexpected heights in Arabic en Hebrew
locales in Wine.
In the ar_MA locale:
font.c:6484: Test failed: 0(0): expected height 12, got 13
font.c:6484: Test failed: 4(14): expected height 13, got 14
In the he_IL locale:
font.c:6484: Test failed: 0(1): expected height 12, got 13
font.c:6484: Test failed: 4(14): expected height 13, got 14
See https://test.winehq.org/data/patterns.html#gdi32:font
This happens on both the TestBot's Debian11 and Testing VMs.
--
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=38690
Bug ID: 38690
Summary: corrupted serial communications
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jpyle490(a)gmail.com
Distribution: ---
Serial communications are corrupted/laggy/ugly. Tested on a Dell Latitude D630
running Linux Mint 17.1 and Wine 1.7.38 from WineHQ PPA, as well as Wine 1.6.2
on the same hardware from the Ubuntu repo. The issue occurs whether it's the
hardware 16550 serial port or a USB attached one. (In this Linux system case
the USB adapter was Prolific-based.)
I observed the same symptoms on Mac OS X Mavericks, compiling Wine 1.7.43 via
Macports, using an FTDI-based USB adapter.
The primary test scenario included Tera Term 4.87 talking to a Cisco router's
console port at 9600 N,8,1 without flow control. Data back from the Cisco was
incomplete, latent and just generally ugly. Using the same hardware and
minicom running natively in either Linux or OS X there were no issues.
Tera Term to a router provided the cleanest environment in which to observe
what was happening. I can't get serial communications to work properly
regardless of the Windows app or the serially-connected 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=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.