Crouton Extension crashes after socket connect on bionic release

[clvgt12]

name: bionic
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/bionic...
crouton: version 1-20190403182822~master:174af0eb
release: bionic
architecture: amd64
xmethod: xiwi
targets: xiwi,cli-extra
host: version 12236.0.0 (Official Build) dev-channel snappy 
kernel: Linux localhost 4.4.180-16533-g77dd0cb94c17 #1 SMP PREEMPT Wed May 29 14:19:30 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/bionic...

Please describe your issue:

This is a repeatable issue on my setup.

After entering the bionic chroot, and launching an xclient in either an embedded tab or full screen mode, the Crouton Extension immediately crashes after the websocket connects.

If known, describe the steps to reproduce the issue:

1. Install crouton extension in host Chrome Browser, verify enabled
2. Build bionic chroot with 'xiwi' and 'cli-extra' targets and enter bionic chroot
3. Download an xclient e.g. firefox
4. In Chroot, run 'xiwi -T firefox' -- or -- 'xiwi -F firefox'
5. Cleanly exit xclient i.e. Ctrl-Q on Firefox
6. Repeat "Failed to retrieve InRelease" error #4 and How do I prevent my Acer C7 from sleeping when lid is closed? #5
7. Observe this ->

localhost ~ # sudo enter-chroot
Entering /mnt/stateful_partition/crouton/chroots/bionic...
CLOUD_DRIVE_MOUNT set to Google Drive
(bionic)cvitalos@localhost:~$ xiwi -T firefox

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-138-generic x86_64 Ubuntu
Current Operating System: Linux localhost 4.4.180-16533-g77dd0cb94c17 #1 SMP PREEMPT Wed May 29 14:19:30 PDT 2019 x86_64
Kernel command line: cros_secure console= loglevel=7 init=/sbin/init cros_secure root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 3686400 verity payload=PARTUUID=046e44ef-0df2-0646-85da-48d9fe657a09/PARTNROFF=1 hashtree=PARTUUID=046e44ef-0df2-0646-85da-48d9fe657a09/PARTNROFF=1 hashstart=3686400 alg=sha1 root_hexdigest=9d46994fbe98ffd502084bb3aa3edac463b54d06 salt=f87766353cd7dd6a324440403ad424718b6594a8518f0f518a2e203c4aafe841" noinitrd vt.global_cursor_default=0 kern_guid=046e44ef-0df2-0646-85da-48d9fe657a09 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic disablevmx=off  
Build Date: 25 October 2018  04:11:27PM
xorg-server 2:1.19.6-1ubuntu4.2 (For technical support please see http://www.ubuntu.com/support) 
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.1.log", Time: Wed Jun  5 20:51:56 2019
(++) Using config file: "/etc/X11/xorg-dummy.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
crouton: version 1-20190403182822~master:174af0eb
release: bionic
architecture: amd64
xmethod: xiwi
targets: xiwi,cli-extra
host: version 12236.0.0 (Official Build) dev-channel snappy 
kernel: Linux localhost 4.4.180-16533-g77dd0cb94c17 #1 SMP PREEMPT Wed May 29 14:19:30 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Connected to extension, launched crouton in a window.

Here the Crouton Extension crashes

(firefox:32312): LIBDBUSMENU-GLIB-WARNING **: 20:52:01.986: Unable to get session bus: Failed to execute child process “dbus-launch” (No such file or directory)
Timeout waiting for extension to connect.
croutonwebsocket error: Error: not connected.

8. In host Chrome Browser, Click Menu->More Tools->Extensions, Repair Crouton Extension
9. Observe the websocket connects after successful repair (the "1" appears on the "C" icon)
10. Click on the "C" Extension Icon, and Click on the session
11. Observe the Tab (or Full Screen) session opens.
12. Cleanly exit Firefox
13. Repeat from Step "Failed to retrieve InRelease" error #4

[clvgt12]

This issue may be similar to, or a duplicate of, Issue #4078

[DennisLfromGA]

Correct, closing and duping to:

• The extension corrupted after last update dev chanel(ASUS C302) The extension corrupted after last update dev chanel(ASUS C302) #4078