iTerm2 fails to start after the upgrade

[angelog0 (Angelo Graziosi)]

Today:

$ sudo port selfupdate
Password:
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.6.2 installed,
MacPorts base version 2.6.2 downloaded.
[...]

$ sudo port outdated
The following installed ports are outdated:
clamav                         0.102.0_1 < 0.102.0_2
iTerm2                         3.2.0_0 < 3.3.5_1
ocaml-findlib                  1.8.0_3 < 1.8.1_0
[...]

$ sudo port upgrade outdated
--->  Computing dependencies for clamav
--->  Fetching archive for clamav
[...]
--->  Fetching distfiles for clamav
--->  Verifying checksums for clamav
[...]
--->  Installing clamav @0.102.0_2
--->  Cleaning clamav
[...]
--->  Fetching archive for iTerm2
--->  Attempting to fetch iTerm2-3.3.5_1.darwin_17.x86_64.tbz2 from http://lil.fr.packages.macports.org/iTerm2
--->  Attempting to fetch iTerm2-3.3.5_1.darwin_17.x86_64.tbz2 from https://packages.macports.org/iTerm2
--->  Attempting to fetch iTerm2-3.3.5_1.darwin_17.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/iTerm2
--->  Fetching distfiles for iTerm2
--->  Verifying checksums for iTerm2
--->  Extracting iTerm2
--->  Applying patches to iTerm2
--->  Configuring iTerm2
--->  Building iTerm2
--->  Staging iTerm2 into destroot
--->  Installing iTerm2 @3.3.5_1
--->  Cleaning iTerm2
--->  Deactivating iTerm2 @3.2.0_0
--->  Cleaning iTerm2
--->  Activating iTerm2 @3.3.5_1
--->  Cleaning iTerm2
--->  Computing dependencies for ocaml-findlib
[...]

but when one tries to start iTerm2 the Dock icon appears corrupted and after a while there is a windows with a report to send to Apple (report.txt bzipped attached).

Reactivating the previous version of iTerm2 works.

[angelog0 (Angelo Graziosi)]

Just tried 3.3.6 from the site and it works as expected....

Why after building 3.3.5 MacPorts says no broken files, no broken ports etc.. and then iTerm2-3.3.5 fails to start because it cannot load a library, if I understand correctly the report?

[markemer (Mark Anderson)]

3.3.7 is being pushed soon. Let me know if that fixes things.

[angelog0 (Angelo Graziosi)]

No, fails in the same manner. It builds fine but crashes at startup. The report (attached) says it does not find a library... Reverting to iTerm2 @3.2.0_0 works.

[EJFielding (Eric Fielding)]

I forget what was happening when I added myself to the Cc: list for this ticket, but both 3.3.5 and the new 3.3.7 are working fine on my 10.14.6 Macs.

[markemer (Mark Anderson)]

Ok, so it can't find Library not loaded: @rpath/libswiftAppKit.dylib

That's interesting. I'm willing to bet it's a side effect of whatever XCode you are using and 10.13.

What Xcode did you build with?

[angelog0 (Angelo Graziosi)]

My MBP is Early 2011 and the last macOS I can use is 10.13.6 (+ all security updates). So Xcode is 10.1 (10B61). App store - Updates reports there is a new update (11.2.1) for it but is marked as NOT COMPATIBLE, and I didn't even try to update it :-( ...

[angelog0 (Angelo Graziosi)]

Out of curiosity, ​https://ports.macports.org/port/iTerm2/builds reports that on 10.13 fails to install; here it builds and installs but fails to start.

[markemer (Mark Anderson)]

Yeah, it seems I need to run the old version for 10.13 as well these days. iTerm2 will basically build on the newest. It will run on 10.12+, but building it is another story.

[markemer (Mark Anderson)]

I'm wondering if we should suggest people on 10.12 and 10.13 download from the iTerm2 website - 3.2.0 has the security flaw found in 3.3.5 and 3.3.7 should run on 10.12+ but won't build properly on >11

[kencu (Ken)]

deja vu #59053

[markemer (Mark Anderson)]

Yep - looks like the same thing.

[angelog0 (Angelo Graziosi)]

BTW, is there a way to update Xcode on 10.13.6 ?

[angelog0 (Angelo Graziosi)]

Still fails to start (3.3.12_1) after the build, in the same manner, on 10.13.6, the last one can have.

After an year we cannot update iTerm2 and we are constrained to exclude it from the update each time

sudo port upgrade outdated and not iTerm2

All this is very annoying

You should take a decision, definitively

[markemer (Mark Anderson)]

I don't have any machines running anything this old, can someone give the older versions a try? Upstream hasn't supported <10.14 for quite a while, and building is even worse, I think you need 10.15.

[kencu (Ken)]

on this page there are downloadable binaries that go back to 10.5 PPC Leopard.

<​https://iterm2.com/downloads.html>.

Once upstream has moved on, dropped systems will have to live with the last version their system supported.

A new port called iterm2-bin could be created to install that for people, or you could instead just give them the message to do it in a note or similar

[markemer (Mark Anderson)]

That's a good idea, although I haven't ever done a binary only port install, I need to figure that out.

[angelog0 (Angelo Graziosi)]

It fails to start because it lacks a dynamic library just adding that would solve this issue, I think

I think you need 10.15

I can't, it is not supported here

[kencu (Ken)]

Replying to angelog0:

It fails to start because it lacks a dynamic library just adding that would solve this issue, I think

It's a system library. iTerm2 decided not to bundle the swift libraries, and rely on system ones, whereas some other software does bundle the needed libraries.

Now -- I believe I fixed this once through some fancy surgery. #59053. I found the missing swift library somewhere, and all it's supporting libraries, and moved that set into the app bundle. Then I messed around with install_name_tool until it actually worked.

But it's too fragile to spend any time doing that again, at least for me.

[markemer (Mark Anderson)]

Oh I expected you were stuck on 10.14 - I meant that the latest versions need 10.15+ to build - I expect that 11.0 will be needed sooon.

But I think the real solution is to install binaries - I'm working on that, but it's all new to me. Does anyone have a good example to take a look at?

[angelog0 (Angelo Graziosi)]

Oh I expected you were stuck on 10.14

The last macOS version I can use is 10.13.6...

[darkfishy (A A)]

Is it just me or it is still crashing upon start for others too after upgrading to 3.4.9_0? Same crashing behaviour as before with 3.4.8_0 on macOS 10.15.7

[darkfishy (A A)]

iTerm2 @3.4.12 works on macOS 10.15.7 See ​https://trac.macports.org/ticket/63542#comment:6

[markemer (Mark Anderson)]

iTerm2 @3.4.12 works on macOS 10.15.7 See ​​https://trac.macports.org/ticket/63542#comment:6