https://bugs.winehq.org/show_bug.cgi?id=51407
Bug ID: 51407
Summary: kernel32:time's test_GetCalendarInfo() fails in Hindi
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 70263
--> https://bugs.winehq.org/attachment.cgi?id=70263
Broken fix and traces
Three GetCalendarInfo() checks fail in Hindi:
https://test.winehq.org/data/patterns.html#kernel32:time
time.c:728: Test failed: GetCalendarInfoA failed err 87
time.c:731: Test failed: GetCalendarInfoA failed err 87
time.c:738: Test failed: got 0, expected 7
The immediate cause for the failure is that Hindi is one of the few languages
for which NLS_IsUnicodeOnlyLcid() returns true. In turn this causes the ANSI
GetCalendarInfoA() to return ERROR_INVALID_PARAMETER. The last failure just
reflects the fact that the two calls to GetCalendarInfoA() should not have
failed.
Only Hindi fails and only in Wine. But before declaring this a Wine bug we need
to look at Windows.
* For some reason probably related to SetWinLocale [1] the system locale of
w10pro64_hi is still English.
* This causes both the ANSI and Unicode GetCalendarInfo() to return English
names (Monday).
* Manually setting the system locale to Hindi is possible on Windows 10 2004.
What's interesting is the disabled and checked-by-default checkbox in that
dialog:
[X] Beta: Use Unicode UTF-8 for worldwide language support
* And indeed doing that and running the test again results in
GetCalendarInfoA() returning UTF-8 strings on Windows!
time.c:730: ret=19
sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0"
सोमवार
time.c:735: ret2=19
sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0"
सोमवार
time.c:742: ret2=19 sdayname1=L"\0938\094b\092e\0935\093e\0930"
* The beta moniker strongly suggests that this is a new option. Indeed
selecting Hindi as the system locale was not possible in Windows 8.1 for
instance.
* This is probably also why SetWinLocale has trouble setting the system locale
to Hindi.
So the Windows behavior can be summarized as such:
* Return localized values for non-Unicode-only locales.
* In older Windows versions setting the system locale to a Unicode-only locale
is impossible.
* In newer Windows versions setting the system locale to a Unicode-only locale
is possible and then it uses UTF-8.
Commenting out the Hindi line in NLS_IsUnicodeOnlyLcid() fixes the failures in
Wine (see attached patch). But this fix is wrong because it causes
GetCalendarInfoA() to return question marks instead of intelligible strings.
(it also impacts many APIs but that's probably ok based on the Windows
behavior)
So Wine should do one of the following:
1. Stick to a 'safe' system locale when $LANG is set to a Unicode-only locale.
Typically this would be English.
2. Or use UTF-8 when the system locale is a Unicode-only locale.
Option 2 would actually make a lot of sense on Unix systems but it is also more
likely to break Windows applications. So option 1 may be the safer (and
simpler?) option (for now).
[1]
https://source.winehq.org/git/tools.git/blob/HEAD:/testbot/bin/SetWinLocale…
--
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=43208
Bug ID: 43208
Summary: Assassin's Creed IV - Black Flag Hangs tightly
Product: Wine-staging
Version: 2.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tall89(a)mail.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
When you switch to the Big Inagua location, the game hangs tight, you have to
do Cntrl + Atl + Delete to remove the task, then the game closes, then you
receive an error message, the program ACBF.exe has a serious error, the
application will be closed, we apologize for the inconvenience
WINEDEBUG=fixme-all,err+loaddll,err+dll,err+file,err+reg
------ Program AC4BFSP.exe ------
err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status
0x2733
err:winedevice:async_create_driver failed to create driver L"ps6ajtsb":
c0000135
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from
192.168.0.102:5353 16 aspire89-P55A-UD4.local. AAAA
FE80:0000:0000:0000:0A12:F0CA:1A84:437A"
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: ProbeCount 2; will
deregister 4 aspire89-P55A-UD4.local. Addr 192.168.0.102"
err:eventlog:ReportEventW L"Local Hostname aspire89-P55A-UD4.local already in
use; will try aspire89-P55A-UD4-2.local instead"
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from
192.168.0.102:5353 25 102.0.168.192.in-addr.arpa. PTR
aspire89-P55A-UD4.local."
err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict
discarding 27 102.0.168.192.in-addr.arpa. PTR aspire89-P55A-UD4-2.local."
err:ole:CoInitializeEx Attempt to change threading model of this apartment from
multi-threaded to apartment threaded
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> has not been linked, or is not a program object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> has not been linked, or is not a program object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> has not been linked, or is not a program object.".
err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error
generated. <program> object is not successfully linked, or is not a program
object.".
wine: Unhandled page fault on read access to 0x00000063 at address 0x8cfb7f
(thread 0047), starting debugger...
wine: Unhandled page fault at address 0x7bc5d590 (thread 0012), starting
debugger...
err:seh:start_debugger Couldn't start debugger ("winedbg --auto 14 168") (1115)
Read the Wine Developers Guide on how to set up winedbg or another debugger
--
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=48048
Bug ID: 48048
Summary: urlmon:protocol - The ftp test fail on Vista to
Windows 8
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The ftp protocol test in urlmon:protocol fails frequently on Windows from Vista
to Windows 8:
protocol.c:1188: Test failed: hrResult = 800c0006, expected E_PENDING or S_OK
protocol.c:1193: Test failed: dwError = 12111, expected ERROR_SUCCESS
protocol.c:3656: Test failed: wait timed out
urlmon:protocol:0700 done (258) in 120s
Test failed: timed out
Note: 800c0006 is INET_E_OBJECT_NOT_FOUND
See https://test.winehq.org/data/tests/urlmon:protocol.html
--
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=18635
Summary: Menu bar is hidden in Adobe Lightroom 2.3
Product: Wine
Version: 1.1.22
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thomas+wine(a)stromberg.org
With the Adobe Lightroom 2.3 demo, the menu bar titles (File, etc.) do not
display. If you click on the area that they should be, the menu does appear
however. Lightroom 2.3 can be downloaded from
https://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_lightroom (free
Adobe login required)
I'm not sure where to go about tracing the issue down to, but I did notice the
following calls that show that it is calling DrawMenuBar().
0009:Call user32.GetMenu(0002003c) ret=60030cbe
0009:Ret user32.GetMenu() retval=000000f0 ret=60030cbe
0009:Call user32.GetMenuBarInfo(0002003c,fffffffd,00000000,0032e1a4)
ret=60030cec
fixme:menu:GetMenuBarInfo (0x2003c,0xfffffffd,0x00000000,0x32e1a4)
0009:Ret user32.GetMenuBarInfo() retval=00000000 ret=60030cec
0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030beb
0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030beb
0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030c06
0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030c06
0009:Call user32.GetMenuItemInfoW(00000280,0000f060,00000000,0032e08c)
ret=60030c22
0009:Ret user32.GetMenuItemInfoW() retval=00000001 ret=60030c22
0009:Call user32.DrawMenuBar(0002003c) ret=6008d171
--
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=51365
Bug ID: 51365
Summary: wininet:http causes urlmon:protocol to time out
Product: Wine
Version: 6.10
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: urlmon
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
If wininet:http is run before urlmon:url the latter will time out as follows:
protocol.c:348: Test failed: unexpected call OnResponse
protocol.c:839: Test failed: unexpected call ReportProgress_MIMETYPEAVAILABLE
protocol.c:1101: Test failed: unexpected call ReportData
protocol.c:3437: Test failed: wait timed out
protocol.c:3439: Test failed: expected Switch
protocol.c:3560: Testing http protocol (redirected, disable auto redirect)...
protocol.c:469: QueryService(IID_IGetBindHandle)
protocol.c:475: QueryService(IID_IWindowForBindingUI)
protocol.c:1178: Test failed: unexpected call ReportResult
protocol.c:1186: Test failed: hrResult = 800c0014, expected: 00000000
urlmon:protocol:0bd0 done (258) in 120s
(0x800c0014 = INET_E_REDIRECT_FAILED)
The timeout actually happens in test_http_protocol_url() on line 3437:
ok( WaitForSingleObject(event_complete, 90000) == WAIT_OBJECT_0, "wait timed
out\n" );
This actually happens on machines that use the wt-daily.bat script [1] because
that script first runs the 32-bit tests (including wininet:http) and then the
64-bit tests and, obviously, no configuration 'reset' happens in between.
Specifically this causes failures in the 64-bit urlmon:protocol results on
cw-gtx560 and cw-rx460:
https://test.winehq.org/data/patterns.html#urlmon:protocol
[1] https://github.com/fgouget/wt-daily/blob/master/wt-daily.bat.template#L138
--
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=50348
Bug ID: 50348
Summary: MFMEv20 Emulator crashes on start
Product: Wine
Version: 6.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adec2011.ac(a)gmail.com
Distribution: ---
Created attachment 68935
--> https://bugs.winehq.org/attachment.cgi?id=68935
Log file for crash
MFMEv20 crashes on start. Log file attached
--
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=46330
Bug ID: 46330
Summary: [Feature Request] Enable winelib on ppc64el
Product: Wine
Version: unspecified
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: winelib
Assignee: wine-bugs(a)winehq.org
Reporter: tpearson(a)raptorengineering.com
Distribution: ---
With the resurgence in POWER hardware support and interest centering around the
POWER8/POWER9 chips, it would be great to get winelib support for the ppc64el
architecture. This would allow Windows open source applications to be used on
these powerful machines (e.g. FEMM, SQLYog, etc.).
--
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=46694
Bug ID: 46694
Summary: widl crashes in dlls/atl during build on ppc64el
Product: Wine
Version: 4.2
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tpearson(a)raptorengineering.com
Distribution: ---
Created attachment 63657
--> https://bugs.winehq.org/attachment.cgi?id=63657
Backtrace
Building on ppc64el fails with a segmentation fault in widl while attempting to
build dlls/atl. Backtrace attached.
--
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.