View Single Post
Old 11-04-2016, 08:36 PM   #2
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: 28,604
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by st_albert View Post
When I rebuilt Sigil using Qt 5.4.1 from the official Qt website (which I've used for previous Sigil versions) the problem went away. I don't know if anyone ever got to the bottom of what was going on in the older case, but maybe the problem was in the Qt package(s), not the Sigil package.
I never really heard much more about it, to tell the truth. I couldn't tell from the old thread whether those repo versions that were having the problem used Qt5.5.1. Does that version come stock with Xenial? If so, it's definitely worth looking into. I've never had any problems building Sigil against the repo versions of Qt5.6/7 on Arch, so it's possible there's something about 5.5.1.
DiapDealer is online now   Reply With Quote