Opened 2 years ago
Last modified 8 months ago
#66238 assigned defect
iTerm2 quit unexpectedly
Reported by: | jmgc | Owned by: | markemer (Mark Anderson) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.0 |
Keywords: | Cc: | rieder (Steven Rieder), i0ntempest, NinoLipartiia | |
Port: | iTerm2 |
Description (last modified by jmroot (Joshua Root))
After installing Ventura and rebuilding iTerm2 with the latest version, every time I launch iTerm2, It crashes. The reported problem is:
Termination Reason: Namespace DYLD, Code 1 Library missing Library not loaded: @rpath/BetterFontPicker.framework/Versions/A/BetterFontPicker Referenced from: <426AEB11-168B-3B9E-BC0F-21C26174C383> /Applications/MacPorts/iTerm2.app/Contents/MacOS/iTerm2 Reason: tried: '/Applications/MacPorts/iTerm2.app/Contents/MacOS/../Frameworks/BetterFontPicker.framework/Versions/A/BetterFontPicker' (code signature in <ED4B4372-9E02-37AE-ADED-0A904093467D> '/Applications/MacPorts/iTerm2.app/Contents/Frameworks/BetterFontPicker.framework/Versions/A/BetterFontPicker' not valid for use in process: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?))
Change History (13)
comment:1 Changed 2 years ago by jmroot (Joshua Root)
Description: | modified (diff) |
---|---|
Owner: | set to markemer |
Status: | new → assigned |
comment:2 Changed 2 years ago by rieder (Steven Rieder)
Cc: | rieder added |
---|
comment:3 Changed 2 years ago by rieder (Steven Rieder)
comment:4 Changed 2 years ago by rieder (Steven Rieder)
It seems a bad code signature is used to sign the BetterFontPicker framework?
comment:6 Changed 2 years ago by esafak (Emre Şafak)
As I reported on gitlab, the TeamIdentifier
is missing from /Applications/MacPorts/iTerm2.app/Contents/Frameworks/BetterFontPicker.framework/Versions/A/BetterFontPicker
, and the iterm2 executable from iterm2.com works, so this is probably a problem at macports' end.
I see a user made a patch code signing for macOS 12. It added CODE_SIGN_IDENTITY
. I suspect we need another revision to add the DEVELOPMENT_TEAM
(I assume this is the TeamIdentifier
) for macOS 13.
Does anyone know how to add @i0ntempest to this conversation?
comment:7 Changed 20 months ago by papadil
I have this issue too. Seems the other Frameworks used by iTerm2 were signed correctly as it only complains about '/Applications/MacPorts/iTerm2.app/Contents/Frameworks/BetterFontPicker.framework/Versions/A/BetterFontPicker'. Perhaps a bad assumption from my part...
comment:9 Changed 20 months ago by markemer (Mark Anderson)
Yeah - I'll take a look this evening. It's strange.
comment:10 Changed 20 months ago by markemer (Mark Anderson)
Cc: | i0ntempest added |
---|
comment:11 Changed 19 months ago by NinoLipartiia
Cc: | NinoLipartiia added |
---|
comment:13 Changed 8 months ago by paxperscientiam (Chris)
I'm interested too. Sorry, I would just subscribe to this, but I can't figure out how.
I'm experiencing the same problem.