OK, we're getting somewhere - removing the vlcrc file allows it to start, and when it ends, it writes a new one that allows it to continue working; here's the diff from the saved one to the good one: $ diff -c save.prefs vlcrc *** save.prefs 2020-05-23 14:15:40.000000000 -0700 --- vlcrc 2020-05-23 1...
Here's the second part: default 14:15:40.166342-0700 runningboardd Assertion 389-178-217 (target:executable<VLC(501)>) will be created as active default 14:15:40.167779-0700 runningboardd [executable<VLC(501)>:2070] Ignoring jetsam update because this process is not memory-managed default 14:15:40.1...
OK, -F doesn't change anything, I wasn't getting logs and dtruss didn't work even when I copied VLC.app to my home directory because to get it to fail, I still had to run open, so I disabled SIP with crsutil disable in recovery mode. dtruss still didn't work, but now I got log messages (too many to ...
No, it still isn't generating one. What exactly happens to invoke an app when you double click it? Maybe I can figure out a way to get a trace out of the thing...
Yeah, I agree; I also wish Apple wouldn't make dtruss useless as that would probably provide a lot of insight as well, except for the part where it works from the command line
Well, I see the crash log from the 12th and the old version of vlc ( 2.2.8 ), but the new one ( 3.0.10-15-gf39c6bc495 ) is not generating one. The window just disappears immediately and it shuts down.
Just setup a new mac mini with 10.15.4 and vlc pops up the window for about a half second then dies. Oddly enough, if I start it from the command line, it works. I did allow it the accessibility security crap, and tried installing the latest 3.0.10 version (even removed the previous installation and...