Sigil-2.3.0 Released

[DiapDealer]

Originally Posted by KevinH

If those changes fix the issue for Windows, I will push them to master.

They fixed the issue for me on the machine I could reproduce it with.

[BeckyEbook]

I too confirm that the fix works.
Now only a single warning appears.

[KevinH]

Originally Posted by RaelIAK

downloaded Sigil.app-2.3.0-1-Mac-arm64.txz (and Sigil.app-2.3.0-1-Mac-x86_64.txz
as well), and unzipped "normally".
Yet they both refuse to even start. As 2.3.0 and previous version of Sigil.
Such a pity. I'm on a Mac, running MacOS 12.7.6

You only need one of those not both.

The arm64 one will never run on an Intel mac. Is your mac a new SOC Arm64 mac or an older Intel (x86_64) Mac?

It works on a new Mac that never once had Sigil installed (as just tested on my wife's new MacBook Air) so it should work on yours.

So I need more info.

Did you download it from the official Sigil github release page?

How exactly did you unpack the archive? Did you double-click it?

What MacOS security settings do you have set? It says something like:
- "Only allow applications downloaded from the Mac App Store"
or
- "Allow applications downloaded from the Mac App Store and Identified Third Party Developers"

You need the second one of the above selected.
(See the attached screenshot for the exact wording.)

Exactly what happens when you double-click on the Sigil.app?

Can you please provide a screenshot of the error or warning that appears?

[KevinH]

@DiapDealer and @BeckyEbook

Originally Posted by BeckyEbook

I too confirm that the fix works.
Now only a single warning appears.

Great! I will push that fix to master.

Update: Fix now in master

[theducks]

I see 1 of these when I launch Sigil from Calibre (Alt-E)
This is (properly) reporting bad content (titlepage and jacket) made by Calibre conversions

[BetterRed]

Originally Posted by DiapDealer

Strange. I couldn't reproduce the issue on my Virtual Windows 10 machines. But I WAS able to do so on a physical Windows 10 machine (only when double-clicking on the epub; just like Doitsu).

I'll test the code changes.

FWIW: I can't reproduce duplicate popups on my Win10 system no matter how I start Sigil and open the file. I tried:

• Opening Doitsu's EPUB in Sigil via Windows Open With;
• Dropping Doitsu's EPUB onto a shortcut to Sigil;
• Starting Sigil and then opening Doitsu's EPUB;
• Double clicking Doitsu's epub - after making Sigil the default handler for EPUB;
• Opening an EPUB that was saved by calibre with Sigil directly or via calibre's built-in Open With… both will invariably generate this message.

BR

[KevinH]

Yes, the code to show the warnings was being entered twice before the first time finished (while the first was waiting at the ok button to be pressed it allowed other events to be processed which in turn made the MainWindow to be activated, triggering the second).

So it is a race / timing issue that may or may not happen all of the time or even at all on some systems. My fix just prevents the race / timing issue from causing a problem.

[RaelIAK]

Thanks for your reply.
I've already used Sigil, on this Mac, for at least a couple of years, without any issue. So Sigil ISN'T brand new on my Mac. Then, in the last month I wasn't able to use Sigil anymore (can't say if because of a new download version of Sigil, or for the security OS update my Mac had in the meanwhile).
Anyway, I delete any possible old Sigil related files, using App Cleaner & Uninstaller.
Downloaded the proper Sigil installer for my intel Mac (the Sigil.app-2.3.0-1-Mac-x86_64.txz) from https://github.com/Sigil-Ebook/Sigil/releases/tag/2.3.0).
Unzipped with double click on the file (having read I wouldn't need the Terminal command anymore, which is a good thing, since I couldn't remember where I got that advice), after having moved the .txz file to the desktop.
Moved the unzipped app in my Application folder.
I have Gatekeeper disabled, so that I can run any app I want, downloaded from everywhere.

When launching Sigil (either by double click that by ctrl+click) I'm presented a very fast verifying the app small panel (which disappear on its own), and the usual warning of any new app. I click on Ok, and then nothing happens.
Sigil freezes, and all I've got is the spinning wheel...

[KevinH]

@RaelIAK,

So there is no macOS crash report? No crash, just a spinning wheel? Have you tried just waiting a couple of minutes to see if a crash happens eventually. Mac OS crash reports are quite valuable in deciphering issues.

Does your system use multiple displays? If so, try powering down all but the main one.

Are you sure you have not corrupted the file permissions on your mac?

App Cleaner and Uninstaller are not software I would recommend in any way on a Mac. Mostly they are Adware.

Did you truly disabled SIP/Gatekeeper (again not recommended at all - unless you are a developer and understand unix security approaches) or did you just set your Privacy as I showed in my first reply?

Are you using a third party anti-malware/anti-virus application? Have you tried temporarily disabling that?

And finally have you tried removing all the old Sigil settings files to make sure they are not corrupted? To do that, try the following to start up with fresh preferences for Sigil.

Open Terminal.app and type the following commands:

cd
cd Library
cd Application*Support
cd sigil-ebook
cd sigil
mv sigil_v6.ini sigil_v6_ini.keep
mv sigil.ini sigil_ini.keep

Outside of trying those, I am not sure how I can help as your system setup is very non-standard if you truly disabled SIP/Gatekeeper (ie. your computer may have issues or be infected).

One other thing to try would be to create a new user on your system, log in as that new user, and try installing and running Sigil, just in case you are auto-launching something that is interfering with Sigil in your regular account.

[RaelIAK]

@KevinH.

Actually I don't have Gatekeeper disable. Just told my Mac to open apps downloaded from any source.
I don't have multiple displays. Nor antivirus/mailware running.

Renaming sigil.ini (then recreating one when Sigil launches) sorts no results.

Sigil doesn't crash. I have to force quit it. Here's the crash resume
https://workupload.com/file/tJM5CC22VGw


I will try creating a new user on my system to see if I can use Sigil from there.

And big thanks for your good support.

[KevinH]

@RaelIAK,

The resume report showed that in Sigil in Qt6 code inside the macOS libFontRegistry.dylib was looping in the process of building up a cache of your fonts to find a fallback font to the one requested by Qt. It never seems to finish, it seems to get stuck in an infinite loop.

Have you installed third party fonts in your system?

Have you removed any Apple supplied fonts on your system?

Do you have an unusually large number of fonts on your system?

Please Try running the Mac Font Utility tool and letting it check for broken or missing fonts.

And when you renamed sigil.ini did you remember to also rename the sigil_v6.ini as I showed earlier. Both must be renamed in order to start Sigil with fresh settings.

Update:

And your resume report shows you also have a strange third party Adobe Sync product running simultaneously that might be related to the issue as it is a service that syncs fonts (files and other assets) from your mac to the Adobe Cloud Services.

My guess is the process is taking forever as Adobe Sync is adding/removing fonts from the Adobe cloud to your mac dynamically.

So turn that Adobe Sync app completely off and then try running Sigil. My guess is that is that Adobe Sync is the real problem.

In newer versions of macOS the ACCFinderSync process is disabled and removed automatically by MacOS when updating.

Process: ACCFinderSync [536]
UUID: 194CF9DF-3361-313C-80A7-511745674CE6
Path: /Applications/Utilities/Adobe Sync/*/Core Sync.app/Contents/PlugIns/ACCFinderSync.appex/Contents/MacOS/ACCFinderSync
Identifier: com.adobe.accmac.ACCFinderSync


You might want to first try launching Sigil after pausing Adobe Sync. The instructions are here:

https://helpx.adobe.com/ca/creative-...c-options.html


Be aware that really turning off Adobe Sync can be quite hard as it keeps reinstalling itself.
I would do a google search on how to remove it. Here is one blog talking about how hard it is to remove.

https://www.ctrl.blog/entry/how-to-d...loud-sync.html


After reading all the anger by customers of Adobe over the inability to turnoff this "feature" you may want remove it completely as it is acting like malware for many people.

[RaelIAK]

ALLELUJA!!!!

thanks a lot, KevinH...
disabling Adobe Cloud Sync solved the issue! ((I "hate" Adobe.. lets hope everything on its stupid side keeps on going well, on my Mac).


Thanks, again, for having took care of my problem, and for you gentle and fast answer...

[KevinH]

Glad to hear it.

Originally Posted by RaelIAK

ALLELUJA!!!!

thanks a lot, KevinH...
disabling Adobe Cloud Sync solved the issue! ((I "hate" Adobe.. lets hope everything on its stupid side keeps on going well, on my Mac).


Thanks, again, for having took care of my problem, and for you gentle and fast answer...

[wildfire070]

I may be the only one with this request, but in the previous versions of Sigil when I open several epubs in bulk that aren't well formed and need to be automatically fixed, the popup messages show up all together and I can quickly hit the enter key to confirm all the messages in bulk. With this newest update, the messages show up stacked within the individual epub windows (if that makes sense), so I have to click on each epub window individually to clear the message for each epub. Is there a way to have those messages pop up as the foremost window like it did in the previous Sigil version?

[DiapDealer]

Messagebox notifications had to be revamped in the latest version. But unless Kevin indicates differently, we probably won't be able to go back to something that accommodates your workflow. Mainly because using Sigil to make bulk epub edits (even if that's being accomplished by opening multiple instances of Sigil) is not something we're interested in accommodating. It was only working by accident in earlier versions. I'm afraid that downgrading Sigil to an earlier version might be your only option to get back to earlier behavior. Sorry.