Call for testers for Sigil 2.6.0 - Beta 2 - Page 6

philja · 06-24-2025, 06:37 AM

Quote:

Originally Posted by BeckyEbook

I guess this is the case (on Mac) where checking once when opening a file doesn't work.
Probably the visibility of the Aria icons depends on the type of file last opened; if it was epub2 then the icons went gray.

I've made extensive tests including: double tapping the file in Finder to open it in Sigil; Opening Sigil and then selecting open recent file; Starting Sigil and then opening the file ...

I can't reproduce that event. I know from years of following various forums that a common solution to various laptop problems is a reboot. I reboot at least once a week and in fact the MacBook was rebooted yesterday.

I'm putting it down to "one of those things" that happen on computers from time to time.

philja · 06-24-2025, 06:51 AM

Having read Doitsu's remark about the language attribute in post #68 above, and Kevin's reply in #69, I decided to install the Access-Aide plugin.

On my MacBook, the plugin fails with the plugin launcher announcing "Launcher process crashed" and Mac announcing "Python quit unexpectedly".

I reloaded the plugin a second time, I binned Sigil.app and remade it from the Beta5 download (which had passed the checksum test after download). I tried the Access-Aide on other epub3 files, which had all passed epubcheck ok.

The plugin crashes each time on my MacBook, but works ok on my linux machine.

philja · 06-24-2025, 07:21 AM

deleted

KevinH · 06-24-2025, 09:59 AM

It doesn't incorrectly grey out the new icons on my Mac during my testing. The mac Allows multiple MainWindows so the initialization for a new Window always happen and should not depend on what any other MainWindow being epub2 or epub3.

But maybe there is a particular sequence I am missing. I will keep testing it.

KevinH · 06-24-2025, 10:10 AM

The latest version of Access-Aide requires a full installation of PySide6. Perhaps there is an issue with the embedded python engine in these Beta Builds. I will test to see if I can recreate the failure in Access-Aide in the official release and the last Beta and will get back to you.

KevinH · 06-24-2025, 11:56 AM

Okay I was able to install and run the Beta 5 version with Access-Aide v1.0.1 (the latest) with no problems at all on my Mac Book Pro (x86_64).

So I can not recreate what you are seeing at all.

If Sigil truly crashes on MacOS, the Mac should ask if you want a crash report. Please say yes and copy and paste the entire contents into a post here (maybe hide in in QUOTE tags) so that I can see what in the code may be causing the crash.

Any type of launcher errors should never really happen and so it typically indicates some type of incomplete install if Sigil or some form of disk corruption. Have you tried running Apple's official Disk Utility app and tried to test and repair your file system?

philja · 06-24-2025, 03:21 PM

Quote:

Originally Posted by KevinH

Okay I was able to install and run the Beta 5 version with Access-Aide v1.0.1 (the latest) with no problems at all on my Mac Book Pro (x86_64).

So I can not recreate what you are seeing at all.

If Sigil truly crashes on MacOS, the Mac should ask if you want a crash report. Please say yes and copy and paste the entire contents into a post here (maybe hide in in QUOTE tags) so that I can see what in the code may be causing the crash.

Any type of launcher errors should never really happen and so it typically indicates some type of incomplete install if Sigil or some form of disk corruption. Have you tried running Apple's official Disk Utility app and tried to test and repair your file system?

I just repeated the op with Access-Aide (it is the latest v1.0.1) and here is the Apple report:

Spoiler:

I'm not really into working on the Mac so it mostly gets used as a reading device (glorified tablet). I use Sigil on the Mac just so's I can tell another author how to install it. I really don't know Apple's official Disk Utility app but I'll look into it.

KevinH · 06-24-2025, 03:53 PM

The real error is here:

Code:

Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Exception Codes: UNKNOWN_0x32 at 0x0000000109ef0000
Exception Codes: 0x0000000000000032, 0x0000000109ef0000

Termination Reason: Namespace CODESIGNING, Code 2 Invalid Page

For some reason, your machine is still testing the code signatures in a BETA build of Sigil that is UNSIGNED.

It should not be doing that.

Which version of macOS are you using?

philja · 06-24-2025, 04:13 PM

It's using Sequoia 15.5

Running First Aid on the utility app doesn't produce any errors.

KevinH · 06-24-2025, 04:34 PM

Quote:

Originally Posted by philja

It's using Sequoia 15.5

Running First Aid on the utility app doesn't produce any errors.

Well at least you have no disk issues!

I am using the older Sonoma 14.7.6 for all builds and testing. So perhaps the newer Sequoia has added even more security. I would not doubt it.

You will only be able to run Plugins that use PySide6 in actual release builds I make and post that are fully signed and notarized. It seems unsigned Beta level builds will not work well on the newer Sequoia.

Sorry but there is not much I can do until the next release comes out.

philja · 06-24-2025, 04:38 PM

Quote:

Originally Posted by KevinH

Well at least you have no disk issues!
Sorry but there is not much I can do until the next release comes out.

No sweat ! I've the linux box for working and a W10 box for back-up. I'll update the MacBook when the next release is ready.

Thanks for your help in understanding the problem.

KevinH · 06-26-2025, 10:01 AM

I have been doing some testing, and it appears I can sign a CI build (made from github ci) even on an Intel Mac for Arm, and visa-versa. This will help me significantly when I am limited to a intel Mac (my laptop) during travels.

For any future betas I post, I will do that so that that they at least have a chance to run properly on newer macOS systems.

In addition, any MacOS user can use their KeyChain Utility to create a self-signing certificate for free - just for themselves (not for distribution like mine which requires money and approval from Apple). With their own certificate they can force sign anything they want to prevent MacOS from barfing on it.

So a determined user can make anything run on their own Mac OS. This is important since many tools are auto "signing" their own libraries and executables which creates issues when the main app itself is unsigned.

My signing process overwrites all other code signing signatures so that the app is properly signed.

If you ever need or want more details, or a template signing script for self-signing Sigil or PageEdit with your own signature, just let me know.

philja · 06-26-2025, 05:37 PM

Quote:

Originally Posted by KevinH

In addition, any MacOS user can use their KeyChain Utility to create a self-signing certificate for free - just for themselves (not for distribution like mine which requires money and approval from Apple). With their own certificate they can force sign anything they want to prevent MacOS from barfing on it.

If you ever need or want more details, or a template signing script for self-signing Sigil or PageEdit with your own signature, just let me know.

That sounds like a good idea. So, I did a look-up on Apple Support and found the following:

Spoiler:

Item 1 worked fine but item 2 was a complete failure. There was no sign of any Certificate Assistant - no mention, no button - nothing. I suppose I could blunder thro and try creating a cert for myself but from the Apple Support it does seem that an 'Assistant' exists. Maybe it used to but not anymore.

Can you shed any light on this?

KevinH · 06-26-2025, 07:18 PM

On my machine it apears exactly where they said it would be.

Apple sometimes tries to redirect people to its Passwords app but do not let it.

Also all MacOS supplied Applications do not live in /Applications anymore. and instead just appear to.

/Applications is where only third party applications are now stored. To protect its own apps from being modified in any way by the user they are now in /System/Applications.

So try the following in Terminal.app

cd /System/Applications/Utilities/
open "Keychain Access.app"

Then under the main Apple menubar at the top of your screen, use your mouse to click on Keychain Access, and a menu will appear that has "About Keychain Access", "Settings...", and "Certificate Assistant" should be third.

--- Update - all of that is true in Sonoma, But in Sequoia it seems to be located here:

/System/Library/CoreServices/Applications

so try the following:

cd /System/Library/CoreServices/Applications/
open "Keychain Access.app"

---

Hope this helps.

KevinH

KevinH · 06-26-2025, 07:20 PM

If that doesn't work you may need to download and install XCode to get all of the developer tools and sdks and where the codesign cli app lives.

06-24-2025, 07:21 AM	#78
philja Addict Posts: 268 Karma: 516 Join Date: Nov 2015 Location: Europe EEC Device: Kindle Fire HD6 & HD8	deleted Last edited by philja; 06-24-2025 at 07:51 AM.

06-24-2025, 09:59 AM	#79
KevinH Sigil Developer Posts: 8,783 Karma: 6000000 Join Date: Nov 2009 Device: many	It doesn't incorrectly grey out the new icons on my Mac during my testing. The mac Allows multiple MainWindows so the initialization for a new Window always happen and should not depend on what any other MainWindow being epub2 or epub3. But maybe there is a particular sequence I am missing. I will keep testing it. Last edited by KevinH; 06-24-2025 at 11:58 AM.

06-24-2025, 11:56 AM	#81
KevinH Sigil Developer Posts: 8,783 Karma: 6000000 Join Date: Nov 2009 Device: many	Okay I was able to install and run the Beta 5 version with Access-Aide v1.0.1 (the latest) with no problems at all on my Mac Book Pro (x86_64). So I can not recreate what you are seeing at all. If Sigil truly crashes on MacOS, the Mac should ask if you want a crash report. Please say yes and copy and paste the entire contents into a post here (maybe hide in in QUOTE tags) so that I can see what in the code may be causing the crash. Any type of launcher errors should never really happen and so it typically indicates some type of incomplete install if Sigil or some form of disk corruption. Have you tried running Apple's official Disk Utility app and tried to test and repair your file system? Last edited by KevinH; 06-24-2025 at 12:18 PM.

06-24-2025, 03:53 PM	#83
KevinH Sigil Developer Posts: 8,783 Karma: 6000000 Join Date: Nov 2009 Device: many	The real error is here: Code: Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)) Exception Codes: UNKNOWN_0x32 at 0x0000000109ef0000 Exception Codes: 0x0000000000000032, 0x0000000109ef0000 Termination Reason: Namespace CODESIGNING, Code 2 Invalid Page For some reason, your machine is still testing the code signatures in a BETA build of Sigil that is UNSIGNED. It should not be doing that. Which version of macOS are you using?

06-24-2025, 04:13 PM	#84
philja Addict Posts: 268 Karma: 516 Join Date: Nov 2015 Location: Europe EEC Device: Kindle Fire HD6 & HD8	It's using Sequoia 15.5 Running First Aid on the utility app doesn't produce any errors. Last edited by philja; 06-24-2025 at 04:26 PM.

06-24-2025, 06:51 AM	#77
philja Addict Posts: 268 Karma: 516 Join Date: Nov 2015 Location: Europe EEC Device: Kindle Fire HD6 & HD8	Having read Doitsu's remark about the language attribute in post #68 above, and Kevin's reply in #69, I decided to install the Access-Aide plugin. On my MacBook, the plugin fails with the plugin launcher announcing "Launcher process crashed" and Mac announcing "Python quit unexpectedly". I reloaded the plugin a second time, I binned Sigil.app and remade it from the Beta5 download (which had passed the checksum test after download). I tried the Access-Aide on other epub3 files, which had all passed epubcheck ok. The plugin crashes each time on my MacBook, but works ok on my linux machine.

06-24-2025, 10:10 AM	#80
KevinH Sigil Developer Posts: 8,783 Karma: 6000000 Join Date: Nov 2009 Device: many	The latest version of Access-Aide requires a full installation of PySide6. Perhaps there is an issue with the embedded python engine in these Beta Builds. I will test to see if I can recreate the failure in Access-Aide in the official release and the last Beta and will get back to you.

06-26-2025, 10:01 AM	#87
KevinH Sigil Developer Posts: 8,783 Karma: 6000000 Join Date: Nov 2009 Device: many	I have been doing some testing, and it appears I can sign a CI build (made from github ci) even on an Intel Mac for Arm, and visa-versa. This will help me significantly when I am limited to a intel Mac (my laptop) during travels. For any future betas I post, I will do that so that that they at least have a chance to run properly on newer macOS systems. In addition, any MacOS user can use their KeyChain Utility to create a self-signing certificate for free - just for themselves (not for distribution like mine which requires money and approval from Apple). With their own certificate they can force sign anything they want to prevent MacOS from barfing on it. So a determined user can make anything run on their own Mac OS. This is important since many tools are auto "signing" their own libraries and executables which creates issues when the main app itself is unsigned. My signing process overwrites all other code signing signatures so that the app is properly signed. If you ever need or want more details, or a template signing script for self-signing Sigil or PageEdit with your own signature, just let me know.

06-26-2025, 07:18 PM	#89
KevinH Sigil Developer Posts: 8,783 Karma: 6000000 Join Date: Nov 2009 Device: many	On my machine it apears exactly where they said it would be. Apple sometimes tries to redirect people to its Passwords app but do not let it. Also all MacOS supplied Applications do not live in /Applications anymore. and instead just appear to. /Applications is where only third party applications are now stored. To protect its own apps from being modified in any way by the user they are now in /System/Applications. So try the following in Terminal.app cd /System/Applications/Utilities/ open "Keychain Access.app" Then under the main Apple menubar at the top of your screen, use your mouse to click on Keychain Access, and a menu will appear that has "About Keychain Access", "Settings...", and "Certificate Assistant" should be third. --- Update - all of that is true in Sonoma, But in Sequoia it seems to be located here: /System/Library/CoreServices/Applications so try the following: cd /System/Library/CoreServices/Applications/ open "Keychain Access.app" --- Hope this helps. KevinH Last edited by KevinH; 06-26-2025 at 07:31 PM.

06-26-2025, 07:20 PM	#90
KevinH Sigil Developer Posts: 8,783 Karma: 6000000 Join Date: Nov 2009 Device: many	If that doesn't work you may need to download and install XCode to get all of the developer tools and sdks and where the codesign cli app lives.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Beta Testers for Sigil-2.3.0 Needed	KevinH	Sigil	71	07-22-2024 09:54 AM
Call for beta testers https://kobli.me	neuraltoxin	Kobo Developer's Corner	10	01-21-2023 12:43 AM
Another call for testers	NiLuJe	Kobo Developer's Corner	26	09-20-2019 11:25 AM
Call for testers	kovidgoyal	Calibre	289	09-19-2008 01:45 PM