https://bugs.winehq.org/show_bug.cgi?id=53214
Bug ID: 53214
Summary: d3d11:d3d11 - test_negative_viewports() fails in the
TestBot VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d11:d3d11 - test_negative_viewports() fails in the TestBot VMs:
d3d11.c:28330: Test succeeded inside todo block: Got 0xffffffff, expected
0xffffffff at (640, 480, 1), sub-resource 0.
d3d11.c:28339: Test succeeded inside todo block: Got 0xffffffff, expected
0xffffffff at (640, 480, 1), sub-resource 0.
d3d11.c:28330: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
d3d11.c:28339: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
d3d11.c:28330: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
d3d11.c:28339: Test failed: Got 0xffffffff, expected 0xff00ff00 at (639, 479,
0), sub-resource 0.
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Happen on Debian Testing + QXL + multi-monitor
So they seems to be related to the VMs QXL GPU.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=53215
Bug ID: 53215
Summary: d3d11:d3d11 - test_fractional_viewports() fails in the
TestBot VMs
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d11:d3d11 - test_fractional_viewports() fails in the TestBot VMs:
d3d11.c:28276: Test failed: Got texcoord {8.43750119e-001, 1.56249881e-001},
expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001.
d3d11.c:28276: Test failed: Got texcoord {8.71093690e-001, 1.28906310e-001},
expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002.
d3d11.c:28276: Test failed: Got texcoord {7.51953065e-001, 2.48046935e-001},
expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001.
https://test.winehq.org/data/patterns.html#d3d11:d3d11
These failures:
* Don't happen on Debian 11 + Intel / KDE
* Happen on Debian 11 + QXL + single-monitor
* Happen on Debian 11 + QXL + multi-monitor
* Happen on Debian Testing + QXL + multi-monitor
So they seems to be related to the VMs QXL GPU.
Note that despite being systematic these failures could cause false positives
due to the test multi-threading (see bug 53212).
--
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=53204
Bug ID: 53204
Summary: shell32:autocomplete - test_custom_source() sometimes
gets DropDown failures on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:autocomplete - test_custom_source() sometimes gets DropDown failures on
Windows:
autocomplete.c:778: Test failed: AutoComplete DropDown should be visible
autocomplete.c:788: Test failed: AutoComplete DropDown should be hidden
https://test.winehq.org/data/patterns.html#shell32:autocomplete
The second failure is not always present.
They only happen on Windows 10.
--
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=53203
Bug ID: 53203
Summary: shell32:autocomplete - test_aclist_expand() sometimes
fails on Windows
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
shell32:autocomplete - test_aclist_expand() sometimes fails on Windows:
autocomplete.c:534: Test failed: Expected 3 expansions, got 2
autocomplete.c:535: Test failed: Expected L"test\\foo\\bar\\baz_bbq\\", got
L"test\\foo\\bar\\"
autocomplete.c:536: Test failed: Expected 3 resets, got 2
autocomplete.c:541: Test failed: Expected 4 expansions, got 3
autocomplete.c:543: Test failed: Expected 4 resets, got 3
autocomplete.c:547: Test failed: Expected 4 expansions, got 3
autocomplete.c:548: Test failed: Expected 5 resets, got 4
autocomplete.c:553: Test failed: Expected 5 expansions, got 4
autocomplete.c:555: Test failed: Expected 6 resets, got 5
autocomplete.c:560: Test failed: Expected 6 expansions, got 5
autocomplete.c:562: Test failed: Expected 7 resets, got 6
https://test.winehq.org/data/patterns.html#shell32:autocomplete
These failures have been seen on Windows 10 1809 and 21H1.
The w8adm VM also got pretty similar failures once:
autocomplete.c:541: Test failed: Expected 4 expansions, got 3
autocomplete.c:542: Test failed: Expected L"test\\", got
L"test\\foo\\bar\\baz_bbq\\"
autocomplete.c:543: Test failed: Expected 4 resets, got 3
autocomplete.c:547: Test failed: Expected 4 expansions, got 3
autocomplete.c:548: Test failed: Expected 5 resets, got 4
autocomplete.c:553: Test failed: Expected 5 expansions, got 4
autocomplete.c:555: Test failed: Expected 6 resets, got 5
autocomplete.c:560: Test failed: Expected 6 expansions, got 5
autocomplete.c:562: Test failed: Expected 7 resets, got 6
--
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=32083
Bug #: 32083
Summary: Diablo III: Missing logo on startup
Product: Wine
Version: 1.5.16
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sworddragon2(a)aol.com
Classification: Unclassified
On starting Diablo III the logo before the game starts is transparent. If I'm
going with the mouse over it the cursor will be hidden.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35213
Bug ID: 35213
Summary: Kane & Lynch: Dead Men demo needs native d3dx9_31
Product: Wine
Version: 1.7.9
Hardware: x86
URL: http://www.gamefront.com/files/9394790/Kane___Lynch__D
ead_Men_Demo
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: wine-bugs(a)winehq.org
Classification: Unclassified
First d3dx9_36 should be installed. Demo crashes with
fixme:d3dx:D3DXCreateEffectEx (0x20f000, 0x1e71cb58, 45008, (nil), (nil),
(nil), 0x10900, 0x1685a8, 0x1a99cf4, 0x1a99cec): semi-stub
after the same issue as for bug 35137, but this time should be d3dx9_31.
--
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=51158
Bug ID: 51158
Summary: advapi32:lsa fails in French on Windows 2004
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: advapi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
advapi32:lsa fails in French on Windows 2004 because the name of the 'Everyone'
group does not seem to be translated anymore:
lsa.c:407: Test failed: expected L"Tout le monde", got L"Everyone"
That's a bit surprising. Maybe the Windows translation was slightly out of
date?
* This should be checked on Windows 2009 but we don't have a test configuration
for it.
* The test also has a translation for German but we don't have a test
configuration for German. There should really be one so we can validate the
test.
Once the results for German and Windows 2009 are known the test can be updated.
--
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=48108
Bug ID: 48108
Summary: kernel32:comm - QEmu's serial baud rate emulation is
broken
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
kernel32:comm got a failure when running on Wine on the TestBot VM:
comm.c:932: Test failed: OutQueue should not be empty
This happens in test_waittxempty():
// Open the serial device
hcom = test_OpenComm(TRUE);
// Here it is already set to 150 bps because that's how a
// previous test left it
...
// Write 17 bytes in overlaped mode.
// At 150 bauds this should take at least 900 ms
res = WriteFile(hcom, tbuf, sizeof(tbuf), &bytes, &ovl_write);
// Leaving us plenty of time to get to
ClearCommError(hcom, &errors, &stat);
...
// And here we expect the serial device to still have data to send.
// But because QEmu sends the data at > 400 kbps this often fails
ok(stat.cbOutQue != 0, "OutQueue should not be empty\n");
That QEmu does not enforce the set baud rate can also be verified from the
command line:
# stty -F /dev/ttyS0
speed 9600 baud; line = 0;
-brkint -imaxbel
# dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000
10000+0 records in
10000+0 records out
10000 bytes (10 kB, 9.8 KiB) copied, 0.224432 s, 44.6 kB/s
# stty -F /dev/ttyS0 300
# stty -F /dev/ttyS0
speed 300 baud; line = 0;
-brkint -imaxbel
# dd if=/dev/zero of=/dev/ttyS0 bs=1 count=10000
10000+0 records in
10000+0 records out
10000 bytes (10 kB, 9.8 KiB) copied, 0.679127 s, 14.7 kB/s
Back to the kernel32:comm failure:
* It did not happen for a long time and started happening on the debian10 VM on
2019-10-03. That corresponds to the time I added the winetest user to the
dialout group, thus giving it access to /dev/ttyS0.
* The same issue happens in the Windows VMs, but the ok() call has a broken()
clause which hides the issue there.
So:
1. The bug needs to be reported to QEmu.
2. See why speeds below 9600 bps are not allowed.
3. We may want a better check for this issue: directly check that the baud rate
is respected. This would allow us to skip tests that depend on the baud rate
and ditch the broken() clause.
4. If the above does not work out the serial device should be removed from the
Wine QEmu 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=52804
Bug ID: 52804
Summary: Crash when save settings in KaiNote
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: matiasmoviegg(a)gmail.com
Distribution: ---
Created attachment 72181
--> https://bugs.winehq.org/attachment.cgi?id=72181
backtrace
Problem with KaiNote
Link for stable https://github.com/bjakja/Kainote/releases
Link for Beta (log from this version)
https://drive.google.com/uc?id=1ECqsrLo5d1jPoz-FKvJrS0279YeTKrmS&export=dow…
Go to File->Settings
Click OK
Click on random place in program
Program Crash
Testing on virtual machine with Xubuntu 21.10 (adding
"LIBGL_ALWAYS_SOFTWARE=1") and Laptop (i5-2520m) with Linux Mint 20.3
--
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=53194
Bug ID: 53194
Summary: d3d9:device - test_cursor_pos() is sometimes missing a
MOUSEMOVE on Windows 10 1809+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d9:device - test_cursor_pos() is sometimes missing a MOUSEMOVE on Windows 10
1809+:
device.c:5296: Test failed: Didn't receive MOUSEMOVE 0 (50, 50).
https://test.winehq.org/data/patterns.html#d3d9:device
These missing WM_MOUSEMOVE issues seem to be known to some extent, but not
quite understood:
https://gitlab.winehq.org/wine/wine/-/blob/1a3217393e2e6226da0f4024d4d384de…
--
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=53001
Bug ID: 53001
Summary: Regression: Endless WAV crashes when moving file list
sub-window
Product: Wine-staging
Version: 7.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: s_chriscollins(a)hotmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
STEPS TO REPRODUCE:
1. Download and extract Endless WAV (version 1.7.8b15 as of this writing):
https://www.bjoernbojahr.de/endlesswav.html
2. Run the extracted "EndlWav.exe" executable.
3. Once the application has launched, drag the bottom window titled "File List"
using its header bar.
RESULT: Endless WAV crashes with the following terminal output:
---
\Endless WAV\EndlWav.exe: dlls/ntdll/unix/thread.c:1737:
ntdll_set_exception_jmp_buf: Assertion `!jmp ||
!ntdll_get_thread_data()->jmp_buf' failed.
wine: Assertion failed at address F7F21549 (thread 0100), starting debugger...
\Endless WAV\EndlWav.exe: dlls/ntdll/unix/thread.c:1737:
ntdll_set_exception_jmp_buf: Assertion `!jmp ||
!ntdll_get_thread_data()->jmp_buf' failed.
0100:err:seh:NtRaiseException Unhandled exception code 80000101 flags 1 addr
0xf7f21549
---
ADDITIONAL INFO:
* The crash happens with wine-staging, but not the same version of wine-devel.
* This crash was introduced in a recent version of wine-staging. At least a
month or two ago with an earlier version of wine-staging, I was not getting
this crash.
* I can reproduce the bug in VirtualBox and with a clean .wine profile.
* Possibly related to bug #52853.
* The crash does not happen if using the OS window manager's shortcut key to
drag the window from anywhere (e.g., left Alt or left Super key).
--
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=53188
Bug ID: 53188
Summary: user32:menu - test_menu_input()'s tests 25, 26 and 27
fail randomly in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
user32:menu - test_menu_input()'s tests 25, 26 and 27 fail randomly (~5.5%
failure rate) in Wine. For instance:
menu.c:2324: Test failed: test 25
https://test.winehq.org/data/patterns.html#user32:menu
The tests 25, 26 and 27 fail independently but seemingly only one at a time.
--
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=53186
Bug ID: 53186
Summary: user32:menu - test_menu_iteminfo() fails randomly when
inserting an invalid submenu in Windows
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:menu - test_menu_iteminfo() fails randomly when inserting an invalid
submenu in Windows:
menu.c:1383: ANSI tests: string 0081FDB0 hbm 38050FB3 txt 0081FD60
menu.c:1566: Test failed: InsertMenuItem should have failed.
menu.c:1383: Unicode tests: string 0081FDB0 hbm 38050FB3 txt 0081FD8C
menu.c:1566: Test failed: InsertMenuItem should have failed.
https://test.winehq.org/data/patterns.html#user32:menu
Most of the time both the ANSI and Unicode tests fail together (~7.7% fail
rate) but there are two instances where only the ANSI test failed (~0.6%).
This impacts Windows 10 1809 to 21H2.
--
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=53185
Bug ID: 53185
Summary: unable to open win app in linux
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: katparamitesh(a)gmail.com
Distribution: ---
Created attachment 72625
--> https://bugs.winehq.org/attachment.cgi?id=72625
robolx player not opening
unable to install any EXE
--
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=53181
Bug ID: 53181
Summary: xinput1_3:xinput has a rare crash in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
xinput1_3:xinput has a rare crash in Wine:
xinput.c:820: Testing xinput9_1_0.dll
Unhandled exception: page fault on execute access to 0x651c3ae2 in 32-bit code
(0x651c3ae2).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:651c3ae2 ESP:0103fe04 EBP:0103ff28 EFLAGS:00010246( R- -- I Z- -P- )
EAX:00000001 EBX:00000002 ECX:0103fe00 EDX:00000000
ESI:00000001 EDI:00000001
Stack dump:
0x0103fe04: 651c0000 000007d0 00001cff 00000002
0x0103fe14: 00000000 00000000 00000000 fffffffd
0x0103fe24: 00000000 00000000 00000000 00000000
0x0103fe34: 00000000 00000000 7b60da30 001439d0
0x0103fe44: 0011051e 00000000 00000000 00000000
0x0103fe54: 00000000 00000000 00000000 00000000
Backtrace:
=>0 0x651c3ae2 (0x0103ff28)
1 0x7b62a1e0 in kernel32 (+0x2a1e0) (0x0103ff48)
2 0x7bc59b27 in ntdll (+0x59b27) (0x0103ff5c)
3 0x7bc5a1e0 RtlCreateUserThread(entry=651C3300, arg=0x000000000)
[Z:\home\fgouget\wine\winetest\src\dlls\ntdll\thread.c:261] in ntdll
(0x0103ffec)
0x651c3ae2: -- no code accessible --
[...]
PE 63480000-6349b000 Deferred version
PE 666c0000-666e8000 Deferred hid
https://test.winehq.org/data/patterns.html#xinput1_3:xinput
The first known instance of this crash happened on 2022-06-01: there was no
crash from Apr 19 to May 31, but 6 crashes occurred from Jun 01 to Jun 17 (~9%
crash rate). So this looks like a new issue.
The crash address is different every time but always falls in the same range
between version and hid. However I have not been able to reproduce the crash
even over 50 runs. It is possible there is a bad interaction with a previous
test.
--
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=53165
Bug ID: 53165
Summary: Sid Meiers: Pirates! error during install, failed to
ready media for L"lang0.FPK"
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: odecif(a)gmail.com
Distribution: ---
Created attachment 72611
--> https://bugs.winehq.org/attachment.cgi?id=72611
Simple execution log
Hi!
When I try to install the 2-disc version of "Sid Meier's: Pirates!" I get a
popup-error and some log info.
Reproduction steps:
1. Put the first CD in the cd-drive
2. Initialize install "WINEPREFIX=/home/user/.wine-pirates wine d:\Autorun.exe
3. Click through the EULA and start the install
4. Wait until popup-message shows saying "Error 1311.Source file not found: Sid
Meier's Pirates!, Disc 1. Verify that the file exists and that you can access
it" during the install of "AssetsLANG0.FPK".
I have tested in 32 and 64-bit prefix with Windows XP, 7 and 10 with the same
results in all of them.
I have also tested the disc in a Windows XP virtualbox on the same PC and that
installation went flawless.
Not sure what else is to be done here...
Br
--
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=37557
Bug ID: 37557
Summary: SketchUp 2015 doesn't start
Product: Wine
Version: 1.7.30
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: gilson.oliveira.junior(a)gmail.com
Distribution: ---
Hi All,
I've installed the last version of SketchUp in Wine 1.7.30 in my Ubuntu and
when I double click the application, the mouse changes the cursor to "working"
and then it's set again as normal cursor and Nothing Happens.
Via command I get the message below:
wine "C:\Program Files (x86)\SketchUp\SketchUp 2015\SketchUp.exe"
err:module:import_dll Library mfc100u.dll (which is needed by L"C:\\Program
Files (x86)\\SketchUp\\SketchUp 2015\\SketchUp.exe") not found
err:module:LdrInitializeThunk Main exe initialization for L"C:\\Program Files
(x86)\\SketchUp\\SketchUp 2015\\SketchUp.exe" failed, status c0000135
Does anybody knows what I can do? I'm a beginner user of Wine and Ubuntu.
Thanks in advanced for your help.
Regards,
Gilson
--
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=53177
Bug ID: 53177
Summary: Menus can't be used with mouse
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kosaji48.cagoti61(a)murena.io
Distribution: ---
When using Polyboard-6.04j elements inside some menus can't be accessed unless
you try to use the keyboard to select the items.
--
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=51720
Bug ID: 51720
Summary: ntdll-ForceBotoomUpAlloc - StarCitizen crashing on
start
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rawfox(a)freenet.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
SC works on wine-vanilla.
It used to work on wine-staging better, due to the benefits of some patches.
Since a couple weeks, SC on wine-staging crashed when pressing play in the
launcher.
Netho from #LUG found the staging patch ntdll-ForceBottomUpAlloc the source of
the crashes.
Removing that patch and its dependencies made the game load and work again.
--all -W ntdll-ForceBottomUpAlloc -W ntdll-WRITECOPY -W ntdll-Builtin_Prot
Problem is, the game performance is reduced by 50%, when removing that patch.
Removing all ntdll* patches from the staging patchset made the game work fine
again, no issues there, but we miss all the tweaks for ntdll from the staging
patches.
No idea, whats wrong with ntdll-ForceBottomUpAlloc .
Netho futher found /0003-ntdll-Force-virtual-memory-allocation-order.patch is
the patch that causes the issue.
--
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=43557
Bug ID: 43557
Summary: Ukrainian I/i letter support for OEM console
applications using cp866.
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: alter(a)ukr.net
Distribution: Other
Created attachment 58962
--> https://bugs.winehq.org/attachment.cgi?id=58962
patch for c_866.c adding ukrainian I/i support
Ukrainian I/i letter support for OEM console applications using cp866.
There is well-known Windows problem with Ukrainian letters 'I' and 'i'. They
are displayed as question mark ('?') in console applications. But the most
annoying thing is that these files cannot be copied with console File Managers,
like Far. Proposed patch fixes it.
OEM cp966 characters 0xf6 (I ukr) and 0xf7 (i ukr) should be mapped to unicode
0x0406 and 0x0456
Since Wine uses statically compited NLS translation, it is not possible to just
fix NLS file like under Windows (http://alter.org.ua/en/soft/win/cp866u/)
--
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=47582
Bug ID: 47582
Summary: World of Tanks -> open field post get a Unhandled
exception
Product: Wine
Version: 4.12.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: oliver.krueckel(a)gmail.com
Distribution: ---
Created attachment 64987
--> https://bugs.winehq.org/attachment.cgi?id=64987
Unhandled exception: unimplemented function urlmon.dll.414 called in 32-bit
code
if I open the filed post in WoT a Unhandled exception occurs.
WoT continues, but no "Field Post" is displayed.
WoT Version v.1.5.1.3
OS: openSUSE Tumbleweed VERSION="20190730"
@pax> rpm -qa '*wine*'
wine-gecko-2.47-56.13.noarch
wine-32bit-4.12.1-658.13.x86_64
winetricks-20190615-1.1.x86_64
wine-4.12.1-658.13.x86_64
wine-mono-4.9.0-8.1.noarch
--
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=51699
Bug ID: 51699
Summary: World of Tank v1.14
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: oliver.krueckel(a)gmail.com
Distribution: ---
Created attachment 70572
--> https://bugs.winehq.org/attachment.cgi?id=70572
glxinfo
With update WoT to v1.14, the following content is no longer displayed (only
the background is displayed).
The entire store and under menu -> Combat Intelligence
If you move the mouse on these pages, the mouse pointer changes over the fields
that are not displayed. So it seems like a display problem!
--
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=53136
Bug ID: 53136
Summary: crypt32:cert - testVerifyRevocation() fails in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
crypt32:cert - testVerifyRevocation() fails in Wine:
cert.c:4177: Test failed: got 80092012
cert.c:4178: Test failed: got 80092012
https://test.winehq.org/data/patterns.html#crypt32:cert
0c80092012 is CRYPT_E_NO_REVOCATION_CHECK.
The failures started on 2022-05-30 and were initially random but are systematic
since 2022-06-07. The actual test was introduced on 2022-05-24 in the commit
below and reverting to that commit produces systematic failures.
So this is not a regression but instead looks like an outside change that broke
the test.
commit 74832c2177808c6222d44f7e4580de84e0ada8f0
Author: Hans Leidekker <hans(a)codeweavers.com>
AuthorDate: Tue May 24 09:46:22 2022 +0200
crypt32/tests: Add more OCSP revocation tests.
Signed-off-by: Hans Leidekker <hans(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=51243
Bug ID: 51243
Summary: In Wine dinput:keyboard fails if the keyboard layout
does not match the display language
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
In Wine dinput:keyboard fails if the keyboard layout does not match the display
language:
https://test.winehq.org/data/patterns.html#dinput:keyboard
keyboard.c:424: Test failed: 0: expected 10, got 41
keyboard.c:462: Test failed: dinput failed to handle keyboard event
* On my laptop which has an Azerty keyboard:
LANG=fr_FR.UTF-8 -> these two tests succeed (but line 467 fails)
LANG=en_US.UTF-8 -> these two tests fail
* On my desktop which has a Qwerty keyboard:
LANG=fr_FR.UTF-8 -> these two tests fail
LANG=en_US.UTF-8 -> these two tests succeed
Note:
* For the TestBot VMs the locale tests only set $LANG so this is why this
failure happens on debiant2-win32-fr-FR.
* The test only tests English, French, German and Japanese.
* The German case has a similar failure (on lines 424 and 467).
* The Japanese case and other locales do not fail.
--
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=52993
Bug ID: 52993
Summary: msi:action - test_publish() fails on date change
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
msi:action - test_publish() fails on date change:
action.c:4219: Test failed: got "20220513"
https://test.winehq.org/data/patterns.html#msi:action
The issue is that when test_publish() started it was slightly before midnight
but when it checked the date in the registry is was slightly after midnight:
3708 get_date_str(date); // now it's 20220512
...
4186 /* complete install */
4187 r = MsiInstallProductA(msifile, "FULL=1"); // now it's 20220513
...
4219 CHECK_REG_STR(prodkey, "InstallDate", date);// --> failure
The registry date should be equal to either the date before the installation
started, or the date after the installation started.
The test was added in this commit:
commit 8db3c0e358c54e0ebc3f7b4b7461296d046029e9
Author: Hans Leidekker <hans(a)codeweavers.com>
AuthorDate: Thu Oct 14 11:06:13 2010 +0200
msi/tests: Move test coverage for standard actions to a separate module.
--
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.