Mu editor on newer Macs such as Dec 2021 16" Mac Book Pro (M1x)

[mlmiller751]

What were you trying to do?

Install Mu

What steps did you take to trigger the issue?

Standard installer from .dmg file. Try to drag the app into the applications folder

What did you expect to happen?

mu.app would appear in Applications folder

What actually happened?

Error pops up: You can’t copy the item “Mu Editor.app” because its name is too long or includes characters that are invalid on the destination volume.

Operating System Version

MacOS 12.4

Mu Version

1.1.1

Other Info

It is possible to run the app direction from the .dmg file but not possible to copy "Mu Editor.app" onto the newer file system of this type of Mac.

Editor Log

No response

[carlosperate]

@ntoll I can't remember, but I think you also tried this in an M1?
I only have intel macbooks to test.

[mlmiller751]

I am trying the following workaround. 1. Install Mu on an external USB stick (FAT format) 2. Test on M1x Mac with Pico. My prediction is that it will work, meaning the underlying problem has to do with the APFS file system native to the M1x Macs. I will let you know shortly. It's a slow copy!

…

On Jun 26, 2022, at 10:44 AM, Carlos Pereira Atencio ***@***.***> wrote: @ntoll <https://github.com/ntoll> I can't remember, but I think you also tried this in an M1? I only have intel macbooks to test. — Reply to this email directly, view it on GitHub <#2274 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2YR335VRQZJLRFQBVQZWLVRCJI3ANCNFSM5ZZU3K4Q>. You are receiving this because you authored the thread.

[mlmiller751]

Sounds right. If I’m unavailable for a bit, I’m sorting through Monterey issues on my obsolete MBP.😩

…

Sent from my iPhone

On Jun 26, 2022, at 3:44 PM, Mark Miller ***@***.***> wrote: I am trying the following workaround. 1. Install Mu on an external USB stick (FAT format) 2. Test on M1x Mac with Pico. My prediction is that it will work, meaning the underlying problem has to do with the APFS file system native to the M1x Macs. I will let you know shortly. It's a slow copy! > On Jun 26, 2022, at 10:44 AM, Carlos Pereira Atencio ***@***.***> wrote: > > > @ntoll I can't remember, but I think you also tried this in an M1? > I only have intel macbooks to test. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you authored the thread. >

[mlmiller751]

Also no joy. Hence, it is a M1x issue possibly AS WELL AS an APFS issue. It doesn't like the file format and it doesn't like the code either! I posted another report, this time with mu.log and a screenshot of my hardware config (from Apple System Info). My workaround is that I am now able to use other editors such as IDLE or Emacs with the "screen" command from Terminal to access print/input activity. I was hoping to teach a University course using the Pico, possibly with Mu Editor for CircuitPython, but probably I'll tell them to use IDLE instead if they have a newer Mac. I have not tested the Mu editor on Windows 11 or on older Macs yet (but Mike has had success on an older Mac). At one point, I had gotten it to work sufficiently to see that it has some nice plotting capability, but I am no longer able to get that far with launching it. It is very odd that it worked that one time (that was launching from the disk image). It is also incredibly slow trying to start up, which I attribute to the Mac being incredibly paranoid about security. This wouldn't be so bad if it were a 1-time thing after initial installation. But I think launching it from a read-only disk image is why it takes a very long time every time (and now just doesn't ever finish launching at all). I actually end up having to do a cold boot of my Mac just to restore normal operation after a couple of tries launching Mu. I believe it is holding onto some system resources after it fails, such as PTYs. Regards, Mark

…

On Jun 26, 2022, at 3:43 PM, Mark Miller ***@***.***> wrote: I am trying the following workaround. 1. Install Mu on an external USB stick (FAT format) 2. Test on M1x Mac with Pico. My prediction is that it will work, meaning the underlying problem has to do with the APFS file system native to the M1x Macs. I will let you know shortly. It's a slow copy! > On Jun 26, 2022, at 10:44 AM, Carlos Pereira Atencio ***@***.*** ***@***.***>> wrote: > > > @ntoll <https://github.com/ntoll> I can't remember, but I think you also tried this in an M1? > I only have intel macbooks to test. > > — > Reply to this email directly, view it on GitHub <#2274 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2YR335VRQZJLRFQBVQZWLVRCJI3ANCNFSM5ZZU3K4Q>. > You are receiving this because you authored the thread. >

[ntoll]

I'm getting a new M1 Mac tomorrow. I'll try to recreate the problems you've encountered and will ping the relevant folks in the Mu core team with the expertise to help.

[mlmiller751]

Wonderful! Thank you!

…

On Jun 27, 2022, at 1:58 AM, Nicholas Tollervey ***@***.***> wrote: I'm getting a new M1 Mac tomorrow. I'll try to recreate the problems you've encountered and will ping the relevant folks in the Mu core team with the expertise to help. — Reply to this email directly, view it on GitHub <#2274 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2YR3YVI5WJTGT52UOXCUTVRFUMZANCNFSM5ZZU3K4Q>. You are receiving this because you authored the thread.

[ntoll]

So, I've just tested things with my M1 Mac. Everything just works and I encountered no problems at all. ☹️ I downloaded the Mac installer from our codewith.mu website and it all worked first time, as expected.

While this is a relief for Mu, it doesn't help with your problem.

I wonder, what is specific about your setup that means Mu can't start. Is your laptop managed in any way by a third party (for instance your employer), who may restrict the applications that can be run on the device..? Is Rosetta installed on the device (thus allowing you to run Intel binaries on M1 devices)..? I wonder if there are any system logs (not sure where) that will reveal what's interfering with Mu. I'm mostly a Linux user so I'm not sure where you'd find such things.

Thoughts?

[carlosperate]

There is a bit more info in mu-editor/crash-reports#202

[ntoll]

Thanks for the pointer @carlosperate - looks like the user is trying to launch directly from within the mounted DMG, rather than copy Mu into "Applications".

[carlosperate]

That shouldn't be a problem though, right? I'd assume it'd be the same as copying the "Mu Editor.app" bundle into another directory and launching it from there? Which I've done quite a lot to keep multiple Mu versions around.

It's worth a try, launching from the mounted dmg in a computer where we know Mu works, in case it does produce weird results, but I think in @mlmiller751's computer launching from anywhere is causing problems.

[mlmiller751]

And I only tried that because it fails to drag-install into Applications folder on APFS file system. Mark L. Miller, Ph.D. http://learningtech.org/ San Carlos, CA 94070 ***@***.*** 650-598-0105 x203

…

On Jun 29, 2022, at 7:24 AM, Carlos Pereira Atencio ***@***.***> wrote:  That shouldn't be a problem though, right? I'd assume it'd be the same as copying the "Mu Editor.app" bundle into another directory and launching it from there? Which I've done quite a lot to keep multiple Mu versions around. It's worth a try, launching from the mounted dmg in a computer where we know Mu works, in case it does produce weird results, but I think in @mlmiller751's computer launching from anywhere is causing problems. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[mlmiller751]

It is a std M1x 16” MBP nearly maxxed out. Mu has been given full disk permissions as advised etc. Still no joy. No weird security settings. Not company owned/controlled. Mark L. Miller, Ph.D. http://learningtech.org/ San Carlos, CA 94070 ***@***.*** 650-598-0105 x203

…

On Jun 29, 2022, at 7:02 AM, Nicholas Tollervey ***@***.***> wrote:  So, I've just tested things with my M1 Mac. Everything just works and I encountered no problems at all. ☹️ I downloaded the Mac installer from our codewith.mu website and it all worked first time, as expected. While this is a relief for Mu, it doesn't help with your problem. I wonder, what is specific about your setup that means Mu can't start. Is your laptop managed in any way by a third party (for instance your employer), who may restrict the applications that can be run on the device..? Is Rosetta installed on the device (thus allowing you to run Intel binaries on M1 devices)..? I wonder if there are any system logs (not sure where) that will reveal what's interfering with Mu. I'm mostly a Linux user so I'm not sure where you'd find such things. Thoughts? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[ntoll]

So, my Mac is a standard 2021 M1pro 16" MBP that has been maxxed out too... (32GB memory, 1Tb HD etc). I didn't have to give Mu any permissions (my user has admin privileges), and my laptop is actually owned by my employer so they have added security settings and virus protection over which I have no control. I can confirm the filesystem is APFS. I also have a completely up to date and fully patched OSX Monterey version 12.4.

It feels to me like we have pretty much the same setup, so I wonder what else might be different to cause the behaviour you describe..? Like I said, it all works flawlessly for me (which isn't at all helpful for this situation).

Thoughts?