https://bugs.winehq.org/show_bug.cgi?id=52648
Bug ID: 52648
Summary: conhost.exe:tty test_read_console_control() fails in
Hindi and Portuguese
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
conhost.exe:tty test_read_console_control() fails on Windows in Hindi and
Portuguese:
tty.c:1365: Test failed: keyboard state: got 8, expected 18
https://test.winehq.org/data/patterns.html#conhost.exe:tty
This can be reproduced on w10pro64-hi, w10pro64-pt-BR and w10pro64-pt-PT but
does not fail in the other locales.
This failure started when these tests were added:
commit 89a8b32d7a976504ee98ba1a7d08574bc9bc00e6
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Tue Mar 1 09:26:08 2022 +0100
conhost/tests: Add tests for ReadConsoleW with control.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
Signed-off-by: Jacek Caban <jacek(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=53437
Bug ID: 53437
Summary: Windows program (ZOSICloud.exe) ran great under an
earlier version, but now crashes
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: david(a)depowell.com
Distribution: ---
Created attachment 72817
--> https://bugs.winehq.org/attachment.cgi?id=72817
Console output when program is run
I have a program, called ZOSICloud.exe, that I installed on my Ubuntu Focal
Fossa (20.04) laptop about six months ago to monitor my security cameras. It
ran perfectly under WINE, but I honestly don't know what version of WINE I was
running.
For some reason, my WINE installation disappeared, perhaps during an update. I
haven't a clue why. So I reinstalled it using apt. The installation went well,
but I wound up with version 5.0 of WINE. Most of my other Windows programs
would run, but a lot of useful functionality (e.g., printing) was missing.
ZOSICloud.exe would not run at all, just crash immediately.
I uninstalled WINE 5.0 and installed version 7.0 by following the instructions
on the winehq.org web site. This restored the missing functionality in my other
Windows programs, but ZOSICloud.exe still crashes when I try to launch it. I
have reinstalled ZOSICloud.exe several times, using both the default (64-bit)
wineprefix and in a 32-bit wineprefix (I don't know how to tell if
ZOSICloud.exe is 64- or 32-bit), but it won't run either way.
The application (ZOSICloud.exe) can be downloaded from
https://s3.amazonaws.com/ansjerfilemanager/ZOSICloud_3.0.1.2.exe
Note that the desktop link it creates is incorrect; it runs a program called
"test_link.exe" instead of "ZOSICloud.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=38604
Bug ID: 38604
Summary: winedbg: internal crash when valgrinding
ieframe/tests/ie.c with pdb debug symbols
Product: Wine
Version: 1.7.43
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
Created attachment 51499
--> https://bugs.winehq.org/attachment.cgi?id=51499
log
See also bug 38594 for a similar issue, though this one causes winedbg to
crash. Log is 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.
http://bugs.winehq.org/show_bug.cgi?id=15679
Summary: cygwin symlinks not working in wine
Product: Wine
Version: 1.1.6
Platform: Other
URL: http://cygwin.com
OS/Version: other
Status: NEW
Keywords: download, source
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Surprisingly, cygwin seems to work nowadays,
as long as you do everything inside a wineconsole
running cygwin.bat. (Perhaps cygwin apps should
work outside wineconsole; that would be a separate
bug report.)
However, cygwin's gcc doesn't work unless you
replace certain cygwin symlinks with unix ones, e.g.
$ cd .wine/drive_c/cygwin/usr/i686-pc-cygwin/bin
$ for a in *; do ln -sf ../../../bin/$a; done
Likewise, /bin/vi doesn't work, as it's a symlink to vim.exe.
In fact, cygwin's ls -l doesn't even recognize cygwin's symlinks as such:
$ ls -l vi
-rw-r--r-- 1 dank mkpasswd 18 Oct 19 05:53 vi
$ cat vi
!<symlink>vim.exe
So either they're not being created right, or they're
not being recognized properly by cygwin for some reason,
or both.
--
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=51529
Bug ID: 51529
Summary: CloseHandle(INVALID_HANDLE_VALUE) returns FALSE,
GetLastError is ERROR_INVALID_HANDLE
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: sergey.bychkow(a)gmail.com
Distribution: ---
Created attachment 70368
--> https://bugs.winehq.org/attachment.cgi?id=70368
Test CloseHandle(INVALID_HANDLE_VALUE)
CloseHandle(INVALID_HANDLE_VALUE) returns FALSE, GetLastError is
ERROR_INVALID_HANDLE on Wine. I tried it with MacOSX and Linux.
But on Windows CloseHandle(INVALID_HANDLE_VALUE) returns TRUE. So many programs
could fail if they didn't expect FALSE here.
Test case (Pascal). Can be compiled with FPC or Delphi.
// file TestCloseHandle.lpr
program TestCloseHandle;
{$APPTYPE CONSOLE}
uses
//Winapi.Windows;
Windows;
var
aHandle: THandle;
aResult: HRESULT;
begin
//aHandle := 0;
aHandle := INVALID_HANDLE_VALUE;
if CloseHandle(aHandle) then
aResult := 0
else
aResult := GetLastError;
Writeln('Result: ', aResult);
end.
--
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=29998
Bug #: 29998
Summary: Crysis 2 (>1.0) huge graphical issues after loading a
savegame
Product: Wine
Version: 1.4-rc5
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: christian.frank(a)gmx.de
Classification: Unclassified
Created attachment 39060
--> http://bugs.winehq.org/attachment.cgi?id=39060
Crysis 2 log
Hi,
if you try to use a saved game in Crysis 2 which is patched to a higher level
than 1.0, you will have huge graphical issues. Either you get a black scree
with only the hud displayed, or completely broken graphics, or a whiet screen
etc..
This does only happen if you use a savegame or if you want to replay a mission.
If you start the campaign from the beginning, the game will look fine.
This behaviour happens with tons of wine version i have testet, so doesnt seem
to be a regression right now.
CryEngine 3 is planned to be used in other upcoming games and is somehow a
engine which really pushes d3d9 to its limits.I think it would make a lot of
sense to get this issue fixed .
Many thanks,
Christian
--
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=52790
Bug ID: 52790
Summary: winedbg 'bt all' filled with dbghelp_dwarf fixmes
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, regression, source
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Debian
First, run any wine app
$ wine notepad
Then, try to run `bt all`:
austin@hyrule:~$ echo "bt all" | winedbg
Wine-dbg>02d4:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
RtlDefaultNpAcl () at Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731
0x7bc53821 ntdll+0x53821 [Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731]: ret
1731 }
Backtracing for thread 0024 in process 0020 (C:\windows\system32\start.exe):
Backtrace:
=>0 0x7bc0be6c CsrAllocateCaptureBuffer+0xae6c() in ntdll (0x0031fd58)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
1 0x7b073b7e WaitForSingleObject+0x39(handle=<internal error>,
timeout=<internal error>) [Z:\home\austin\wine-git\dlls\kernelbase\sync.c:334]
in kernelbase (0x0031fd98)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for
frame_CFA resolution (RULE_VAL_EXPRESSION)
2 0x00402804 wmain+0xa14(argc=<internal error>, argv=<internal error>)
[Z:\home\austin\wine-git\programs\start\start.c:701] in start (0x0031fef8)
3 0x004038d8 wmainCRTStartup+0x68()
[Z:\home\austin\wine-git\dlls\msvcrt\crt_wmain.c:60] in start (0x0031ff30)
4 0x7b62d310 WriteTapemark+0x100(device=7FFD1000, type=<is not available>,
count=<is not available>, immediate=<is not available>)
[Z:\home\austin\wine-git\dlls\kernel32\tape.c:317] in ker
nel32 (0x0031ff48)
5 0x7bc58ca7 RtlWakeConditionVariable+0x57(variable=7B62D300)
[Z:\home\austin\wine-git\dlls\ntdll\sync.c:757] in ntdll (0x0031ff5c)
6 0x7bc59360 RtlCreateUserThread(entry=00403870, arg=7FFD1000)
[Z:\home\austin\wine-git\dlls\ntdll\thread.c:261] in ntdll (0x0031ffec)
02d4:fixme:dbghelp_dwarf:dwarf2_read_range no entry found
0x7bc53821 ntdll+0x53821 [Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731]: ret
1731 }
with WINEDEBUG=-all, it's much more readable:
Backtracing for thread 0024 in process 0020 (C:\windows\system32\start.exe):
Backtrace:
=>0 0x7bc0be6c CsrAllocateCaptureBuffer+0xae6c() in ntdll (0x0031fd58)
1 0x7b073b7e WaitForSingleObject+0x39(handle=<internal error>,
timeout=<internal error>) [Z:\home\austin\wine-git\dlls\kernelbase\sync.c:334]
in kernelbase (0x0031fd98)
2 0x00402804 wmain+0xa14(argc=<internal error>, argv=<internal error>)
[Z:\home\austin\wine-git\programs\start\start.c:701] in start (0x0031fef8)
3 0x004038d8 wmainCRTStartup+0x68()
[Z:\home\austin\wine-git\dlls\msvcrt\crt_wmain.c:60] in start (0x0031ff30)
4 0x7b62d310 WriteTapemark+0x100(device=7FFD1000, type=<is not available>,
count=<is not available>, immediate=<is not available>)
[Z:\home\austin\wine-git\dlls\kernel32\tape.c:317] in ker
nel32 (0x0031ff48)
5 0x7bc58ca7 RtlWakeConditionVariable+0x57(variable=7B62D300)
[Z:\home\austin\wine-git\dlls\ntdll\sync.c:757] in ntdll (0x0031ff5c)
6 0x7bc59360 RtlCreateUserThread(entry=00403870, arg=7FFD1000)
[Z:\home\austin\wine-git\dlls\ntdll\thread.c:261] in ntdll (0x0031ffec)
0x7bc53821 ntdll+0x53821 [Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731]: ret
1731 }
--
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=47595
Bug ID: 47595
Summary: Tequila City of Heroes Launcher - expect_no_runtimes
Process exited with a Mono runtime loaded.
Product: Wine
Version: 4.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 65009
--> https://bugs.winehq.org/attachment.cgi?id=65009
Console output - wine 4.11 (staging)
Hello everyone,
"Tequila" is a launcher for the abandoned game "City of Heroes". It starts up
okay, downloads some stuff but terminates.
Console output is 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=38594
Bug ID: 38594
Summary: dbghelp_msc:pe_load_debug_directory Got a page fault
while loading symbols (Visual C++ 2013 .pdb's)
Product: Wine
Version: 1.7.43
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: dbghelp
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
Created attachment 51493
--> https://bugs.winehq.org/attachment.cgi?id=51493
terminal output in wine-1.7.43
Now that we have pdb's for wine_gecko (see bug 36941), I tried running valgrind
with gecko 2.36. The atl100/tests/atl.c test shows a lot of issues with unknown
symbols, eventually getting a page fault, e.g.,:
fixme:dbghelp_msc:codeview_fetch_type Cannot locate type 103
fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 103
fixme:dbghelp_msc:codeview_snarf S-Udt nullptr_t: couldn't find type 0x103
fixme:dbghelp_msc:codeview_snarf S-Udt NullptrT: couldn't find type 0x103
fixme:dbghelp_msc:codeview_snarf Unsupported symbol id 114c
fixme:dbghelp_msc:codeview_add_type_enum_field_list Unsupported type 1404 in
ENUM field list
fixme:dbghelp_msc:numeric_leaf Unsupported numeric leaf type 8009
fixme:dbghelp_msc:numeric_leaf Unsupported numeric leaf type 800a
...
err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols
full output 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=53521
Bug ID: 53521
Summary: imm32:imm32 - test_default_ime_window_creation() fails
on Windows 10 21H1+
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: imm32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
imm32:imm32 - test_default_ime_window_creation() fails on Windows 10 21H1+:
imm32.c:1427: Test failed: Expected IME window existence
https://test.winehq.org/data/patterns.html#imm32:imm32
This failure is systematic and this check was introduced in:
commit 716e9c93e4a2a0574e0028d428eb087574d8d843
Author: Akihiro Sagawa <sagawa.aki(a)gmail.com>
AuthorDate: Fri Sep 2 21:55:37 2016 +0900
imm32/tests: Add more default IME window tests with message-only window.
Signed-off-by: Akihiro Sagawa <sagawa.aki(a)gmail.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.