[Bug 56271] New: Free Download Manager no longer works after it updated (stuck at 100% CPU, no visible window)
https://bugs.winehq.org/show_bug.cgi?id=56271
Bug ID: 56271 Summary: Free Download Manager no longer works after it updated (stuck at 100% CPU, no visible window) Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: o.dierick@piezo-forte.be Distribution: ---
Created attachment 75992 --> https://bugs.winehq.org/attachment.cgi?id=75992 Free Download Manager terminal output on Wine 9.1
Hello,
Free Download Manager was working until it updated and restarted itself.
I updated Wine from 9.0-rc3 to 9.1. The application was working as usual after the Wine update. I used the menu to check for an application update and allowed it to update. Then the application downloaded some stuff and tried to restart and got hung.
After forcing everything to close, when I launch the application, there is a fdm.exe process using one core at 100% and nothing more.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=56271
David Kahurani k.kahurani@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |k.kahurani@gmail.com
--- Comment #1 from David Kahurani k.kahurani@gmail.com --- It seems like Free Download Manager does use 100% of a core even during normal circumstances because this is the case with Free Download Manager version 5.1.38.
The problems also doesn't seem related Wine version 9.1 but more or less related to FDM version 6.20(for Windows 10/11).
In my case I get additional errors relating to Qt
03e8:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. 03e8:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr par ameter qt.network.ssl: No functional TLS backend was found qt.qpa.windows: SetProcessDpiAwarenessContext(DPI_AWARENESS_CONTEXT_PER_MONITOR_ AWARE_V2) failed: COM error 0x57 (Invalid parameter.) 03e8:fixme:win:RegisterPowerSettingNotification (000000000003015C,{02731015-4510-4526-99e6-e5a17ebd1aea},0): stub 03e8:fixme:system:NtUserQueryDisplayConfig flags 0x2, paths_count 0x7ffffe1fe164, paths 0x7fffff28f1a0, modes_count 0x7ffffe1fe168, modes 0x7fffff2815a0, topology_id (nil) semi-stub 03e8:fixme:file:NtLockFile I/O completion on lock not implemented yet 03fc:fixme:netprofm:connection_point_Advise 00007F735702BE30, 00007F7357030220, 00007F735703024C - semi-stub 03fc:fixme:netprofm:list_manager_GetConnectivity 00007F735702BDF0, 00007FFFFF97BB28 03fc:fixme:netprofm:list_manager_GetNetworks flags 00000001 not supported
https://bugs.winehq.org/show_bug.cgi?id=56271
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #2 from Bernhard Übelacker bernhardu@mailbox.org --- Created attachment 76054 --> https://bugs.winehq.org/attachment.cgi?id=76054 WINEDEBUG=+pid,+netprofm wine fdm.exe
I tried the current 6.20 x86 FDM download, with wine-9.2: md5sum: 2dffb2a3f68ce9b506f4aa14ceaf433a fdm_x64_setup.exe
It looks like fdm.exe gets into an infinitife loop by looking at the network interfaces.
Attached file shows the start of a trace with +netprofm.
Unfortunately returning early from list_manager_GetNetworks is no workaround because then it could not find library for "Windows.Networking.Connectivity.NetworkInformation" and crashes.
https://bugs.winehq.org/show_bug.cgi?id=56271
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |netprofm
https://bugs.winehq.org/show_bug.cgi?id=56271
temp82@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82@luukku.com
--- Comment #3 from temp82@luukku.com --- saw this on wine's gitlab. hope it helps.
https://gitlab.winehq.org/wine/wine/-/merge_requests/5166
https://bugs.winehq.org/show_bug.cgi?id=56271
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |d2df3c2c21f02a23a5c852c83f2 | |6e2bd7483d80f Status|NEW |RESOLVED
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- This should be fixed with d2df3c2c21f02a23a5c852c83f26e2bd7483d80f.
https://bugs.winehq.org/show_bug.cgi?id=56271
--- Comment #5 from Hans Leidekker hans@meelstraat.net --- (In reply to temp82 from comment #3)
saw this on wine's gitlab. hope it helps.
Right, the app checks the return pointer instead of the return value which caused an infinite loop. It also asks for connected networks only which wasn't supported. Both bugs are fixed with that MR.
Missing library for Windows.Networking.Connectivity.NetworkInformation deserves its own report.
https://bugs.winehq.org/show_bug.cgi?id=56271
--- Comment #6 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Hans Leidekker from comment #5)
Missing library for Windows.Networking.Connectivity.NetworkInformation deserves its own report.
Hello,
That would be bug 46534, which has a staged patchset that is reported to fix that issue.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=56271
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 9.4.
https://bugs.winehq.org/show_bug.cgi?id=56271
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |9.0.x
-
WineHQ Bugzilla