https://bugs.kde.org/show_bug.cgi?id=400178
Erik Duisters <e.duiste...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |e.duiste...@gmail.com
--- Comment #46 from Erik Duisters <e.duiste...@gmail.com> ---
After playing around with a KDE Neon VM I noticed the following error in
~/.xsession-errors:
kdeinit5: Got EXEC_NEW
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' from launcher.
kdeinit5: preparing to launch
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so'
QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::applicationDirPath: Please instantiate the QApplication
object first
QCoreApplication::applicationFilePath: Please instantiate the QApplication
object first
QCoreApplication::arguments: Please instantiate the QApplication object first
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = path = pid = 2439
KCrash: Arguments: kdeinit5: PID 2439 terminated.
That got me looking at other KIO slaves (eg ftp) and apparently things have
changed a bit:
Instead of a .properties file they now use a .json file to define the plugins
metadata and embed that using a dummy class having Q_PLUGIN_METADATA(IID "xxx"
FILE "xxx.json")
Then in the kdemain function they initialize a QCoreApplication object.
Last but not least I now had to move kio_kdeconnect.so to
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/
Let me do some more test to see if it also works on my fedora system and I'll
upload the patch to phabricator
--
You are receiving this mail because:
You are watching all bug changes.
