January 2022 - Wine-Bugs - list.winehq.org

[Bug 50516] New: Broken link 'https://wiki.winehq.org/Useful_Registry_Keys'
by WineHQ Bugzilla April 9, 2022

April 9, 2022

https://bugs.winehq.org/show_bug.cgi?id=50516 Bug ID: 50516 Summary: Broken link 'https://wiki.winehq.org/Useful_Registry_Keys' Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: jose.relland(a)free.fr Distribution: --- Hi, thank you for your time. I noted that the linnk: "Wine Man Page" (at the bottom of the page) is broken. Send to 404 page error. Best 2021 year :) José from France -- 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 50512] New: Wiki /Bugs links broken, can't edit them
by WineHQ Bugzilla April 9, 2022

April 9, 2022

https://bugs.winehq.org/show_bug.cgi?id=50512 Bug ID: 50512 Summary: Wiki /Bugs links broken, can't edit them Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: ddascalescu+wine(a)gmail.com Distribution: --- I've created an account to edit the wiki. May I please have permission to do so? I'm User:Dandv on Wikipedia as well. Due to the extensive reorg of https://wiki.winehq.org/Wine_User's_Guide, the links at https://wiki.winehq.org/Bugs in "You installed and ran the application using Wine, not on your Windows installation" are broken. -- 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 52340] New: wine-mono + RMS Express: COM Port errors connecting to radios
by WineHQ Bugzilla April 8, 2022

April 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=52340 Bug ID: 52340 Summary: wine-mono + RMS Express: COM Port errors connecting to radios Product: Wine Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: eric.wheez(a)gmail.com Distribution: --- Hello again, I just wanted to report in a "not implemented" exception in wine-mono. I believe that "System.IO.Ports.SerialPort.set_ReceivedBytesThreshold" not implemented in wine-mono is causing RMS Express to not be able to control the radio (channel selection and "push-to-talk"/"PTT" switch) over USB connection. Normal behavior is for RMS Express to tell the radio what radio channel to send/receive on & when to transmit/listen (via PTT switch). This behavior is working on RMS Express via Windows. This behavior is also working with RMS Express on Debian 10 VM with wine & .NET 4.6 (I had to set `sudo adduser $USER dialout && sudo reboot` to set permissions for the COM port for the user account so before channels/PTT worked .NET 4.6 though). The not implemented exception pops up in the linux terminal with wine-mono exactly at the same time that the (known-working-with-.NET4.6) COM port is said to be inaccessible. I've included the short log of the wine-mono not implemented exception at the of this post. [Setup] OS: Debian 10 (VMware Workstation on a Windows laptop) Wine: wine-7.0-rc4 devel Wine Mono: wine-mono 2f50d2c (https://nightly.link/madewokherd/wine-mono/actions/artifacts/131614059.zip) Program: Winlink Express 1.5.44.0 Radio: Yaesu FT-891 transceiver (with dummyload attached directly to radio - no feed line so I don't accidentally send signals) Details: - FT-891 connected to PC via USB cable (and make sure VMWare has the USB line routed into the VM instead of the host PC) - I set the FT-891's on-board settings to data 'baud' 9600. - I set in/out audio devices in ARDOP settings on the PC. Thank you again! And here's to 2022 being better than the previous two years :) Cheers ---- wine-mono not implemented exception log: ``` WINE_MONO_TRACE=E:System.MissingMethodException MONO_INLINELIMIT=0 WINE_MONO_HIDETYPES=1 wine RMS\ Express.exe ... [00000024:] EXCEPTION handling: System.NotImplementedException: The method or operation is not implemented. "<unnamed thread>" tid=00000024 this=04570120 , thread handle : 01df5788, state : not waiting at System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x0000f] in <117354a27af94c36af91c072a84e6fb8>:0 at (wrapper remoting-invoke-with-check) System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x00032] in <117354a27af94c36af91c072a84e6fb8>:0 at RMS_Express.Radio.OpenControlPort () [0x000b3] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Radio.SetRadio () [0x0014f] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Radio.SetFrequency (int,string) [0x00021] in <25c56d5497bc4490bd1b5395b173c5df>:0 at (wrapper remoting-invoke-with-check) RMS_Express.Radio.SetFrequency (int,string) [0x00033] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.ArdopSession.Ardop_Activated (object,System.EventArgs) [0x00823] in <25c56d5497bc4490bd1b5395b173c5df>:0 at System.Windows.Forms.Form.OnActivated (System.EventArgs) [0x0001f] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.set_Active (bool) [0x000a6] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.WmActivate (System.Windows.Forms.Message&) [0x0001a] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.WndProc (System.Windows.Forms.Message&) [0x001b8] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.OnMessage (System.Windows.Forms.Message&) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) [0x000b3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00025] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper native-to-managed) System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) <0x00067> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Windows.Forms.SafeNativeMethods.ShowWindow (System.Runtime.InteropServices.HandleRef,int) <0x00012> at System.Windows.Forms.Control.SetVisibleCore (bool) [0x00061] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.SetVisibleCore (bool) [0x000d1] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.set_Visible (bool) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.Show () [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at RMS_Express.ArdopSession.ShowSession () [0x00000] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Main.StartSession () [0x005fd] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Main.mnuSession_Click (object,System.EventArgs) [0x00000] in <25c56d5497bc4490bd1b5395b173c5df>:0 at System.Windows.Forms.ToolStripItem.RaiseEvent (object,System.EventArgs) [0x0001b] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.OnClick (System.EventArgs) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripMenuItem.OnClick (System.EventArgs) [0x0001d] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.HandleClick (System.EventArgs) [0x00051] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.HandleMouseUp (System.Windows.Forms.MouseEventArgs) [0x000fd] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.FireEventInteractive (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00053] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00103] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00033] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStrip.OnMouseUp (System.Windows.Forms.MouseEventArgs) [0x0007d] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.WmMouseUp (System.Windows.Forms.Message&,System.Windows.Forms.MouseButtons,int) [0x001c3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message&) [0x005a0] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message&) [0x00043] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStrip.WndProc (System.Windows.Forms.Message&) [0x00128] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.MenuStrip.WndProc (System.Windows.Forms.Message&) [0x00056] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.OnMessage (System.Windows.Forms.Message&) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) [0x000b3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00025] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper native-to-managed) System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) <0x00067> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW (System.Windows.Forms.NativeMethods/MSG&) <0x00012> at System.Windows.Forms.Application/ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop (intptr,int,int) [0x001d7] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoopInner (int,System.Windows.Forms.ApplicationContext) [0x00282] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x0001a] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x00033] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext) [0x00006] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun () [0x00044] in <e344caf534bf4ffb982376a141ed987b>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel () [0x00035] in <e344caf534bf4ffb982376a141ed987b>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run (string[]) [0x0001b] in <e344caf534bf4ffb982376a141ed987b>:0 at RMS_Express.My.MyApplication.Main (string[]) [0x0000f] in <25c56d5497bc4490bd1b5395b173c5df>:0 at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) [0x00027] in <25c56d5497bc4490bd1b5395b173c5df>:0 ``` -- 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

[Bug 42309] New: The Crew (Uplay) crashes at start
by wine-bugs＠winehq.org April 8, 2022

April 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=42309 Bug ID: 42309 Summary: The Crew (Uplay) crashes at start Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 57043 --> https://bugs.winehq.org/attachment.cgi?id=57043 Unhandled page fault read access to 0x0 in 64-bit code backtrace After the loading screen has closed, the screen goes black and then wine crashes with a read access to 0x00000000 in 64-bit code. The terminal is also filled with DirectX 11 fixme's. Tested on wine 2.0 + staged patch from bug 41356. -- 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 21

[Bug 51437] New: If Windows version changes from 7 to 10, Microsoft Edge calls unimplemented function uiautomationcore.dll.UiaRaiseAutomationPropertyChangedEvent
by WineHQ Bugzilla April 8, 2022

April 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=51437 Bug ID: 51437 Summary: If Windows version changes from 7 to 10, Microsoft Edge calls unimplemented function uiautomationcore.dll.UiaRaiseAutomationPropertyChanged Event Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: uiautomationcore Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Steps to reproduce: 1. Install Wine Staging (Edge will not start on vanilla Wine). 2. Run `wine MicrosoftEdgeSetup.exe` (make sure to download the installer for Windows 7). 3. Run `winecfg` and change the Windows version from 7 to 10. 4. Run `wine msedge`. If the Windows version is set to 10 from the beginning (and Edge's Windows 10 installer is used), the crash does not occur. However, it's a reasonable use case to install Edge with default Wine settings and then "upgrade" Wine to Windows 10 later. $ sha256sum MicrosoftEdgeSetup.exe c449a35ff96012ae26336ff630ced945d85f83b162b041606549c555b8a997c8 -- 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 50158] New: Oculus Runtime won't start: "Could not load file or assembly 'Daybreak'"
by WineHQ Bugzilla April 8, 2022

April 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=50158 Bug ID: 50158 Summary: Oculus Runtime won't start: "Could not load file or assembly 'Daybreak'" Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: criteria32(a)gmail.com Distribution: --- Created attachment 68674 --> https://bugs.winehq.org/attachment.cgi?id=68674 Crash log Can be downloaded at oculus.com/setup or with this direct link: https://www.oculus.com/download_app/?id=1582076955407037 -- 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 17

[Bug 45103] New: FlixGrab: Crashes on launch after showing the splash screen
by wine-bugs＠winehq.org April 7, 2022

April 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=45103 Bug ID: 45103 Summary: FlixGrab: Crashes on launch after showing the splash screen Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lucas.halbig(a)gmail.com Distribution: --- Created attachment 61276 --> https://bugs.winehq.org/attachment.cgi?id=61276 backtrace file when app crashed When attempting to launch https://www.freegrabapp.com/flixgrab after installation it failes to go past the splash screen. -- 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 8

[Bug 50460] New: Regression on installing mdac28 on 6.0-rc5 was ok in 5.0.4
by WineHQ Bugzilla April 7, 2022

April 7, 2022

https://bugs.winehq.org/show_bug.cgi?id=50460 Bug ID: 50460 Summary: Regression on installing mdac28 on 6.0-rc5 was ok in 5.0.4 Product: Wine Version: 6.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pierre(a)couderc.eu Distribution: --- Created attachment 69085 --> https://bugs.winehq.org/attachment.cgi?id=69085 log of the trial Using : sudo rm -rI .wine/ WINEARCH=win32 winecfg winetricks mdac28 wine .wine/drive_c/windows/system32/odbcad32.exe fails on last version (from winehq-devel from deb https://dl.winehq.org/wine-builds/debian/ bullseye main debian) and is ok with default bullseye release (5.0.4). odbcad32.exe box is not displayed. Full (small...) listing in attachment I am not able to know if the problem is wine or winetricks. But I am surprised that msado15 is installed as ado is not needed for mdac adn odbs... -- 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 51901] New: Warcraft 3 disconnects Randomly when using bonjour service and w3champions
by WineHQ Bugzilla April 5, 2022

April 5, 2022

https://bugs.winehq.org/show_bug.cgi?id=51901 Bug ID: 51901 Summary: Warcraft 3 disconnects Randomly when using bonjour service and w3champions Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: kostile(a)gmail.com Distribution: --- I didn't get a full trace log, but below is the output I get when the game disconnects randomly: npacked/flo-worker.exe: /home/ubuntu/buildbot/runners/wine/wine-src/dlls/ntdll/unix/thread.c:1773: ntdll_set_exception_jmp_buf: Assertion `!jmp || !ntdll_get_thread_data()->jmp_buf' failed. 0630:err:virtual:virtual_setup_exception nested exception on signal stack in thread 0630 addr 0x7fd6118a5d22 stack 0x67fbddb0 There doesn't seem to be any reason, it just randomly disconnects. Could be 2 minutes into a game or 30 minutes into a game. -- 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 48758] New: ConEmu Ctrl+c has different behavior
by WineHQ Bugzilla March 30, 2022

March 30, 2022

https://bugs.winehq.org/show_bug.cgi?id=48758 Bug ID: 48758 Summary: ConEmu Ctrl+c has different behavior Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- In ConEmu, Ctrl+c behavior is different on Wine and Windows. ConEmu+Cmd on Windows: Ctrl+c breaks current command and starts new empty prompt Ctrl+C shows ^C ConEmu+Cmd on Wine: Ctrl+c shows 'c' Ctrl+C terminates ConEmu completely ConEmu+Far Manager+console application on Windows: Ctrl+c terminates the application Ctrl+C shows ^C ConEmu+Far Manager+console application on Wine: Ctrl+c does nothing or shows 'c' Ctrl+C terminates the application -- 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 17