wine-bugs April 2022

wine-bugs@winehq.org

1 participants
3471 discussions

[Bug 41309] New: Cannot activate ChessbaseLight 2009
by wine-bugs＠winehq.org 01 Nov '22

01 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=41309 Bug ID: 41309 Summary: Cannot activate ChessbaseLight 2009 Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dbacc(a)posteo.de Distribution: --- Created attachment 55639 --> https://bugs.winehq.org/attachment.cgi?id=55639 log Installation runs fine. Activation screen shows up. I enter my code, then it contacts the activation server until I eventually run in to the message "not implemented yet". If I remember correctly, I had this running in a WINE installation years ago. Program can be downloaded here: http://web.archive.org/web/20090822130548/http://www.chessbase.com/download… Activation try needs a valid key though. -- 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.

2 5

[Bug 41350] New: Chessbase 12 does not activate
by wine-bugs＠winehq.org 01 Nov '22

01 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=41350 Bug ID: 41350 Summary: Chessbase 12 does not activate Product: Wine Version: 1.9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dbacc(a)posteo.de Distribution: --- Created attachment 55701 --> https://bugs.winehq.org/attachment.cgi?id=55701 log Installation works fine. Activation of program is not working. Get message "... not implemented" Probably related to bug 41309 -- 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.

2 13

[Bug 47990] New: Wine64: Candidate of CJK input method is invisible on macOS Catalina.
by WineHQ Bugzilla 01 Nov '22

01 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=47990 Bug ID: 47990 Summary: Wine64: Candidate of CJK input method is invisible on macOS Catalina. Product: Wine Version: 4.18 Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com Created attachment 65509 --> https://bugs.winehq.org/attachment.cgi?id=65509 WINEDEBUG=+tid,+pid,+imm,+keyboard,+key,+macdrv Tested with wine-4.18-112-g717109ce79: 1. $ wine64 notepad 2. Switch to Chinese Pinyin input method, and try to type something You will find that candidate didn't display, though you still can type some Chinese characters into notepad with the input method. I didn't see similar on macOS 10.14, so I think this is a Catalina special 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.

1 5

[Bug 51775] New: Axiom Verge 2 crashes on startup due to incomplete sapi implementation
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=51775 Bug ID: 51775 Summary: Axiom Verge 2 crashes on startup due to incomplete sapi implementation Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: sapi Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- This game initializes sapi, even though it doesn't appear to use it at all. It appears from the .NET backtrace, that speechsynthesizer.SetOutputTotDefaultAudioDevice is at fault. After playing around, we can reproduce the crash in a C# application with the following lines ... System.Speech.Synthesis.SpeechSynthesizer synth = new SpeechSynthesizer(); synth.SetOutputToDefaultAudioDevice(); ... Function SetOutputToDefaultAudioDevice, requires that basic iteration and a few registry values are in place. -- 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.

1 4

[Bug 52648] New: conhost.exe:tty test_read_console_control() fails in Hindi and Portuguese
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

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.

1 4

[Bug 38604] New: winedbg: internal crash when valgrinding ieframe/tests/ie.c with pdb debug symbols
by wine-bugs＠winehq.org 31 Oct '22

31 Oct '22

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.

2 5

[Bug 15679] New: cygwin symlinks not working in wine
by wine-bugs＠winehq.org 31 Oct '22

31 Oct '22

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.

2 40

[Bug 51529] New: CloseHandle(INVALID_HANDLE_VALUE) returns FALSE, GetLastError is ERROR_INVALID_HANDLE
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

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.

1 5

[Bug 29998] New: Crysis 2 (>1.0) huge graphical issues after loading a savegame
by wine-bugs＠winehq.org 31 Oct '22

31 Oct '22

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.

2 55

[Bug 52790] New: winedbg 'bt all' filled with dbghelp_dwarf fixmes
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

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.

1 13

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs April 2022