MacOS 11.5.2 crash on startup #756

jjfPCSI1 · 2021-09-04T20:25:10Z

When installing the last MacOS pyzo version from the website (4.11.2), it seems to crash on startup with the given error message.

As you seem to have solve the last MacOS update problem in #731, is this somehow related or is it a new problem ?

almarklein · 2021-09-06T11:40:31Z

Hi, thank for the report! Were you using Pyzo before, and is there something that changed after which you got this error? E.g. upgraded either Pyzo or your Mac?

jjfPCSI1 · 2021-09-06T13:18:44Z

It's on a fresh computer that has not seen Pyzo before this installation.

almarklein · 2021-09-07T07:43:40Z

This looks like this description of a bug recently fixed in pyinstaller: "(macOS) Fix python shared library detection for non-framework python builds when the library path cannot be inferred from imports of the python executable. (#6021)"

almarklein · 2021-09-07T08:00:58Z

I just ran a new build with the latest PyInstaller. With some luck this fixes it. Could you please try? https://github.com/pyzo/pyzo/releases/download/v4.11.2/pyzo-4.11.2-maybefix1-macos.dmg

jjfPCSI1 · 2021-09-08T04:37:34Z

There is an error saying that Pyzo is damaged and therefore could not be open.

almarklein · 2021-09-08T07:57:45Z

LOL, I cannot open the image you linked: it cannot be displayed because it contains errors. What curse is this? :P

I uploaded another artifact. Try this one: https://github.com/pyzo/pyzo/releases/download/v4.11.2/pyzo-4.11.2-maybefix2-macos.dmg

jjfPCSI1 · 2021-09-08T12:22:15Z

Strange curse indeed because I can see it.
But it's just an image of the error message that says (in French so I have to translate): Pyzo is damaged and can't be open. You should put this item in the trash (and you're given the choice: put in trash or cancel).

No luck with the new one. Even worse: on an older MacOS (10.15.7), it's not working anymore with the same error message.

SzamCha · 2021-09-08T14:08:14Z

Hi ! Same issue with this download on MacOS 12 beta. Can you check the size of the downloaded dmg ? 86,5 MB or 86 484 551 bytes for me. — Samuel Chalifour 06 16 30 13 28 4 lotissement des Champs de la Croix 88600 Fremifontaine — Le 8 sept. 2021 à 14:22 +0200, Jean-Julien Joseph Fleck ***@***.***>, a écrit :

…

Strange curse indeed because I can see it. But it's just an image of the error message that says (in French so I have to translate): Pyzo is damaged and can't be open. You should put this item in the trash (and you're given the choice: put in trash or cancel). No luck with the new one. Even worse: on an older MacOS (10.15.7), it's not working anymore with the same error message. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

jjfPCSI1 · 2021-09-08T16:17:48Z

Hi ! Same issue with this download on MacOS 12 beta. Can you check the size of the downloaded dmg ? 86,5 MB or 86 484 551 bytes for me.

Only 32M for me, but coherent with previous downloads

 ~/Downloads>du -h pyzo*dmg
 34M	pyzo-4.11.2-macos.dmg
 32M	pyzo-4.11.2-maybefix2-macos.dmg

SzamCha · 2021-09-08T16:29:03Z

I meant the Pyzo size. Not the dmg. — Samuel Chalifour 06 16 30 13 28 4 lotissement des Champs de la Croix 88600 Fremifontaine — Le 8 sept. 2021 à 18:18 +0200, Jean-Julien Joseph Fleck ***@***.***>, a écrit :

…

> Hi ! Same issue with this download on MacOS 12 beta. Can you check the size of the downloaded dmg ? 86,5 MB or 86 484 551 bytes for me. Only 32M for me, but coherent with previous downloads ~/Downloads>du -h pyzo*dmg 34M pyzo-4.11.2-macos.dmg 32M pyzo-4.11.2-maybefix2-macos.dmg — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

jjfPCSI1 · 2021-09-08T16:58:29Z

I meant the Pyzo size. Not the dmg.

There it is:

/Applications>\du -ks pyzo*
85552	pyzo.app
92700	pyzo_working.app

pyzo_working.app being my safety net of the previous working copy.

almarklein · 2021-09-13T09:44:15Z

So, if I understand correctly, the DMG opens, and when you extract Pyzo that all works, but on starting Pyzo it produces the error?

jjfPCSI1 · 2021-09-13T09:48:00Z

That's right.

almarklein · 2021-09-13T10:27:51Z

Another attempt, using PySide2: https://github.com/pyzo/pyzo/releases/download/v4.11.2/pyzo-4.11.2-maybefix3-macos.dmg

I'm not even sure whether this is an issue with the freezing process itself of related to Qt ...

jjfPCSI1 · 2021-09-13T17:52:34Z

Still the same error either on MacOS 11.5.2 or 10.15.7. Sorry.

adddvent · 2021-09-18T08:42:10Z

My guess is that there is an outdated python3.7.0 somewhere on the computer that crashes and this also takes down pyzo.

On the first run, when there was no pyzo on the computer before, pyzo will search for all python binaries in specific places and it will run all of these binaries in a subprocess with the "-V" argument to obtain the python version string, so pyzo can suggest the user to use the binary with the highest version.
see https://github.com/pyzo/pyzo/blob/master/pyzo/util/interpreters/pythoninterpreter.py#L103
see https://github.com/pyzo/pyzo/blob/master/pyzo/util/interpreters/__init__.py

On a Linux system, invalid or missing libraries will just cause the subprocess to terminate, but I guess, that macOS 11 will also take down the parent process (pyzo).

@jjfPCSI1:
Can you check what happens when you run that python 3.7.0 manually in a bash terminal? I guess, it will crash with the same error message.
Please also try to use a dummy config file so that pyzo will not search for and execute all python binaries:
create a textfile "~/Library/Application Support/pyzo/config.ssdf" with the following contents and start pyzo afterwards:

shellConfigs2 = list:
  dict:
    name = 'Python'
    exe = '/usr/bin/python3'
    gui = 'auto'

almarklein · 2021-12-21T14:49:33Z

I revamped the whole freezing process. Could the people who are watching this please try the binary here? https://github.com/almarklein/pyzo/releases/tag/vt201 Please let me know whether it works for you!

jjfPCSI1 · 2021-12-21T19:15:37Z

Unfortunately not. I tried this version against MacOS 10.15.7 (Catalina) and still got the same "Pyzo is damaged" error as in #756 (comment)

jjfPCSI1 · 2021-12-21T19:29:12Z

@adddvent
I've just seen your past comment. But no, there are no outdated Python3.7 on my system. I've got

/usr/bin/python    # 2.7.16
/usr/bin/python3   # 3.8.2
/opt/bin/python    # 3.9.9
/opt/bin/python3.6 # 3.6.15
/opt/bin/python3.7 # 3.7.12
/opt/bin/python3.8 # 3.8.12
/opt/bin/python3.9 # 3.9.9

all of them are working versions that I use from time to time directly from the command line.

I also tried your config.ssdf file but it does not change anything.

One thing though for @almarklein , when I copy pyzo from the .dmg and start it for the first time, it takes several seconds before answering the "Pyzo is damaged" error, whereas when I start it a second (or third) time, it gives the error right away.

almarklein · 2021-12-21T20:05:50Z

Thanks for testing. I just read this page explaining that it might just be something regarding the signing: https://qiagen.secure.force.com/KnowledgeBase/KnowledgeNavigatorPage?id=kA41i000000L5swCAC

I wonder if its because we add files to the pyzo.app after it has been created (and signed) by pyinstaller ...

almarklein · 2021-12-21T21:41:23Z

I tried preventing editing the .app after it has been created. Could you try this please: https://github.com/pyzo/pyzo/releases/download/v4.11.7/pyzo-4.11.7-macos_x86_64_02.dmg If it works, please also try it a second time, I'm not sure what happens to any .pyd files that may have been created in the first run.

start it for the first time, it takes several seconds

Yeah, the very first time is known to take longer. I suppose its due to the compilation of py files, though there are not that many so it's actually surprising that the difference is so large not that I think about it. Could also be that file system caching plays a role.

jjfPCSI1 · 2021-12-22T07:13:15Z

Ok then:

with normal security settings, neither version works ;
with sudo spctl --master-disable as indicate in the link above, the version from https://github.com/almarklein/pyzo/releases/tag/vt201 is working but not the latest one from https://github.com/pyzo/pyzo/releases/download/v4.11.7/pyzo-4.11.7-macos_x86_64_02.dmg

almarklein · 2022-01-14T15:20:45Z

Could you test either/both of these please:

https://github.com/pyzo/pyzo/releases/download/v4.11.7/pyzo-4.11.7.11-macos_x86_64.zip
https://github.com/pyzo/pyzo/releases/download/v4.11.7/pyzo-4.11.7.11-macos_x86_64.dmg

almarklein · 2022-01-18T21:52:17Z

I have a Mac M1 now, and I can reproduce the original error.

The latest binaries that I linked do work for me, except that I get a warning "Pyzo can’t be opened because Apple cannot check it for malicious software." I then had to control-click it, click open, and tell it to open anyway. I'm a Mac newby, is this normal for downloaded apps, or is there something we can do to make that warning go away (e.g. signing the binary with our own signature?)

In the mean time I will probably make a new release tomorrow.

almarklein · 2022-01-20T14:10:26Z

Looks like pyinstaller/pyinstaller#5434 and may have been fixed in pyinstaller by pyinstaller/pyinstaller#5451

almarklein mentioned this issue Sep 13, 2021

Getting binary Pyzo working on Mac 11.5.2 #760

Closed

almarklein mentioned this issue Nov 29, 2021

4.11.4 broken on MacOS: damaged dmg file #769

Closed

almarklein pinned this issue Dec 21, 2021

almarklein mentioned this issue Dec 21, 2021

Let PyInstaller copy data instead of doing that afterwards #780

Merged

almarklein mentioned this issue Jan 14, 2022

fix macos frozen source dir #788

Merged

almarklein closed this as completed in #788 Jan 20, 2022

almarklein unpinned this issue Jan 20, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MacOS 11.5.2 crash on startup #756

MacOS 11.5.2 crash on startup #756

jjfPCSI1 commented Sep 4, 2021

almarklein commented Sep 6, 2021

jjfPCSI1 commented Sep 6, 2021

almarklein commented Sep 7, 2021

almarklein commented Sep 7, 2021

jjfPCSI1 commented Sep 8, 2021

almarklein commented Sep 8, 2021

jjfPCSI1 commented Sep 8, 2021

SzamCha commented Sep 8, 2021 via email

jjfPCSI1 commented Sep 8, 2021

SzamCha commented Sep 8, 2021 via email

jjfPCSI1 commented Sep 8, 2021

almarklein commented Sep 13, 2021

jjfPCSI1 commented Sep 13, 2021

almarklein commented Sep 13, 2021 •

edited

jjfPCSI1 commented Sep 13, 2021

adddvent commented Sep 18, 2021

almarklein commented Dec 21, 2021

jjfPCSI1 commented Dec 21, 2021

jjfPCSI1 commented Dec 21, 2021

almarklein commented Dec 21, 2021

almarklein commented Dec 21, 2021 •

edited

jjfPCSI1 commented Dec 22, 2021

almarklein commented Jan 14, 2022

almarklein commented Jan 18, 2022

almarklein commented Jan 20, 2022

MacOS 11.5.2 crash on startup #756

MacOS 11.5.2 crash on startup #756

Comments

jjfPCSI1 commented Sep 4, 2021

almarklein commented Sep 6, 2021

jjfPCSI1 commented Sep 6, 2021

almarklein commented Sep 7, 2021

almarklein commented Sep 7, 2021

jjfPCSI1 commented Sep 8, 2021

almarklein commented Sep 8, 2021

jjfPCSI1 commented Sep 8, 2021

SzamCha commented Sep 8, 2021 via email

jjfPCSI1 commented Sep 8, 2021

SzamCha commented Sep 8, 2021 via email

jjfPCSI1 commented Sep 8, 2021

almarklein commented Sep 13, 2021

jjfPCSI1 commented Sep 13, 2021

almarklein commented Sep 13, 2021 • edited

jjfPCSI1 commented Sep 13, 2021

adddvent commented Sep 18, 2021

almarklein commented Dec 21, 2021

jjfPCSI1 commented Dec 21, 2021

jjfPCSI1 commented Dec 21, 2021

almarklein commented Dec 21, 2021

almarklein commented Dec 21, 2021 • edited

jjfPCSI1 commented Dec 22, 2021

almarklein commented Jan 14, 2022

almarklein commented Jan 18, 2022

almarklein commented Jan 20, 2022

almarklein commented Sep 13, 2021 •

edited

almarklein commented Dec 21, 2021 •

edited