Bug 386792

Summary: LabPlot 2.5RC2 crashes when starting without admin privileges
Product: [Applications] LabPlot2 Reporter: uwestoehr <uwestoehr>
Component: generalAssignee: Alexander Semke <alexander.semke>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: latest   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshot of the error message
difference between original Qt 5.9.2 DLL (left) and the one from LabPlot

Description uwestoehr 2017-11-12 20:30:18 UTC
Created attachment 108811 [details]
Screenshot of the error message

- log in a user to Windows that has no admin privileges
- start LabPlot 2.5RC2

-> Crash

I attached a screenshot. It Qt5Widgets is to blame here. But I wonder about that because I got the same crash with RC1 that was built with Qt 5.6.2.
Comment 1 uwestoehr 2017-11-12 20:52:55 UTC
Created attachment 108813 [details]
difference between original Qt 5.9.2 DLL (left) and the one from LabPlot

I attached another screenshot. You can see that the Qt5Widgets is not the original one from the Qt Windows installer from qt.io.

I guess the problem is a patch in the Qt that is delivered with Craft because I also had problems with this "patched" Qt.

So my proposal is to try to compile LabPlot for Windows using the official Qt libraries. Here is the QtSDK part in craftsettings.ini that works for me:

[QtSDK]
## For advanced users only
## Whether to use prebuild Qt binaries.
Enabled = True
## The path to the Qt sdk.
Path = C:\Qt\Qt5.9.2
## The version of Qt.
Version = 5.9.2
## The compiler version, if you are not sure what to use, have a look into the derectory set in QtSDK/Path.
## The compiler must be of the same type as General/KDECOMPILER.
## If you are using mingw please make sure you have installed the mingw using the Qt installer.
Compiler = msvc2015_64

I propose this because this bug is in my opinion a release blocker.
Comment 2 uwestoehr 2017-11-26 00:07:41 UTC
This bug vanished in the meantime. I'll keep it open until I could test that it is gone also with a build from Stefan.
Comment 3 uwestoehr 2017-12-13 02:50:51 UTC
(In reply to Uwe Stöhr from comment #2)
> This bug vanished in the meantime. I'll keep it open until I could test that
> it is gone also with a build from Stefan.

It is also gone in Stefan's Build -> Closing FIXED.