The workaround in bug 18752 fixes the blank screen. (This is also my bug report)
export QT_X11_NO_MITSHM=1
export _X11_NO_MITSHM=1
export _MITSHM=0
This work until 81.0.4044.122 which causes a crash (chromium exit) with
FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye
The --no-sandbox is a work around loosing process isolation. Which disabling the sandbox is not recommended,
The --use-gl=swiftshader was a work around for the blank screen not the crash and --use-gl option does nothing in 81.0.4044.138.
Summary so far:
This is not same bug as 18752 but a new problem on a new version of chromium (Have not removed 18752 work around)
There exists a work around --no-sandbox but is not recommended to use.
Sorry about last comment. (ignore last comment)
The workaround in bug 18752 fixes the blank screen. (This is also my bug report)
export QT_X11_NO_MITSHM=1
export _X11_NO_MITSHM=1
export _MITSHM=0
This work until 81.0.4044.122 which causes a crash (chromium exit) with data_manager_ impl_private. cc(439) ] GPU process isn't usable. Goodbye
FATAL:gpu_
The --no-sandbox is a work around loosing process isolation. Which disabling the sandbox is not recommended,
The --use-gl= swiftshader was a work around for the blank screen not the crash and --use-gl option does nothing in 81.0.4044.138.
Summary so far:
This is not same bug as 18752 but a new problem on a new version of chromium (Have not removed 18752 work around)
There exists a work around --no-sandbox but is not recommended to use.