[sage-support] Sage-6.5-x86_64_Darwin-OSX_10.7_x86_64-app does not seem to run

2015-02-27 Thread Murray Eisenberg
I downloaded, verified MD5 checksum for, and opened sage-6.5-x86_64-Darwin-OSX_10.7_x86_64-app.dmg on my iMac running OS X 10.10.2, then moved the app into my Applications folder. After the usual nod to Apple's security about the app, I opened it. While Activity Monitor shows it's running,

[sage-support] Re: Sage-6.5-x86_64_Darwin-OSX_10.7_x86_64-app does not seem to run

2015-02-27 Thread Murray Eisenberg
D'oh, never mind, sorry! I missed the separate 10.10 .dmg near the bottom of the download page. On Friday, February 27, 2015 at 9:17:22 PM UTC-5, Murray Eisenberg wrote: I downloaded, verified MD5 checksum for, and opened sage-6.5-x86_64-Darwin-OSX_10.7_x86_64-app.dmg on my iMac running OS

[sage-support] Re: SageMath 8.5 Crash Report

2018-12-31 Thread Murray Eisenberg
Re my previous message that I had the same crash (in fact, causing a kernel panic) at tend of .dmg's verification by macOS 10.14.2: I _did_ check the md5 checksum, and it was OK. On Saturday, December 29, 2018 at 2:04:39 PM UTC-5, ahaus...@umassd.edu wrote: > > Hi, > > > I have attempted to

[sage-support] Re: SageMath 8.5 Crash Report

2018-12-31 Thread Murray Eisenberg
I "solved" this issue finally by disabling my Intego VirusScan and then opened the .dmg.app again. The verification process proceeded without incident. Scanned the resulting .app with ClamXAV: seems OK. Was able then to open the app and use it. But _something_ is odd about the .dmg's for this

[sage-support] Re: SageMath 8.5 Crash Report

2019-01-01 Thread Murray Eisenberg
Are any of you reporting this crash when opening the 8.5 .dmg also, like me, using Intego's VirusBarrier? On Saturday, December 29, 2018 at 2:04:39 PM UTC-5, ahaus...@umassd.edu wrote: > > Hi, > > > I have attempted to install SageMath 8.5 on a 15" 3.1 GHz Intel Core i7 > 16GB 2017 MacBook

[sage-support] Re: SageMath 8.5 Crash Report

2018-12-30 Thread Murray Eisenberg
Same crash - with kernel panic reported - at end of process of process of verifying when opening sage-8.5-OSX_10.14.2-x86_64.app under macOS 10.14.2. Tried downloads from both UW and MIT, with same result. I've never seen this happen before, even when opening/verifying MUCH larger dmg's (e.g.,

[sage-support] Re: Sage 9.0 macOS Jupyter Server failed to start

2020-01-05 Thread Murray Eisenberg
Note that I *can* first start sage in Terminal (by executing there /Applications/SageMath-9.0-app/sage) Terminal, then from the sage command line execute: !sage -n jupyter On Sunday, January 5, 2020 at 2:39:50 PM UTC-5, Murray Eisenberg wrote: > > When I open SageMath-9.0.app under

[sage-support] Sage 9.0 macOS Jupyter Server failed to start

2020-01-05 Thread Murray Eisenberg
When I open SageMath-9.0.app under macOS Catallina (10.15.2), I get an immediate pop-up error window saying, "Jupyter Server failed to start". The log shows: ┌┐ │ SageMath version 9.0, Release Date: 2020-01-01

[sage-support] Re: Jupiter Server fails to start on macOS Catalina

2020-01-06 Thread Murray Eisenberg
I separately reported the same behavior -- the Jupyter server not starting with SageMath-9.0 -- and so tried the suggestion of APP=/Applications/SageMath-9.0.app xattr -dr com.apple.quarantine $APP reportedthe latter both as shown and with "sudo". This does *not* fix the problem! On

[sage-support] Re: Jupiter Server fails to start on macOS Catalina

2020-01-06 Thread Murray Eisenberg
Giving SageMath-9.0 full disk access works for me, too. It seems like a rather blunt solution for getting around Catalina's increased security! Is it full disk access that's really required? Or just the ability to launch a terminal process? On Monday, January 6, 2020 at 5:04:35 AM UTC-5, Eric