| |
| |
On 1/29/23 19:47 Greg Ercolano wrote:
I'm coming in late here, but I see MacOS and /tmp being at issue, and
it's possible
Apple's weird new permission stuff might be getting triggered here?
[...] Perhaps apps need special access to /tmp?
Side note: it looks like "/tmp" is in reality "/private/tmp" which looks
like one of these mechanisms to make things really "private". I found
this out (accidentally) by using test/demo, enabling the "debug
terminal" and watching the output. Somehow "demo" gets the "real"
directory string. This may or may not have to do anything with the issue...
Anyway, to detect this "new" security stuff, you have to use the
/System/Applications/Utilities/Console
to monitor these errors while the app is running, as such errors
often don't get reported via
traditional unix mechanisms like errno and strerror(), and often
post dialogs asking for access
to things.
Great hint, thanks!
So if you suspect weird new Apple security stuff, first run the
Console app (mentioned above),
and hit "Start streaming", then run your app and watch for weird
error messages about your
app in the console.
The console is /very/ chatty, so you have hit "Pause" so you can
scroll around or Copy/Paste
into an editor to find errors/warnings related to your app.
I used the "search" feature and selected either "Process" fluid or "PID"
and its PID. See attached logs.
Apple's error messages in this log
about the new privacy stuff are often quite clear about what the
security/privacy problem is,
and it can sometimes be related to how the process was started,
and what limitations are set
in place for that. For instance often the /bin/sh or /bin/bash has
limitations on it that prevent
users from running things from that shell.
I can't find anything useful in these logs which I'm attaching. In both
logs 'fluid' is started, once by running `fluid/fluid` (relative path:
this hangs) and the other by `/tmp/fltk/fluid/fluid` (full path: works).
Maybe someone else can see what's happening or can test on their
system(s). Mine is macOS Ventura 13.1 on MacBook Air (M1).
The names of the logs are self-explanatory, and as far as I can see they
are very similar until the "hanging" fluid stops. Notable difference:
the "working" process issues "SetFrontProcess: asn= options=1" somewhat
later than the hanging process - and continues to work and logs more
messages.
Maybe someone else can find the underlying issue and maybe even find a
workaround?
Maybe it *has* to do with the hidden "/private" in the working directory
and app directory before "/tmp"?
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/b0452c83-862d-c4ff-1c6e-78a2eec430df%40online.de.
default 20:47:09.454663+0100 fluid Received configuration update from daemon (initial)
default 20:47:09.455020+0100 fluid CHECKIN: pid=90582
default 20:47:09.459995+0100 fluid CHECKEDIN: pid=90582 asn=0x0-0x3f72f6f foreground=0
default 20:47:09.466963+0100 fluid FRONTLOGGING: version 1
default 20:47:09.467159+0100 fluid Registered, pid=90582 ASN=0x0,0x3f72f6f
default 20:47:09.474390+0100 fluid Current system appearance, (HLTB: 1), (SLS: 0)
default 20:47:09.475229+0100 fluid No persisted cache on this platform.
default 20:47:09.478099+0100 fluid Current system appearance, (HLTB: 1), (SLS: 0)
default 20:47:09.478884+0100 fluid Post-registration system appearance: (HLTB: 1)
default 20:47:09.505992+0100 fluid SetFrontProcess: asn=0x0-0x3f72f6f options=1
default 20:47:09.509423+0100 fluid Registering for test daemon availability notify post.
default 20:47:09.509531+0100 fluid notify_get_state check indicated test daemon not ready.
default 20:47:09.509638+0100 fluid notify_get_state check indicated test daemon not ready.
default 20:47:09.509763+0100 fluid notify_get_state check indicated test daemon not ready.
default 20:47:09.515435+0100 fluid SignalReady: pid=90582 asn=0x0-0x3f72f6f
default 20:47:09.516592+0100 fluid SIGNAL: pid=90582 asn=0x0x-0x3f72f6f
default 20:45:22.806660+0100 fluid Received configuration update from daemon (initial)
default 20:45:22.810247+0100 fluid CHECKIN: pid=90567
default 20:45:22.812982+0100 fluid CHECKEDIN: pid=90567 asn=0x0-0x3f66f63 foreground=0
default 20:45:22.818181+0100 fluid FRONTLOGGING: version 1
default 20:45:22.818262+0100 fluid Registered, pid=90567 ASN=0x0,0x3f66f63
default 20:45:22.821027+0100 fluid Current system appearance, (HLTB: 1), (SLS: 0)
default 20:45:22.822096+0100 fluid No persisted cache on this platform.
default 20:45:22.824229+0100 fluid Current system appearance, (HLTB: 1), (SLS: 0)
default 20:45:22.824667+0100 fluid Post-registration system appearance: (HLTB: 1)
default 20:45:22.834884+0100 fluid Registering for test daemon availability notify post.
default 20:45:22.835021+0100 fluid notify_get_state check indicated test daemon not ready.
default 20:45:22.835172+0100 fluid notify_get_state check indicated test daemon not ready.
default 20:45:22.835306+0100 fluid notify_get_state check indicated test daemon not ready.
default 20:45:22.837311+0100 fluid SignalReady: pid=90567 asn=0x0-0x3f66f63
default 20:45:22.837647+0100 fluid SIGNAL: pid=90567 asn=0x0x-0x3f66f63
default 20:45:22.847405+0100 fluid SetFrontProcess: asn=0x0-0x3f66f63 options=1
default 20:45:22.868127+0100 fluid NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 0
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x60000312ef80
(
"<NSAquaAppearance: 0x60000312f000>",
"<NSSystemAppearance: 0x600003120b00>"
)>
default 20:45:22.877604+0100 fluid order window front conditionally: 404 related: 0
default 20:45:22.894095+0100 fluid Initializing connection
default 20:45:22.894133+0100 fluid Removing all cached process handles
default 20:45:22.894150+0100 fluid Sending handshake request attempt #1 to server
default 20:45:22.894161+0100 fluid Creating connection to com.apple.runningboard
default 20:45:22.894705+0100 fluid Handshake succeeded
default 20:45:22.894720+0100 fluid Identity resolved as anon<fluid>(501)
default 20:45:22.914680+0100 fluid order window front conditionally: 404 related: 0
default 20:45:22.914845+0100 fluid order window front conditionally: 404 related: 0
default 20:45:23.938332+0100 fluid order window front conditionally: 409 related: 0
default 20:45:25.497169+0100 fluid order window: 409 op: 0 relative: 0 related: 0
default 20:45:27.675863+0100 fluid Entering exit handler.
default 20:45:27.675914+0100 fluid Sending exit barrier. activeSendTransactions=0
default 20:45:27.676070+0100 fluid Exiting exit handler.
[ Direct Link to Message ] | |
|
| |
