[Bug 281334] Qt plugins cannot be found.

Patrick Spendrin ps_ml at gmx.de
Sat Sep 10 21:50:04 UTC 2011


https://bugs.kde.org/show_bug.cgi?id=281334





--- Comment #8 from Patrick Spendrin <ps_ml gmx de>  2011-09-10 21:50:04 ---
Ok, I added debug packages to our Qt now, and what I found is this: the first
call of the findConfiguration function has this backtrace:

QtCore4!QLibraryInfoPrivate::findConfiguration+0x44
QtCore4!QLibrarySettings::QLibrarySettings+0x2b
QtCore4!qt_library_settings+0x5c
QtCore4!QLibraryInfo::location+0x61
QtCore4!QCoreApplication::libraryPaths+0xa3
QtCore4!QCoreApplication::addLibraryPath+0x65
kdecore!KComponentDataPrivate::lazyInit+0x163
kdecore!KComponentData::dirs+0xc
kdecore!KConfigPrivate::KConfigPrivate+0x12c
kdecore!KConfig::KConfig+0x73
kdecore!KSharedConfig::KSharedConfig+0x4b
kdecore!KSharedConfig::openConfig+0x138
kdecore!KComponentDataPrivate::configInit+0x1b6
kdecore!KComponentDataPrivate::lazyInit+0xfd
kdecore!KComponentData::KComponentData+0x7a
kdeui!KUniqueApplication::Private::initHack+0x43
kdeui!KUniqueApplication::KUniqueApplication+0x3a
skgbasegui!SKGUniqueApplication::SKGUniqueApplication+0x33
skrooge!main+0x787
skrooge!WinMain+0x105

This means especially that the QCoreApplication instance which would be added
*after* the initHack of the KUniqueApplication::Private will not be there. This
also means that the code for the external qt.conf will never be called.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the Kde-windows mailing list