View Single Post
Old 04-29-2020, 12:10 PM   #108
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
I can replicate this on the frozen Linux binaries. Removing and regenerating the file calibre-4.99.4-x86_64/lib/python3.8/site-packages/calibre/gui2/preferences/look_feel_ui.pyc based on the py3 branch was sufficient to get it to work.

The problem doesn't manifest if, like me, you build your own or use the CALIBRE_DEVELOP_FROM environment variable pointed at a copy of the source. In that case, calibre/gui2/preferences/look_feel.ui will be regenerated with pyuic and the problem will go away.

Looks like something went wrong in the build environment. The source code is fine though.
eschwartz is offline   Reply With Quote