Chrome Crashing on Startup

How it works in WTware without terminal server
Post Reply
effin_dead_again
Posts: 20
Joined: Tue Dec 18, 2018 10:40 pm

Chrome Crashing on Startup

Post by effin_dead_again »

All,

I'm evaluating WTWare and the platform is promising, but I'm trying to get Chrome to launch and it's crashing when it attempts to start:

Code: Select all

[            gm] [ 2743.361728] Run '/usr/lib/chromium/chromium --window-size=1920,1080 --window-position=0,0 --disable-ipv6 --disable-gpu --wm-window-animations-disabled --no-default-browser-check --password-store=basic --disable-infobars --show-component-extension-options --ignore-gpu-blacklist --disable-pings --media-router=0 --enable-remote-extensions <URL_REDACTED>', log '/tmp/Xapp00.out', env 'DISPLAY=:0.0 LANG=en_US.utf8 LANGUAGE=en_US HOME=/home/chromium XDG_RUNTIME_DIR=/run/user/777 GOOGLE_API_KEY=AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k GOOGLE_DEFAULT_CLIENT_ID=811574891467.apps.googleusercontent.com GOOGLE_DEFAULT_CLIENT_SECRET=kdloedMFGdGla2P1zacGjAQh CHROME_VERSION_EXTRA=WTware', pid '/tmp/Xapp00.pidpipe'.
[          pfac] [ 2743.361780] Run /usr/lib/chromium/chromium --window-size=1920,1080 --window-position=0,0 --disable-ipv6 --disable-gpu --wm-window-animations-disabled --no-default-browser-check --password-store=basic --disable-infobars --show-component-extension-options --ignore-gpu-blacklist --disable-pings --media-router=0 --enable-remote-extensions <URL_REDACTED>.
[          pfac] [ 2743.361916] Ok, PID 1700.
[X00] close kotopipe (n = 0, errno 0).
[          pfac] [ 2743.362086] Process pid 1700 terminated, status 00007f00.
[            gm] [ 2743.362116] Success, pid 1700.
[            gm] [ 2743.362419] Run '/usr/lib/chromium/chromium --window-size=1920,1080 --window-position=0,0 --disable-ipv6 --disable-gpu --wm-window-animations-disabled --no-default-browser-check --password-store=basic --disable-infobars --show-component-extension-options --ignore-gpu-blacklist --disable-pings --media-router=0 --enable-remote-extensions <URL_REDACTED>', log '/tmp/Xapp00.out', env 'DISPLAY=:0.0 LANG=en_US.utf8 LANGUAGE=en_US HOME=/home/chromium XDG_RUNTIME_DIR=/run/user/777 GOOGLE_API_KEY=AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k GOOGLE_DEFAULT_CLIENT_ID=811574891467.apps.googleusercontent.com GOOGLE_DEFAULT_CLIENT_SECRET=kdloedMFGdGla2P1zacGjAQh CHROME_VERSION_EXTRA=WTware', pid '/tmp/Xapp00.pidpipe'.
[          pfac] [ 2743.362455] Run /usr/lib/chromium/chromium --window-size=1920,1080 --window-position=0,0 --disable-ipv6 --disable-gpu --wm-window-animations-disabled --no-default-browser-check --password-store=basic --disable-infobars --show-component-extension-options --ignore-gpu-blacklist --disable-pings --media-router=0 --enable-remote-extensions <URL_REDACTED>.
[          pfac] [ 2743.362555] Ok, PID 1701.
[            gm] [ 2743.362630] Success, pid 1701.
[X00] close kotopipe (n = 0, errno 0).
[          pfac] [ 2743.362714] Process pid 1701 terminated, status 00007f00.
[            gm] [ 2743.362810] Run '/usr/lib/chromium/chromium --window-size=1920,1080 --window-position=0,0 --disable-ipv6 --disable-gpu --wm-window-animations-disabled --no-default-browser-check --password-store=basic --disable-infobars --show-component-extension-options --ignore-gpu-blacklist --disable-pings --media-router=0 --enable-remote-extensions <URL_REDACTED>', log '/tmp/Xapp00.out', env 'DISPLAY=:0.0 LANG=en_US.utf8 LANGUAGE=en_US HOME=/home/chromium XDG_RUNTIME_DIR=/run/user/777 GOOGLE_API_KEY=AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k GOOGLE_DEFAULT_CLIENT_ID=811574891467.apps.googleusercontent.com GOOGLE_DEFAULT_CLIENT_SECRET=kdloedMFGdGla2P1zacGjAQh CHROME_VERSION_EXTRA=WTware', pid '/tmp/Xapp00.pidpipe'.
[          pfac] [ 2743.362844] Run /usr/lib/chromium/chromium --window-size=1920,1080 --window-position=0,0 --disable-ipv6 --disable-gpu --wm-window-animations-disabled --no-default-browser-check --password-store=basic --disable-infobars --show-component-extension-options --ignore-gpu-blacklist --disable-pings --media-router=0 --enable-remote-extensions <URL_REDACTED>.
[          pfac] [ 2743.362930] Ok, PID 1702.
[            gm] [ 2743.363000] Success, pid 1702.
Here's my config:

Code: Select all

display=1920x1080, VGA
M2_display=1920x1080, HDMI
video=intel(U)
SIP=0000:0000@<HOST_REDACTED>, config:linphone.wtc
sound=on
timezone=Central Standard Time
domain=<REDACTED>
M2_position=right
chrome_mode=window
chrome_url=<URL_REDACTED>
loadbalanceinfo=tsv://VMResource.1.<REDACTED>
chrome_language=en
clienthostname=T8432
connection
application=tsclient
server=<REDACTED>
displayName=<REDACTED>
connection
application=chrome
displayName=Self Service Portal
I'm attempting to run this on a Lenovo M32

Any thoughts on why Chrome would be crashing? Thanks!
akatik
SUPPORT
SUPPORT
Posts: 562
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: Chrome Crashing on Startup

Post by akatik »

Here is the manual about logs: https://wtware.com/logs.html
No words "remove everything interesting and leave only few lines".
effin_dead_again
Posts: 20
Joined: Tue Dec 18, 2018 10:40 pm

Re: Chrome Crashing on Startup

Post by effin_dead_again »

You know if you're expecting me to spend money on your platform a slightly better attitude would go a long way...

Log is attached
Attachments
wtware-log.txt
(173.38 KiB) Downloaded 444 times
akatik
SUPPORT
SUPPORT
Posts: 562
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: Chrome Crashing on Startup

Post by akatik »

We have no Chrome for UEFI right now. In wtware distributive there are three different wtware for three different platforms: 32-bit x86 running from legacy BIOS, 64-bit x86 running from UEFI and arm raspberry pi. Chrome in 32-bit x86 and raspberry. Please wait a little, we expect Chrome for UEFI in the next wtware version, possibly in this year. Or try to switch boot in BIOS from UEFI to Legacy BIOS, Compatibility, CSM and so on if possible.
effin_dead_again
Posts: 20
Joined: Tue Dec 18, 2018 10:40 pm

Re: Chrome Crashing on Startup

Post by effin_dead_again »

I switched to legacy BIOS mode on the system and Chrome was able to launch. This issue should be considered resolved, I will await a UEFI compatible Chrome release.
Post Reply