View Single Post
Old 04-21-2013, 05:40 AM   #13
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 8,754
Karma: 39457947
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Are you sure you haven't (manually) relocated your Qt5 installation after building Sigil? Even with the LD_LIBRARY_PATH env var updated to the new Qt5 location, I've seen segfaults under those conditions. It seems the path to the Qt5 platform plugins is hard coded in the various libraries (never mind that the platform plugin doesn't show up as a dependency when using ldd). You could try adding the line
Code:
export QT_DEBUG_PLUGINS=1
to your launch script (before the call to launch Sigil) to see if you get some more useful output to work with.

Last edited by DiapDealer; 04-21-2013 at 06:06 AM.
DiapDealer is offline   Reply With Quote