Remote Terminator slow to start after upgrading to 19.1

Questions about applications and software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
rjmoses

Remote Terminator slow to start after upgrading to 19.1

Post by rjmoses »

Weird problem which I hope I supply enough info that someone might have an idea where I can start looking.

Overview and background:

I upgraded from Mint 18.3 to 19.1 on a test system a couple of days ago. The 18.3 system was up-to-date before I began. I installed the 18 --> 19.0 upgrade, then installed the 19.1 on top of 19.0. The test system runs on Virtualbox hosted on a Windows 10 system. Virtualbox is current version. Windows 10 current on updates. The system operates off of a 512GB SSD.

I have other PCs that I use to X-Windows (either cygwin or Xming) to remotely access the Linux system.

Problem:
I like to use Terminator as my terminal emulator.

On 18.3, the Terminator program startup is almost immediate on both local and remote displays.

On 19.1, the Terminator program startup is almost immediate on the local display, BUT takes 10-11 seconds on remote displays. Terminator displays the initial screen almost immediately, but is delayed 10-11 seconds before the prompt is displayed.


Diagnosis steps:
1. I rolled 19.1 kernel back to 4.4.0.101 -- no change -- reverted back to 4.15.0.45
2. Tested xfce terminal emulator and KDE konsole--neither have the problem when started remotely.
3. I have not seen a problem with any other programs yet.

This leads me to believe it is an interaction problem between Mint 19.1 X-windows support and Terminator but I am at a loss to know where to go at this point.

Thanks in advance.

inxi -Fxzzd results follows:

System:
Host: Mint18 Kernel: 4.15.0-45-generic x86_64 bits: 64 compiler: gcc v: 7.3.0
Desktop: Xfce 4.12.3 Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic
Machine:
Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <filter>
Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek
v: VirtualBox date: 12/01/2006
CPU:
Topology: 6-Core model: AMD Phenom II X6 1035T bits: 64 type: MCP arch: K10
L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4a bogomips: 31338
Speed: 2612 MHz min/max: N/A Core speeds (MHz): 1: 2612 2: 2612 3: 2612 4: 2612
5: 2612 6: 2612
Graphics:
Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter driver: vboxvideo
v: kernel bus ID: 00:02.0
Display: x11 server: Cygwin/X Project 1.19.6 driver: modesetting
unloaded: fbdev,vesa resolution: 1920x1030~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.2.2
direct render: Yes
Audio:
Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel
bus ID: 00:05.0
Sound Server: ALSA v: k4.15.0-45-generic
Network:
Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI
port: d010 bus ID: 00:03.0
IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge
driver: piix4_smbus v: N/A port: d200 bus ID: 00:07.0
Drives:
Local Storage: total: 64.00 GiB used: 37.63 GiB (58.8%)
ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 64.00 GiB
Optical-1: /dev/sr0 vendor: VBOX model: CD-ROM rev: 1.0 dev-links: cdrom,dvd
Features: speed: 32 multisession: yes audio: yes dvd: yes rw: none
state: running
Partition:
ID-1: / size: 60.90 GiB used: 37.63 GiB (61.8%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5
Sensors:
Message: No sensors data was found. Is sensors configured?
Info:
Processes: 247 Uptime: 41m Memory: 5.82 GiB used: 1.05 GiB (18.0%)
Init: systemd runlevel: 5 Compilers: gcc: 7.3.0 clang: 7.0.1 Shell: bash
v: 4.4.19 inxi: 3.0.27
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Locked

Return to “Software & Applications”