On 2022-03-18 04:41, Thiago Macieira wrote:
On Thursday, 17 March 2022 19:50:45 PDT Alexander Dyagilev wrote:
This error message is shown by Windows OS when it's failed to load a
library the process sayed it to load.
I.e. Qt calls LoadLibrary (directly, or by loading some other modules
which calls it to load another modules they depends on).
Short googling tells that it's an graphics card driver related issue
(e.g. https://github.com/spyder-ide/spyder/issues/10084).
But, maybe there is some known work around for this...
If you can generate a backtrace from the application at the moment that dialog
is shown, it can help pinpoint what was being loaded and where from. There are
too many LoadLibrary in the source code to guess which one has incorrect
parameters.
Hi, note: it's not certain that the LoadLibrary error is from Qt, for
example a similar error:
"Load Library failed with error 126: The specified module could not be
found." was found to be from within the bowels of Windows itself (non-Qt
apps also got this error).
More here about error 126:
https://forum.qt.io/topic/132880/qt-creator-error-126-running-on-windows-10-via-rdp
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
