Question Can't start UnityHub - Ubuntu 20.04

Hi all!
I've just had a fresh install of Ubuntu 20.04 and tried installing Unity Hub through apt. There were no particular problem during the install, but when I try to start it, I get a blank window. When starting from a terminal, I have the following error message :

[I][71210:0225/105720.409826:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=5

[71210:0225/105720.629017:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=5

[71210:0225/105720.812470:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=5

[71210:0225/105720.928222:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=5

[71210:0225/105721.029237:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=5

[71210:0225/105721.134052:ERROR:gpu_process_host.cc(974)] GPU process exited unexpectedly: exit_code=5

[71315:0225/105721.151950:ERROR:gpu_init.cc(481)] Passthrough is not supported, GL is disabled, ANGLE is

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Error: The name org.freedesktop.secrets was not provided by any .service files

(Use `unityhub-bin --trace-warnings ...` to show where the warning was created)

(node:71210) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Error: The name org.freedesktop.secrets was not provided by any .service files

(node:71210) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)

APPIMAGE env is not defined, current application is not an AppImage

[71210:0225/105722.364710:ERROR:browser_main_loop.cc(271)] Gdk: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed[/I]

I've looked around and I really don't know how to solve this problem.

As an aside, I'd tested the same install on the same laptop that was then under 18.04 and I didn't have a problem then.

 

Small update : I've realised that the Unity Hub appears to be working overall (the tray widget racts normaly). It's just that the main window remains blank whatever I do.
Still no idea how to solve that...

 

So, 3.4.0 has the same problem while 3.3.0 works.
What has changed that created this bug, and how to correct it (or should I file a bug ? But that problem doesn't seem to be widespread, so it feels more like a conflict with whatever on my computer).