Comment # 2 on bug 1160068 from David Herman

Confirming workaround, disconnecting chromecast allows chromium to start
correctly on my Tumbleweed workstations.

Issue was not affecting google-chrome browser, vivaldi (based on chromium) or
chromium running on other distributions, but affected all versions of chromium
available in the tumbleweed repositories (official and community) on my
machines.

question Michael and Bryan, how did you recognize the chromecast connection to
this issue?