View Single Post
Old 01-19-2024, 06:52 AM   #20
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,450
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by jbacelar View Post
Ok, it only happens on OpenSUSE 15.5, Win10 Pro, Windows 11 and Manjaro Linux. What can we do?.
It doesn't happen in Win10 Pro for me. I have spent over 2 hours trying to make it fail, using all the "clues" from this thread. Making the column small doesn't trigger it, with or without a restart. Putting the column on a viewport edge doesn't trigger it. Changing a column size has only the expected effect, the column changes size. It doesn't fail for standard or custom columns.

I don't use the View Manager. If it is the trigger then we need to know what steps are required to make it fail.

As for what you can do, perhaps sending us your metadata.db and your calibre configuration folder contents will help (use a bug report). That way we can test with your calibre configuration but not your hardware/OS. If that still doesn't fail for us then the last option is for someone to do what Kovid suggested: run from source with print statements in the updateEditorGeometry() function in delegates.py.
chaley is offline   Reply With Quote