wine-bugs

wine-bugs@winehq.org

1 participants
159185 discussions

[Bug 55051] New: Build regression in wine 8.10 using clang on aarch64 (error in backend: Invalid register name "x18")
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55051 Bug ID: 55051 Summary: Build regression in wine 8.10 using clang on aarch64 (error in backend: Invalid register name "x18") Product: Wine Version: 8.10 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: pierrick.bouvier(a)linaro.org Distribution: --- When compiling wine for aarch64, a build regression appeared in Wine 8.10 when using clang (any version). This is only present when performing make install, which compiles some DLL. Error is that register x18 is used, and clang reports it as an hard error. gcc reports a warning but does not produce an error (warning: call-clobbered register used for global register variable). --- Reproduction steps (from linux-aarch64, debian bookworm): # download llvm-mingw and add to PATH $ ./configure CC="clang" --without-x --without-freetype --prefix=/usr $ make # works $ make install # fails clang -c -o dlls/msvcr110/onexit.o ... fatal error: error in backend: Invalid register name "x18". ... 3. Running pass 'Function Pass Manager' on module 'dlls/msvcrt/onexit.c'. 4. Running pass 'AArch64 Instruction Selection' on function '@_register_onexit_function' --- Bisect pointed this commit: https://github.com/wine-mirror/wine/commit/56cfbf6b860b46768eeae60eef7dfe0a… include: Only enable the non-inline NtCurrentTeb() on the Unix side. This previous commit introduced register x18 for TEB on arm64 (but commit above makes it active): https://github.com/wine-mirror/wine/commit/7f088b0b1387a3b54c438b839046afad… This previous bug already discussed this topic (https://bugs.winehq.org/show_bug.cgi?id=38780) but I'm not sure what the conclusion would be. --- Compiling with CLAGS=-ffixed-x18 silences clang, but I'm not sure it's the right thing to do. gcc works only because it's a warning and not an error. -- 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 6

[Bug 55047] New: d3d test_cursor_clipping() fails
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55047 Bug ID: 55047 Summary: d3d test_cursor_clipping() fails Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression, testcase Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: af902c188ebaf7d6dda3b628409d8c390ab410d5 Distribution: --- I can observe this on two different machines, with at least ddraw and d3d8 tests. It happens regardless of whether the virtual desktop is used. The failure looks like this: ddraw:ddraw1: ddraw1.c:14352: Test failed: SetDis.layMode failed, hr 0x80004001 d3d8:device: device.c:10815: Test failed: Adapter 0: Expect clip rect (0,0)-(640,480), got (1,1)-(639,479). It's not quite consistent, though. One machine can reproduce the ddraw1 failure pretty consistently, enough for me to be able to bisect, but the other seems to fail only intermittently. As a result I can't be 100% sure of the bisect result, but it seems to make sense. -- 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 8

[Bug 55027] New: Microsoft Office: IME result string may get doubled when edit is done
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55027 Bug ID: 55027 Summary: Microsoft Office: IME result string may get doubled when edit is done Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: firelzrd(a)gmail.com Distribution: --- Created attachment 74582 --> https://bugs.winehq.org/attachment.cgi?id=74582 Bad and Good cases in Excel 2003 The recent (v8.x) IMM32 progress is so remarkable that CJK users may finally think of replacing Windows for using Microsoft Office. However, in Microsoft Office apps (confirmed in 2003) having done editing IME preedit text by hitting Enter key may actually put the result text doubled (see in the attached video). My analysis showed that when: WM_IME_COMPOSITION which has GCS_RESULTREADSTR & GCS_RESULTSTR flags on is sent to complete the edit, and result text is sent, Only in case the problem occurs, right after that: WM_IME_COMPOSITION which has GCS_COMPSTR & GCS_COMPATTR & GCS_RESULTSTR flags on is sent. This behavior indicates that xic_preedit_done() and xim_set_result_string() which I found in xim.c are called sometimes in a wrong order. A: XICCallback preedit_done is called xic_preedit_done is called B: keyboard.c:X11DRV_KeyEvent xim_set_result_string is called A is supposed to be called first, and then B should follow. in the good case A happens, then B happens. in the bad case B happens, then A happens. So I think this problem occurs because XIC callback and X11DRV_KeyEvent are called asynchronously. I think the solution may be: * In xim_set_result_string(), check if XIC preedit context exists, and if so, ppostpone the sending of WM_IME_COMPOSITION until next xic_preedit_done() is called or * Ignore xic_preedit_done() if xim_set_result_string() was called very recently Let me hear what you guys think. Thank you -- 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 14

[Bug 55026] New: Expose save_period as a configurable option via winecfg
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55026 Bug ID: 55026 Summary: Expose save_period as a configurable option via winecfg Product: Wine Version: 8.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Wine dumps registry files to the disk every 30 seconds which might not be good for users of SSD/NVMe disks considering it involves completely rewriting them since they are text files, not binary databases as the real Windows registry is where updates are local and small. E.g after installing Microsoft Office the system.reg file can easily blow up to tens of megabytes and it's not that funny having this file being rewritten so often. Would be nice to have this option exposed via winecfg. -- 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 19

[Bug 55123] New: widl crashes when uuid is missing
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55123 Bug ID: 55123 Summary: widl crashes when uuid is missing Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 74678 --> https://bugs.winehq.org/attachment.cgi?id=74678 Minimal Sample See attached sample -- 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 1

[Bug 55122] New: oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55122 Bug ID: 55122 Summary: oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com oleaut32:vartest - test_VarParseNumFromStrFr() fails on Windows 11: vartest.c:1999: Test failed: 1: Call succeeded, hres = 00000000 vartest.c:2012: Test failed: 1: returned 80020005 vartest.c:2049: Test failed: 1: returned 80020005 vartest.c:2121: Test failed: 1: Call succeeded, hres = 00000000 vartest.c:2135: Test failed: 1: returned 80020005 See https://test.winehq.org/data/patterns.html#oleaut32:vartest Where 80020005 == DISP_E_TYPEMISMATCH -- 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 1

[Bug 55121] New: wintrust:asn - test_encodeSPCPEImage() fails on Windows 11
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55121 Bug ID: 55121 Summary: wintrust:asn - test_encodeSPCPEImage() fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wintrust:asn - test_encodeSPCPEImage() fails on Windows 11: asn.c:385: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:398: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:563: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:673: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:696: Test failed: CryptEncodeObjectEx failed: c0000005 asn.c:709: Test failed: CryptEncodeObjectEx failed: c0000005 See https://test.winehq.org/data/patterns.html#wintrust:asn Where c0000005 == STATUS_ACCESS_VIOLATION -- 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 1

[Bug 53431] New: widl generates enum forward declarations in typedefs which are not valid in C++
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=53431 Bug ID: 53431 Summary: widl generates enum forward declarations in typedefs which are not valid in C++ Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: gfw.kra(a)gmail.com Distribution: --- Hi everyone, I recently discovered an issue with C++ code in headers compiled from winrt idl's using widl. It does not compile when included, when tried using mingw g++ v12.1.0. There’s seems to be issue with how enum typedefs are translated within namespaces. Example: When tried to include windows.media.speechsynthesis.h compiled from windows.media.speechsynthesis.idl in cpp file, the following output is received (compiler output shows headers from mingw, but these look the same when compiled using widl in wine). ``` /usr/x86_64-w64-mingw32/include/windows.foundation.h:90:26: error: use of enum ‘PropertyType’ without previous declaration 90 | typedef enum PropertyType PropertyType; | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.foundation.h:164:18: error: using typedef-name ‘ABI::Windows::Foundation::PropertyType’ after ‘enum’ 164 | enum PropertyType { | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.foundation.h:90:39: note: ‘ABI::Windows::Foundation::PropertyType’ has a previous declaration here 90 | typedef enum PropertyType PropertyType; | ^~~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:30: error: use of enum ‘VoiceGender’ without previous declaration 218 | typedef enum VoiceGender VoiceGender; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:476:22: error: using typedef-name ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ after ‘enum’ 476 | enum VoiceGender { | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:42: note: ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ has a previous declaration here 218 | typedef enum VoiceGender VoiceGender; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:822:30: error: using typedef-name ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ after ‘enum’ 822 | enum VoiceGender *value) = 0; | ^~~~~~~~~~~ /usr/x86_64-w64-mingw32/include/windows.media.speechsynthesis.h:218:42: note: ‘ABI::Windows::Media::SpeechSynthesis::VoiceGender’ has a previous declaration here 218 | typedef enum VoiceGender VoiceGender; ``` windows.media.speechsynthesis.idl has typedef of enum VoiceGender, which is defined later. ``` namespace Windows { namespace Foundation { interface IClosable; } namespace Media { namespace SpeechSynthesis { typedef enum VoiceGender VoiceGender; ``` This is translated to following: ``` #ifdef __cplusplus namespace ABI { namespace Windows { namespace Media { namespace SpeechSynthesis { typedef enum VoiceGender VoiceGender; } } } } #else /* __cplusplus */ typedef enum __x_ABI_CWindows_CMedia_CSpeechSynthesis_CVoiceGender __x_ABI_CWindows_CMedia_CSpeechSynthesis_CVoiceGender; #endif /* __cplusplus */ ``` This typedef is not valid in C++. According to the standard, enum cannot be forward declared using typedef. This could be replaced with just simple enum declaration, but it would need to have type specifier (that goes for definition as well). Best regards. -- 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 1

[Bug 36079] New: loader fails to build with clang -faddress=sanitize
by wine-bugs＠winehq.org 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=36079 Bug ID: 36079 Summary: loader fails to build with clang -faddress=sanitize Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Created attachment 48263 --> https://bugs.winehq.org/attachment.cgi?id=48263 make log I tried building wine with clang's address sanitizer enabled, which mostly worked, until the loader: make[1]: Entering directory '/home/austin/wine-gcc49-asan/loader' clang -fsanitize=address -m32 -o wine-preloader -static -nostartfiles -nodefaultlibs -Wl,-Ttext=0x7c400000 preloader.o ../libs/port/libwine_port.a /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../lib32/libpthread.a(pthread_mutex_lock.o): In function `__pthread_mutex_lock': /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:80: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:116: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:146: undefined reference to `__assert_fail' /var/tmp/portage/sys-libs/glibc-2.19/work/glibc-2.19/nptl/../nptl/pthread_mutex_lock.c:151: undefined reference to `__assert_fail' .. austin@aw25 ~/wine-gcc49-asan $ clang --version clang version 3.3 (tags/RELEASE_33/final) Target: x86_64-pc-linux-gnu Thread model: posix austin@aw25 ~/wine-gcc49-asan $ git describe wine-1.7.17-42-g24c5728 -- 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 3

[Bug 55119] New: advapi32:security - test_process_security() fails on GitLab CI's Windows VM
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55119 Bug ID: 55119 Summary: advapi32:security - test_process_security() fails on GitLab CI's Windows VM Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:security - test_process_security() fails on GitLab CI's Windows VM: security.c:3176: Test failed: OpenProcess(PROCESS_VM_READ) should have failed security.c:3178: Test failed: OpenProcess(PROCESS_ALL_ACCESS) should have failed security.c:3209: Test failed: OpenThread(THREAD_SET_THREAD_TOKEN) should have failed See https://test.winehq.org/data/patterns.html#advapi32:security These three failures happen in both the 32- and 64-bit tests but only on gitlab-win10-21h2, the GitLab's Windows VM. -- 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 1

[Bug 49797] New: WIDL doesn't tolerate anonymous structs within interfaces
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=49797 Bug ID: 49797 Summary: WIDL doesn't tolerate anonymous structs within interfaces Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- IDLs in Windows SDKs sometimes contain anonymous structs within interfaces. WIDL fails to compile such IDLs. -- 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 2

[Bug 55118] New: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55118 Bug ID: 55118 Summary: shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:shlfolder - test_SHOpenFolderAndSelectItems() is missing a registry key in the new WoW mode: shlfolder.c:5512: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5513: Test failed: Failed to create window. shlfolder.c:5520: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5521: Test failed: Failed to create window. shlfolder.c:5530: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5531: Test failed: Failed to create window. shlfolder.c:5540: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5541: Test failed: Failed to create window. shlfolder.c:5550: Test failed: Got unexpected hr 0x80040152. shlfolder.c:5551: Test failed: Failed to create window. See https://test.winehq.org/data/patterns.html#shell32:shlfolder Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. See also bug 55117 where shell32:shelldispatch has a similar 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 1

[Bug 55117] New: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55117 Bug ID: 55117 Summary: shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:shelldispatch - test_ShellWindows() is missing a registry key in the new WoW mode: shelldispatch.c:1025: Test failed: got 0x80040152 See https://test.winehq.org/data/patterns.html#shell32:shelldispatch Where 0x80040152 == REGDB_E_KEYMISSING This happens in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. See the *-i386 and *-x86_64 results. -- 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 1

[Bug 55116] New: services.exe:service - service_main() is missing PATHEXT in the new WoW mode
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55116 Bug ID: 55116 Summary: services.exe:service - service_main() is missing PATHEXT in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- services.exe:service - test_service() is missing PATHEXT in the new WoW mode: service.c:420: Test failed: service: did not find PATHEXT environment variable See https://test.winehq.org/data/patterns.html#services.exe:service This happens during both test_service() and test_kill_service_process(), in both the 32-bit and 64-bit tests but only in the new Windows-on-Windows mode. -- 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 1

[Bug 55094] New: Memory Access Violation & Run-Time Error 7 in WINE
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55094 Bug ID: 55094 Summary: Memory Access Violation & Run-Time Error 7 in WINE Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: vikasy.enjay(a)gmail.com Distribution: --- Created attachment 74654 --> https://bugs.winehq.org/attachment.cgi?id=74654 Memory Access Violation & Run-Time Error 7 in WINE Memory Access Violation & Run-Time Error 7 in WINE: I am writing this to seek assistance regarding an issue I encountered while installing and running "Busy Accounting Software" using Wine. Despite my previous unsuccessful attempts, I was eventually able to install the software. However, I am currently facing an ongoing problem when attempting to execute the application. It consistently displays a "Runtime 7 Error and Memory Access Violation" error. Any assistance or troubleshooting steps you can provide would be greatly appreciated. Thank you for your attention to this matter. -- 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 7

[Bug 37346] New: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP
by wine-bugs＠winehq.org 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=37346 Bug ID: 37346 Summary: New application , installed successfully , starts up fine , no data storing , BUSY WIN ACCOUNTING APP Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lax.sunny(a)gmail.com Created attachment 49664 --> https://bugs.winehq.org/attachment.cgi?id=49664 Log created by wine on running the app , problem is with database storage and runtime functions Application named busy win very much famous accounting software tried using number of prefixes application installs smoothly when i run the app it starts up normally but crashes on adding a new company or detecting an old DATABASE -- 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 10

[Bug 55112] New: Chip's Challenge (Steam version) only shows black screen on Nvidia dGPU (works fine on AMD iGPU)
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55112 Bug ID: 55112 Summary: Chip's Challenge (Steam version) only shows black screen on Nvidia dGPU (works fine on AMD iGPU) Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: asdfghrbljzmkd(a)outlook.com Distribution: --- Created attachment 74675 --> https://bugs.winehq.org/attachment.cgi?id=74675 Log when running game on Nvidia dGPU The Steam version of Chip's Challenge only shows a black screen when running on my Nvidia dGPU (RTX 3060 Mobile). The game displays fine on my AMD iGPU (Vega). Note: as this version of the game is only available on Steam, it was tested with Proton 8.0. However, due to the age and nature of the game (basic 2D win32), it is very unlikely to be hitting any Proton-specific code paths (there are no mentions of DXVK/etc in the log either.) If needed, I can try more ways to run it in stock Wine Devel, but it's 2AM and I just wanted to at least get the bug report out. -- 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 2

[Bug 50079] New: Wine msiexec fails when building inside a windows/mac os x docker container
by WineHQ Bugzilla 23 Jun '23

23 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=50079 Bug ID: 50079 Summary: Wine msiexec fails when building inside a windows/mac os x docker container Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: spam(a)crasu.de Distribution: --- Created attachment 68535 --> https://bugs.winehq.org/attachment.cgi?id=68535 Run with winedebug=msi and strace Sample dockerfile: FROM ubuntu:20.04 RUN export DEBIAN_FRONTEND="noninteractive" \ && dpkg --add-architecture i386 \ && apt-get update \ && apt-get install -y wget winbind xvfb unzip curl jq \ && apt-get remove -y libmysqlclient21 mysql-common \ && apt autoremove -y RUN wget -nc https://dl.winehq.org/wine-builds/winehq.key && apt-key add winehq.key RUN echo 'deb https://dl.winehq.org/wine-builds/ubuntu/ focal main' > /etc/apt/sources.list.d/wine.list RUN export DEBIAN_FRONTEND="noninteractive" \ && apt-get update \ && apt-get install -o APT::Immediate-Configure=false --install-recommends -y winehq-devel RUN useradd -ms /bin/bash wineuser # Install winemono RUN wget https://dl.winehq.org/wine/wine-mono/5.1.1/wine-mono-5.1.1-x86.msi RUN WINEPREFIX=/home/wineuser/.wine su wineuser -c "wine msiexec /i wine-mono-5.1.1-x86.msi && wineserver -w" Eroor message: 0024:err:msi:ACTION_InstallFiles compressed file wasn't installed (L"bin\\libmono-2.0-x86.dll") 0024:err:msi:execute_script Execution of script 0 halted; action L"InstallFiles" returned 1603 I tried different msis (wine gecko, wine mono, ....) they all fail. After serveral tries the installation sometimes does not through an error. But the package is still not fully installed. Reference: https://github.com/Winetricks/winetricks/issues/1525 -- 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 6

[Bug 51502] New: Civilization 3 Sound Stutters, loops, and fails (eventually)
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=51502 Bug ID: 51502 Summary: Civilization 3 Sound Stutters, loops, and fails (eventually) Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: bryan(a)varnernet.com Distribution: --- Audio on Civilization III is just not very good. Typical short sounds stutter, playback sounding badly rendered into the target buffer, loop when they shouldn't, etc. The most common problem is for the sound (all of it) to just stop, or just continuously loop a small soundfile that should have been a one-off play at the triggered point in time. Looks like the app is using dsound, along with winmm to mmioOpenA the .wav's. -- 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 52762] New: DesignDoll will not boot/crashes upon booting.
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=52762 Bug ID: 52762 Summary: DesignDoll will not boot/crashes upon booting. 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: catchyandcleche(a)gmail.com Distribution: --- Created attachment 72129 --> https://bugs.winehq.org/attachment.cgi?id=72129 This file (designdoll_backtrace01.txt) is the backtrace file/error log file that was created when I tried to run the DesignDoll application. I am using a GUI version of Ubuntu for Desktop (Ubuntu 20.04.4 LTS), also utilizing WINE version 7.0 (Displayed as wine-7.0 in the terminal). When double clicking the .desktop application created on the desktop (DesignDoll.desktop) after installing the DesginDollLauncher.exe program and after making sure that the DesignDoll.desktop shortcut created during the installation process allows launching, the program will boot* but quickly crash. I attached the program error log (see "designdoll_backtrace01.txt). *I can only assume that the application booted (or at least tried to) and quickly crashed. It did not display any indication that the program had booted in the GUI environment. When a window did show up to indicate that the program had run (in a sense), it was to inform me of the fact that the program crashed (or simply could not boot). -- 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 55107] New: DirectX programs cannot run on dedicated GPU in windowed mode for hybrid-graphics laptop
by WineHQ Bugzilla 22 Jun '23

22 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55107 Bug ID: 55107 Summary: DirectX programs cannot run on dedicated GPU in windowed mode for hybrid-graphics laptop Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xuancong84(a)gmail.com Distribution: --- Years ago, I created a Direct3D program with statically-linked C library. This program has minimal library dependency and has been tested working on all versions of Windows with DirectX 9 supported. You can download it at: https://github.com/xuancong84/solid-rubix-cube/raw/master/Release/svcube.exe I typically run this programs in 4 modes of Wine: 1. full-screen mode without dedicated GPU, `wine svcube.exe` 2. full-screen mode with dedicated GPU, `__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia wine svcube.exe` 3. windowed mode without dedicated GPU, cmdline same as 1 but with 'emulate a virtual desktop' checked 4. windowed mode with dedicated GPU, cmdline same as 2 but with 'emulate a virtual desktop' checked From Wine 5.0 onwards (not tested on older versions), not a single version of Wine (including both wine and winehq, including -stable -staging and -devel) can pass all the 4 modes. In the latest winehq-stable (version 8.0.1~bullseye-1, on MX-Linux21/Debian11), the program can run successfully in 1,2, and 3, but crashes on 4 with the following error: ``` 002c:fixme:winediag:LdrInitializeThunk wine-staging 7.22 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0 MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0 MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0 0110:fixme:ver:GetCurrentPackageId (006CFAF0 00000000): stub 006c:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub 006c:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub 0110:fixme:imm:ImeSetActiveContext (00010072, 1): stub 0110:fixme:imm:ImmReleaseContext (0002006A, 00010072): stub X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 156 (NV-GLX) Minor opcode of failed request: 43 () Serial number of failed request: 409 Current serial number in output stream: 410 ``` I have NVIDIA CUDA installed (Driver Version: 530.30.02, CUDA Version: 12.1). And PyTorch/Tensorflow can run with/without GPU decoding. I am pretty sure my Nvidia GLX is working properly because Mode 2 can run successfully with the process appearing in `nvidia-smi` and taking GPU usage. -- 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 0

[Bug 55104] New: DesignDoll shows an error on start
by WineHQ Bugzilla 21 Jun '23

21 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55104 Bug ID: 55104 Summary: DesignDoll shows an error on start Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 74672 --> https://bugs.winehq.org/attachment.cgi?id=74672 Error message Needs "winetricks corefonts", also work around bug 55103. Install, then run DesignDollLauncher.exe. Install 5.7.0.1, then click "Start". Now there's an error message, see attachment. -- 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 1

[Bug 55103] New: DesignDoll launcher has graphical glitches
by WineHQ Bugzilla 21 Jun '23

21 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55103 Bug ID: 55103 Summary: DesignDoll launcher has graphical glitches Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 74670 --> https://bugs.winehq.org/attachment.cgi?id=74670 Screenshot on Wine (broken) This needs "winetricks corefonts" or it will crash. Download: https://www.terawell-installer.info/setup/en/Setup.exe Archived: https://web.archive.org/web/20230320182515/https://www.terawell-installer.i… Just install the program and then run "DesignDollLauncher.exe" "winetricks dxvk" seems to reliably work around 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.

1 2

[Bug 55102] New: Rework __TRY / __EXCEPT to work on other architectures than x86, e.g. x86_64
by WineHQ Bugzilla 21 Jun '23

21 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=55102 Bug ID: 55102 Summary: Rework __TRY / __EXCEPT to work on other architectures than x86, e.g. x86_64 Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- There is wine/exception.h that provides a try/catch mechanism using the macros __TRY / __EXCEPT. There's two versions 1) Use compiler exceptions (define USE_COMPILER_EXCEPTIONS), needs compiler support 2) Use the wine version of exception handling GCC doesn't support those compiler exceptions, so that's not really an option. The wine implementation however doesn't work on windows. Underlying problem is that the wine try/catch sets up exceptions like x86, this assumption fails when using x86_64. x86 uses a stack of frame pointers in the TEB, while x86_64 (and others) use SEH metadata instead. Since it would be nice using try/catch in tests, this would be a welcome improvement. -- 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 0

[Bug 54271] New: gdiplus:get_gif_background_color can't get gif background color
by WineHQ Bugzilla 21 Jun '23

21 Jun '23

https://bugs.winehq.org/show_bug.cgi?id=54271 Bug ID: 54271 Summary: gdiplus:get_gif_background_color can't get gif background color Product: Wine Version: unspecified Hardware: x86 OS: other Status: UNCONFIRMED Severity: critical Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Created attachment 73837 --> https://bugs.winehq.org/attachment.cgi?id=73837 wrong picture OS：debian When I was using WeChat, I found that when sending an animated gif, the same image would have different serious errors, such as misalignment, flickering, solid black(sometimes pink, brown) background . I know that using winetricks gidplus can fix this problem, but this method introduces some other problems, so I come here for help hoping to find a solution to the problem. I really need your help! ! ! Maybe you need an account for this application. Of course, it would be great if you can find a similar demo. I am trying to find a demo APP download url：https://weixin.qq.com/ -- 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 11

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