Running 'chromium' locks up machine

["John D. Baker" <jdbaker%consolidated.net@localhost>]

I finally got "www/chromium" built but upon running it for the first
time, its window didn't quite finish rendering and the system gradually
froze until only the (PS/2) mouse pointer could move but not affect any
visual elements.

The (also PS/2) keyboard was unresponsive so the only way to regain
control was a hard reset.

I suspect the issue is 'dbus'.  I seem to recall seeing some message
about that in the terminal window from which I ran 'chromium', but
couldn't read it entirely before 'chromium's window obscured the terminal.

ISTR that dbus-using applications usually try to launch it if they find
that it isn't currently running.  Do I need to ensure it's running before
starting 'chromium'?

Anyone else have problems running 'chromium'?

In case it matters, as mentioned in PR pkg/59164, I built my 'chromium'
after re-enabling "dbus" for _only_ "devel/at-spi2-core" and re-enabling
"gtk3-atk-bridge" for "x11/gtk3".  Was this sufficient, or should "dbus"
be re-enabled on other dependencies of "www/chromium"?

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645