wine-bugs June 2024

1 participants
926 discussions

[Bug 38889] New: Microsoft Orca unable to create transform file
by wine-bugs＠winehq.org 16 Sep '24

16 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=38889 Bug ID: 38889 Summary: Microsoft Orca unable to create transform file Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: crosstieger(a)gmail.com Distribution: --- Created attachment 51827 --> https://bugs.winehq.org/attachment.cgi?id=51827 terminal output of the error Microsoft Orca is unable to modify cells within an .msi file. Modifying a cell returns the following error message: Could not change this cell to '<Value>'. The data was rejected by the database. It may be out of the valid range or formatted incorrectly. In the terminal you can see the error message: fixme:msidb:TABLE_modify 0x7a5098 4 0x7a5e40 - mode not implemented The value 0x7a5098 and 0x7a5e40 changes depending on the cell you edit. If you click on 'Transform - Generate Transform' and want to save your .MST file, it returns the error: Orca was unable to generate the transform. (MSI Error 120) On the terminal: fixme:msi:MsiDatabaseGenerateTransformW 3 2 L"Z:\\home\\techniktriberg\\Downloads\Untitled.mst" 0 0 The path depends on where you want to save the file. Full terminal output as an attachment. ---- Installation process ---- run: winetricks dotnet40 run: winetricks mfc42 run: msiexec -i Orca.Msi -- 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 9

[Bug 12532] New: Autodesk TrueView fails to install
by wine-bugs＠winehq.org 16 Sep '24

16 Sep '24

http://bugs.winehq.org/show_bug.cgi?id=12532 Summary: Autodesk TrueView fails to install Product: Wine Version: CVS/GIT Platform: PC URL: http://usa.autodesk.com/adsk/servlet/index?id=6703438&si teID=123112 OS/Version: Linux Status: UNCONFIRMED Keywords: download, Installer Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: xerox_xerox2000(a)yahoo.co.uk Hi, a user submitted this new app into appdb with garbage test results, so i gave it a try as well. That user reported a problem that the disk was full, but i can't reproduce that, it fails differently here. To run into this bug you need Alex Villacis' patch here: http://article.gmane.org/gmane.comp.emulators.wine.patches/49916 hopefully that patch will make it into git monday. after applying that patch the intaller failed with a message 'Call not implemented' The problem seems to be: fixme:MsiDatabaseGenerateTransformW By just returning ERROR_SUCCESS, it ran into two other unimplemnted functions: MsiQueryFeatureStateFromDescriptorA and MsiCreateTransformSummaryInfoW By stubbing these out with ERROR_SUCCESS the installer claimed to be successfull (but i guess that's doubtful). Anyway , this all shows that these three functions need to be implemented to get this installer finish, and that's where I created this bug for. -- 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 53

[Bug 51139] New: Application T@X 2021 freezes when trying to transmit data to Elster (German Tax Application)
by WineHQ Bugzilla 16 Sep '24

16 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=51139 Bug ID: 51139 Summary: Application T@X 2021 freezes when trying to transmit data to Elster (German Tax Application) Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dieter.jurzitza(a)harman.com Distribution: --- T@X20XX can be used with wine since years. This year it apparently worked as usual, with one frustrating exception: when trying to transfer the entire documetation to the finance office at the end the application freezes and does noting any more. Unfortunately no error shows in the logs when starting wine with a corresponding debug option (WINEDEBUG=+relay, I hope this is ok ...). I have 32 GByte of logging code what is meaningless to upload - but no "real" error message inside. "top" shows 100% CPU - load by the wine process stman.exe. Messages show like: 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000024) ret=089a10d6 01b8:Ret ntdll.RtlAllocateHeap() retval=3ec3bbe0 ret=089a10d6 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000024) ret=089a10d6 01b8:Ret ntdll.RtlAllocateHeap() retval=2f24da98 ret=089a10d6 01b8:Call KERNEL32.HeapFree(00220000,00000000,2f24da98) ret=0899e7eb 01b8:Ret KERNEL32.HeapFree() retval=00000001 ret=0899e7eb 01b8:Call KERNEL32.HeapFree(00220000,00000000,3ec3bbe0) ret=0899e7eb 01b8:Ret KERNEL32.HeapFree() retval=00000001 ret=0899e7eb in fast sequence and this: 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000014) ret=6be509ba 01b8:Ret ntdll.RtlAllocateHeap() retval=31991020 ret=6be509ba 0238:Call ntdll._strnicmp(17f9c7cc "Inter-| Receive | Transmit\n",17f9ca0c "eth1",00000004) ret=7eceaa21 01b8:Call ntdll.RtlAllocateHeap(00220000,00000008,00000014) ret=6be7960b 0238:Ret ntdll._strnicmp() retval=00000001 ret=7eceaa21 01b8:Ret ntdll.RtlAllocateHeap() retval=31983590 ret=6be7960b 0238:Call ntdll._strnicmp(17f9c7cd "face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed\n",17f9ca0c "eth1",00000004) ret=7eceaa21 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000020) ret=6be798c1 0238:Ret ntdll._strnicmp() retval=00000001 ret=7eceaa21 01b8:Ret ntdll.RtlAllocateHeap() retval=31992478 ret=6be798c1 0238:Call ntdll._strnicmp(17f9c7d0 "lo: 376975 3786 0 0 0 0 0 0 376975 3786 0 0 0 0 0 0\n",17f9ca0c "eth1",00000004) ret=7eceaa21 0238:Ret ntdll._strnicmp() retval=00000001 ret=7eceaa21 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,0000000c) ret=6be7974e 0238:Call ntdll._strnicmp(17f9c7ce "eth1: 727671935 574392 0 0 0 0 0 2870 31275660 279019 0 0 0 0 0 0\n",17f9ca0c "eth1",00000004) ret=7eceaa21 01b8:Ret ntdll.RtlAllocateHeap() retval=31991978 ret=6be7974e 0238:Ret ntdll._strnicmp() retval=00000000 ret=7eceaa21 cycling through eth0, eth1, wlan0 etc ... Finally I see once this at the begin (when the trouble starts ...): 01b8:Ret ntdll.RtlAllocateHeap() retval=3ecc7cc8 ret=089a10d6 01b8:Call KERNEL32.OutputDebugStringW(3ecc7cd8 L"void __thiscall BTS::FormViewerPage::enablePrevNext(void) -1 21\n") ret=67020427 01b8:Call ntdll.RtlInitUnicodeString(0021d000,3ecc7cd8 L"void __thiscall BTS::FormViewerPage::enablePrevNext(void) -1 21\n") ret=7b0125fa 01b8:Ret ntdll.RtlInitUnicodeString() retval=00000082 ret=7b0125fa with the "void __thiscall entries - but no clue on my behalf. Any support is very much appreciated, most specifically what could I do and how could I better debug the process without flooding my harddisk with trillions (ok, maybe less :-)) of messages. Thank you very much, take care Dieter Jurzitza -- 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 65

[Bug 56056] New: Exiting IrfanView full screen mode creates a redundant task bar "Untitled window" item which is not clickable
by WineHQ Bugzilla 16 Sep '24

16 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=56056 Bug ID: 56056 Summary: Exiting IrfanView full screen mode creates a redundant task bar "Untitled window" item which is not clickable Product: Wine Version: 9.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 75712 --> https://bugs.winehq.org/attachment.cgi?id=75712 "Untitled window" item Steps to reproduce: 1) Download IrfanView 2) Install/unpack and run 3) Open any image, click Enter (to enter full screen mode) 4) Click enter again (leave full screen mode) An unclickable taskbar entry will appear. -- 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 51732] New: TradeStation Installer: Unable to register servers. Setup will now abort.
by WineHQ Bugzilla 15 Sep '24

15 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=51732 Bug ID: 51732 Summary: TradeStation Installer: Unable to register servers. Setup will now abort. Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christopher.m.penalver(a)gmail.com Distribution: Ubuntu Created attachment 70617 --> https://bugs.winehq.org/attachment.cgi?id=70617 WINEDEBUG=+relay wine 'TradeStation Setup.exe' 2>&1 Hello, attempting to install TradeStation from https://update.tradestation.com/Installs/TradeStation/10.00.02.925/TradeSta… with wine 6.0.1 causes a window to pop up noting precisely: Unable to register servers. Setup will now abort. In other words, the install fails and the user is left scratching their head about why it doesn't work. -- 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 55347] New: widl generated winrt headers fails to compile with C++ code
by WineHQ Bugzilla 15 Sep '24

15 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=55347 Bug ID: 55347 Summary: widl generated winrt headers fails to compile with C++ code Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: nathbappai(a)gmail.com Distribution: --- Created attachment 74933 --> https://bugs.winehq.org/attachment.cgi?id=74933 minimal sample code If winrt headers are used with C++ code, it fails to compile with both g++ and clang++. In this case, the error comes from data types of virtual function parameters. Replacing the data types with fully qualified name fixes the compiler errors. In the attachment section, a minimal sample code is added. That code does not do anything, it's just for compilation testing purpose. It compiles fine with MSVC/Visual Studio. Firefox is one of the project which is affected by this issue. Currently, a patch is used with mingw-w64 https://hg.mozilla.org/mozilla-central/file/tip/taskcluster/scripts/misc/mi… -- 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 9

[Bug 56030] New: Left 4 Dead 2 Version 2.2.0.0 Keyboard / Mouse inputs not properly recognized.
by WineHQ Bugzilla 14 Sep '24

14 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=56030 Bug ID: 56030 Summary: Left 4 Dead 2 Version 2.2.0.0 Keyboard / Mouse inputs not properly recognized. Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- With Wine-9.0-rc1 Left 4 Dead 2 Version 2.2.0.0 does not properly recognize keyboard / mouse inputs. It seems that in some cases key state changes are ignored. I.e. The key "gets stuck" in the last read state. Causing behaviors like the player not moving despite any of the WSAD keys being held down, continuing to move in a single direction, or the player constantly firing / reloading / switching a weapon (similar to a turbo controller) despite the mouse having only been clicked / scrolled once (and the mouse not having a turbo mode). This seems to happen about once every ~15-20 seconds. Making the game unplayable. It also seems that the only way for the key to be "unstuck" is to change it's state while the game is getting input. For example, If the player is stuck firing a weapon, the player needs to manually fire the weapon again (Mouse1 by default) and release the key before the game ignores input again to make the weapon stop firing. Simply doing nothing will *not* fix the key state as far as the game is concerned. It should be noted that mouse movement does not seem to be affected by this. As the player can still use mouse look normally despite the above behaviors. -- 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 37263] New: World Of Warcraft: stuck keys
by wine-bugs＠winehq.org 14 Sep '24

14 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=37263 Bug ID: 37263 Summary: World Of Warcraft: stuck keys Product: Wine Version: 1.7.25 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: brian(a)infinityplusb.com I'm running WoW 5.4.8. At random intervals keys appear "stuck", even though they are not physically stuck. I can really only notice the ones where the "stuck key" is for moving (e,d,s,f) cause the character keeps strafing or running. Sometimes repressing these keys causes the key to unstick, but that's maybe a 20-25% success rate. Maybe less. I'm new to this bug-filing thing so I'll try replicate the issue. I'm not sure this issue is specific to Warcraft, but it's the only game I play. There are other google tracks related to this, but they seem quite old (pre-2008). -- 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 11

[Bug 33296] New: Need For Speed Most Wanted 1 - Control sticks
by wine-bugs＠winehq.org 14 Sep '24

14 Sep '24

http://bugs.winehq.org/show_bug.cgi?id=33296 Bug #: 33296 Summary: Need For Speed Most Wanted 1 - Control sticks Product: Wine Version: 1.5.27 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: vova7890(a)mail.ru Classification: Unclassified >From 1.5.17 have regression in input control on nfs mw. Pressing is delayed a few seconds after you released it. Like RELEASE action is delayed, and when, for example, pressing to left a few secconds, then release key - car stil going to the left. It reproduced not only on the that, have on any key in game. Regression still have 1.5.17 - 1.5.27, on <= 1.5.16 work fine. -- 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 25

[Bug 55849] New: Wine sends WM_(SYS)KEYUP event twice for Alt (and such) key if Fcitx/iBus daemon is running
by WineHQ Bugzilla 14 Sep '24

14 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=55849 Bug ID: 55849 Summary: Wine sends WM_(SYS)KEYUP event twice for Alt (and such) key if Fcitx/iBus daemon is running Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: emuser20140816(a)gmail.com Distribution: --- Created attachment 75355 --> https://bugs.winehq.org/attachment.cgi?id=75355 A test application I've attached an example application that reproduces this issue (win32-syskey-test.exe). The expected behavior of this application is to toggle background color (red/green) by pressing Alt (VK_MENU) key. This application behaves correctly on Windows, and behaves correctly on Wine too but only when the Fcitx/iBus daemon (with XIM integration enabled) is *not* running: WM_SYSKEYDOWN: wParam: 18, lParam: 0x20380001 WM_SYSKEYUP: wParam: 18, lParam: 0xc0380001 However, the application behaves differently on Wine if Fcitx/iBus daemon is running: WM_SYSKEYDOWN: wParam: 18, lParam: 0x20380001 WM_SYSKEYUP: wParam: 18, lParam: 0xc0380001 WM_KEYUP: wParam: 18, lParam: 0xc0380001 and the toggle switch no longer works. (This affects every application that takes a similar approach, i.e. an application that uses Alt, Ctrl or Shift key to toggle something on WM_(SYS)KEYUP event.) The workaround for this issue is either quit the Fcitx/iBus daemon (which makes IME unusable for this application) or revert the commit https://gitlab.winehq.org/wine/wine/-/commit/a4a5a2ec121eeb2a7cd4ffbb5ba7b2… (which requires complete rebuild from wine source tree). -- 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

Jump to page:

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 June 2024