View Single Post
Old 07-25-2018, 12:54 PM   #9
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,893
Karma: 6120478
Join Date: Nov 2009
Device: many
The only linux specific thing I see in that backtrace is this:

QWindowSystemInterface::sendWindowSystemEvents(QFl ags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#32 0x00007fffe769a2cb in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

libQt5XcbQpa.so is a front for a platform specific plugin (libqxcb.so)

Do you have multiple versions of Qt installed?
Do you have environment variables set that might point to incorrect Qt library plugins?

What script are you using to actually launch Sigil and does it properly set the QT_PLUGIN_PATH?
KevinH is offline   Reply With Quote