Is it possible for two different Racket threads to use racket/gui on linux-y systems to talk to two different X servers? The only way I can think of how that would work is if the threads set the DISPLAY environment variable in the current-environment-variables parameter and that didn’t explode when GTK was called via FFI
@zaomir has joined the channel
@notjack that seems unlikely to be possible to me, but it’s more likely in racket than in other systems
I will try that and get back to you.
@eeide Which version of macOS are you running? I’m still on 10.11 (El Capitan), and the current security update didn’t affect DrRacket for me, but maybe I need to be on [High] Sierra to see the problem.
@mflatt I am running macOS 10.12.6 “Sierra.”
@eeide I updated a Sierra machine, and things still work for me. Maybe the output from Sam’s suggestion will help.
I will try that when I get back to my house, later today.
What do people here think of the idea of named partially applied functions?
@mathias.garnier69000 has joined the channel
@mflatt @samth Running bin/racket -l drracket seems to work without problem on my Mac.
Doubling-clicking the DrRacket icon yields the same error that I reported earlier, in system.log: Nov 5 12:41:40 gris com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x1000002f.DrRacket[3153]): Service exited with abnormal code: 1
Sometimes (?) I see that a volume is mounted and then quickly unmounted around the time that I run DrRacket by double-clicking on it. The volume seems to be a random hex string, different each tim—a UUID? (The mounting and unmounting is reported to me by HardwareGrowler.)
The mounting/unmounting does not happen when I run bin/racket -l drracket from the command line.
@eeide That behavior sounds like macOS trying to sandbox the application as untrusted. But the disk image that you used to install should have been signed, and so the application shouldn’t be tagged as needing a sandbox. Maybe something has gone wrong with signing, but I’d expect to have seen and heard about more problems in that case.
FWIW, I downloaded the Racket 6.11 package from the Utah mirror.
Just now, I downloaded the Racket 6.11 package again, from the Utah mirror, to another Mac running macOS 10.12.6. Double-clicking on DrRacket starts right up, no problem.
My machine on which it works is “fairly new”: an iMac (Retina 5K, 27-inch, Late 2015) with a 4GHz Interl Core i7.
My machine on which it does not work is “fairly old”: a MacBook Pro (15", Mid 2012) with a 2.6GHz Intel Core i7.
Perhaps the biggest difference between the machines is the graphics systems. Notably, my MacBook Pro does not have a retina display.
I’ve been trying via VNC to a 2012 Mac mini, so I don’t think the vintage or display is the problem Does codesign -v racket-6.11-x86_64-macosx.dmg say anything? Or codesign -v /Applications/Racket\ v6.11/DrRacket.app (if you installed to “Applications”)?
I ran both commands. Neither one produced any output.
That’s good in that no output means no detected signing problem, but it leaves me with no more guesses
Well, if you think of another hypothesis, let me know. Thanks for pondering!
:thinking_face:
@eeide Sometimes when I download a nightly build, when I run it (double-click on the icon), nothing happens, other than DrRacket seems to start to start and then quickly shuts down again. At some point in the past, someone told me (on MacOS) when this happens to drag the DrRacket icon/app out of the folder it’s in, to the folder above, and then to drag it back into the original folder and try double-clicking again. When I do that, the problem goes away and DrRacket starts normally from that point forward. I don’t know if this is related to the problem you saw, but I’m mentioning it in case it might be.
@gknauth I tried that procedure on my MacBook Pro (where DrRacket was not working), and— the problem went away!
Your trick worked!
“Huh.”
Thank you for your help, @gknauth!
@samth @stamourv hopefully for the 6.12 release you’ll be able to watch the GUI tests from your friendly neighborhood web browser https://github.com/samth/docker-racket-build/pull/18
@eeide I’m on macOS. Installing the new version was a breeze for me. Simply drag the old folder to the trash, and then the new (entire folder—after opening package) to Applications. After that, running sudo sh -c 'echo "/Applications/Racket v6.11/bin" >> /etc/paths' seems to work flawlessly. Here also is another guide for that http://beautifulracket.com/setting-the-mac-os-path.html\|beautifulracket.com/setting-the-mac-os-path.html
Thanks for the help, @dustin!