View Single Post
Old 09-03-2024, 05:11 PM   #26
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,906
Karma: 6120478
Join Date: Nov 2009
Device: many
Quote:
Originally Posted by BeckyEbook View Post
Hmmm… On my system (Windows 10 Pro) Sigil closes totally.

I am not able to click the “Show Details...” button because Sigil just shuts down.

Tested on 2.3.0 original + 2.3.1 my build.
Sigil 2.3.0 will segfault due to the warning message causing a crash. Sigil 2.3.1 caught the exception, warning you that it may need to close. Having a corrupt (missing files) in the manifest but one that is referenced from elsewhere will do that.

It is not a bug as far as I am concerned as once the manifest can not be trusted, what can you do but error out letting the user know. My guess if you enable the Sigil DEBUG log file using an environment variable you might hopefully get more information.

I am nicely seeing the reason in the details and no closing at all.

Last edited by KevinH; 09-03-2024 at 05:19 PM.
KevinH is offline   Reply With Quote