Bug 500996

Summary: Qt6Gui.dll not found
Product: [Applications] kdiff3 Reporter: Jan Klass <jan.klass>
Component: applicationAssignee: michael <reeves.87>
Status: RESOLVED WORKSFORME    
Severity: crash CC: compel_kelp759
Priority: NOR    
Version First Reported In: 1.12.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: screenshot

Description Jan Klass 2025-03-03 09:54:50 UTC
Created attachment 179064 [details]
screenshot

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Install KDiff3 1.12.1 on Windows
2. Launch

OBSERVED RESULT
Error entry point `""` not found in Qt6Gui.dll

EXPECTED RESULT
KDiff3 launches

SOFTWARE/OS VERSIONS
Windows: Windows 10 Business, 22H2
Qt Version: ?

ADDITIONAL INFORMATION
I see 1.12.1 is not on the website yet, but a tag exists in the source repo, and the winget package manifest has been updated with the installer URL https://github.com/microsoft/winget-pkgs/tree/master/manifests/k/KDE/KDiff3/1.12.1
I used the installer referenced there https://download.kde.org/stable/kdiff3/kdiff3-1.12.1-windows-x86_64.exe / https://fr2.rpmfind.net/linux/KDE/stable/kdiff3/kdiff3-1.12.1-windows-x86_64.exe

When I install 1.12.0 kdiff3-1.12.0-windows-cl.exe it launches and works fine.
Comment 1 hideaki 2025-03-21 17:03:57 UTC
I have the same issue with my environment.

I installed kdiff3-1.12.1-windows-x86_64-sideload.appx, and it is working fine, but I prefer winget to install kdiff3, also obviously non-sideloaded kdiff3-1.12.1-windows-x86_64.exe is smaller.
Comment 2 michael 2025-03-21 17:57:45 UTC
Out of curiosity does upgrading to 1.12.1 work as expected I ask this because it sounds a packaging error going push 1.12.2 as 1.12.1 has a merge bug that prevents actually saving if there is an encoding error. For UTF-* you likely won't trigger trigger this as these codecs have a built-in replacement character defined so they don't flag an error for encoding issues.
Comment 3 michael 2025-03-22 14:30:54 UTC
Tarballs for 1.12.2 uploaded https://phabricator.kde.org/T17977
Comment 4 hideaki 2025-03-23 13:56:51 UTC
(In reply to michael from comment #2)
> Out of curiosity does upgrading to 1.12.1 work as expected I ask this
> because it sounds a packaging error going push 1.12.2 as 1.12.1 has a merge
> bug that prevents actually saving if there is an encoding error. For UTF-*
> you likely won't trigger trigger this as these codecs have a built-in
> replacement character defined so they don't flag an error for encoding
> issues.

I had no problem when I installed 1.12.1. note that it was "Just for me" installation.

I uninstall and install 1.12.1 again, now it works.

one thing I noticed is the installation path. in my setup, I had "%LOCALAPPDATA%\KDiff3\bin" instead of "%LOCALAPPDATA%\Programs\KDiff3\bin" in %PATH%.
I don't remember, but probably an old installer used %LOCALAPPDATA%\KDiff3 as the defualt folder for "Just for me", and recent ones use "%LOCALAPPDATA%\Programs\KDiff3\bin".
Comment 5 michael 2025-04-03 17:10:38 UTC
Looks like the path change is the reason the kdiff3 installer uses the default install path supplied by underling tooling. Unfortunately that means it can change unexpectedly. This sometimes confuses windows after an upgrade.