search

xibbon / LaTerminal

50 stars 2 forks source link

The setting keep alive: native does not work at all for me. I have a host running Ubuntu 20.04 with... #26

Closed instabug[bot] closed 1 year ago

instabug[bot] commented 1 year ago

:clipboard: Bug Details

The setting "keep alive: native" does not work at all for me. I have a host running Ubuntu 20.04 with default OpenSSH. The only "unusual" thing is that it is on port 2345 instead of 22.

What I mean is that it does seem to connect, it reports a bunch of success status messages (see screenshot) -- and then nothing happens. I've waited a couple minutes, bnut nothing

This is on an iPad Pro 11" with iOS 15, and I am using a keyboard case to type

Trying to connect with "keep alive: tmux" or "keep alive: none" does work, though with "none" another strange thing happens: pressing "return" on my physical keyboard does not work as expected in bash terminal prompts; though ctrl-return does. While in tmux mode, "return" works as expected in a bash prompt. (I only mention this in case it gives a hint as to what might be wrong).

I also tried the "Process Explorer" option while in tmux mode and also with "keep alive: none" but in both cases this opens an empty window (see 2nd screenshot). Again, I only mention this in case it gives a hint.

key value
Reported At 2022-09-27 16:19:44 UTC
Categories Report a bug
App Version 1.0.4 (263)
Session Duration 784
Device iPad13,4, iOS 15.7
Display 1194x834 (@2x)

:point_right: View Full Bug Report on Instabug :point_left:

:iphone: View Hierarchy

This bug was reported from LaTerminal.TerminalViewController Find its interactive view hierarchy with all its subviews here: :point_right: Check View Hierarchy :point_left:

:chart_with_downwards_trend: Session Profiler

Here is what the app was doing right before the bug was reported:

Key Value
CPU Load 3.4%
Used Memory 1.2% - 0.06/5.0 GB
Used Storage 68.5% - 163.2/238.36 GB
Connectivity WiFi - Unknown
Battery 89% - unplugged
Orientation landscape

Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: View Full Session Profiler :point_left:

:mag_right: Logs

User Steps

Here are the last 10 steps done by the user right before the bug was reported:

16:04:02 Top View: _TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVS_7AnyViewVS_24NavigationColumnModifier__
16:04:02 Tap in UIDimmingView in _TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVVS_22_VariadicView_Children7ElementVS_24NavigationColumnModifier__
16:03:58 Scroll in SwiftUI.UpdateCoalescingTableView in _TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVVS_22_VariadicView_Children7ElementVS_24NavigationColumnModifier__
16:03:56 Top View: _TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVVS_22_VariadicView_Children7ElementVS_24NavigationColumnModifier__
16:03:55 Top View: HostEditView
16:03:55 Scroll in SwiftUI.UpdateCoalescingTableView in _TtGC7SwiftUI19UIHostingControllerGVS_15ModifiedContentVS_7AnyViewVS_24NavigationColumnModifier__
16:03:53 Application: DidBecomeActive
16:03:53 Application: SceneDidActivate
16:03:52 Application: WillEnterForeground
16:03:19 Application: DidEnterBackground

Find all the user steps done by the user throughout the session here: :point_right: View All User Steps :point_left:

:warning: Looking for More Details?

  1. Network Log: we are unable to capture your network requests automatically. If you are using AFNetworking or Alamofire, check the details mentioned here.
  2. User Events: start capturing custom User Events to send them along with each report. Find all the details in the docs.
  3. Instabug Log: start adding Instabug logs to see them right inside each report you receive. Find all the details in the docs.
  4. Console Log: when enabled you will see them right inside each report you receive. Find all the details in the docs.
migueldeicaza commented 1 year ago

This should be fixed