New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No text in window after upgrade to Qt 5.11 #140

vmsiam opened this Issue May 8, 2018 · 3 comments


None yet
5 participants

vmsiam commented May 8, 2018

I just upgraded to Bibletime 2.11.1 on Yosemite.
However after the upgrade I find no text in the windows. See image. Thanks for your help.


This comment has been minimized.

fullrich commented May 27, 2018

This exact thing (2.11.1) has happened to me as well on Arch Linux . Upon trying to uninstall and reinstall I received error about could not satisfy dependencies ... it was looking for sword 1.8 and all Arch has is sword1.7.4.12.


This comment has been minimized.

piater commented Jun 2, 2018

Are you sure the causes and effects are exactly as you state? I had bibletime 2.11.1-1 running fine on Arch; it stopped displaying text when Arch upgraded Qt5 from 5.10 to 5.11 [1]. I saw similar, sword-related error messages as well, but they appear to be unrelated. I suggest you try downgrading Qt5 to confirm (as I did). If this restores bibletime's funtionality, change this bug description accordingly; if not, I will file a new bug here.



This comment has been minimized.


gholmlund commented Jun 4, 2018

I have confirmed that ubuntu 18.04 and qt 5.11.0 show blank windows. Qt 5.10.1 works correctly. This appears to be a Qt 5.11.0 issue. I will investigate further.

@gholmlund gholmlund self-assigned this Jun 4, 2018

@gholmlund gholmlund added the type: BUG label Jun 4, 2018

@gholmlund gholmlund changed the title from No text in window after upgrade to No text in window after upgrade to Qt 5.11 Jun 6, 2018

@gholmlund gholmlund closed this Jun 6, 2018

@jaakristioja jaakristioja added this to the 2.11.2 milestone Jun 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment