Bug 469718 - "Unable to find Entry point" in DLLs - crash on launching KDE Connect
Summary: "Unable to find Entry point" in DLLs - crash on launching KDE Connect
Status: REPORTED
Alias: None
Product: kdeconnect
Classification: Applications
Component: windows-application (other bugs)
Version First Reported In: 23.04.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: brute4s99
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-13 21:23 UTC by tanak.juka
Modified: 2023-05-18 08:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Errors_in_dlls_ITALIAN+FileVersions (39.90 KB, image/png)
2023-05-13 21:23 UTC, tanak.juka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tanak.juka 2023-05-13 21:23:06 UTC
Created attachment 158921 [details]
Errors_in_dlls_ITALIAN+FileVersions

Cannot provide Backtrace because I'm on Windows, as the Guidelines remarked me. Sorry!

SUMMARY
KDE Connect crashes upon launching, claiming to be "Unable to find entry point" (I get the error in Italian, but roughly that should be the translation) in two DLL libraries:
- Qt5QuickControls2.dll
- Qt5QuickTemplates2.dll
The Entry point failing in both cases is called:
?accessibleRole@QQuickItemPrivate@@UEBA?AW4Role@QAccessible@@XZ
I've installed KDE through Chocolatey install manager, and the problem started manifesting with Version 23.04.0.1335. Currently I've got .1337 installed and the issue is still present.
I've found that rollbacking to 23.04.0.1334 (latest version available as Offline Installer through KDE Connect's Download page) brings back the expected behaviour.

The issue happened on both my PCs:
- My personal PC, running Windows 10 Pro 22H2 (Build 19045.2965), on most recent security update I was given at the beginning of May;
- My work laptop, running Windows 11 to the latest patch allowed by my organisation (...sorry I can't get the specifics of the running version right now, but I should be able to update on Monday if requested).

I haven't tried the version available from the Microsoft store as I prefer to avoid the UWP format but I can give it a try if it helps discriminate the issue.

STEPS TO REPRODUCE
1. Install/Update KDE Connect through Chocolatey (as of today 2023/05/13 it installs v23.04.0.1337)
2. Launch KDE Connect (any method  of launching - from desktop shortcut up to running kdeconnect-app.exe as Administrator directly from the installation folder)
3. The error pops up in two consecutive windows, then KDE Connect closes - No tray icon, and none of its 3 processes remain.

OBSERVED RESULT
KDE Connect throws two errors, and shuts down. Its window cannot be opened, nor the tray icon is present.
No processes are left running so communication from other platforms (in my case, an Android phone) is interrupted.

EXPECTED RESULT
KDE Connect starts without errors, tray icon is open and processes keep running after launch. PC can be found from other devices while KDE Connect is running.

SOFTWARE/OS VERSIONS
Windows: 10 Pro N 22H2 (Build 19045.2965) and 
Windows: 11 (possibly an Enterprise version, can update on Monday)

ADDITIONAL INFORMATION
Attached there's a compiled image with the two consecutive errors I get, and the Properties\Details tab for the two DLLs mentioned in the errors.

I hope this was helpful in the investigation. I'm available for more information and testing if needed.
Thank you,
Tanak
Comment 1 Nicolas Fella 2023-05-17 10:58:43 UTC
Generally speaking don't use KDE Connect from Chocolatey, it's not maintained by us and doesn't get QA from us. Only the Windows Store and installers from the website are supported.

That said I can reproduce the problem with an unreleased nightly build
Comment 2 tanak.juka 2023-05-18 08:49:04 UTC
(In reply to Nicolas Fella from comment #1)
> Generally speaking don't use KDE Connect from Chocolatey, it's not
> maintained by us

I guess that's the answer for my issue for now, then! 
Can't use the MSs Store on my work PC, but I'll get the official distributed installer in the future.
Hopefully the issue will be resolved before the nightly version passes through, but thanks for checking!

I've also rechecked, and the version currently in the Download page which does not give the error is the .1322, not the .1334 as I previously written, sorry.
Thank you!