Chrome can't connect to bus on RPI3 running -current

bob prohaska fbsd at www.zefox.net
Sat Dec 21 22:29:31 UTC 2019


Www/chromium finally compiled on a Pi3 running -current. 
The system is presently at (GENERIC) #5 r355919: Sat Dec 21 09:51:45 PST 2019

Chrome can be run (slowly!) across a network and seems to work, but
the controlling terminal is littered with

bob at www:~ % chrome
[1471:1333606144:1221/142239.390187:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[1471:1333606144:1221/142239.751450:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[1471:1333606144:1221/142239.753206:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[1505:1328579328:1221/142248.078482:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[1505:1208291328:1221/142251.443394:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response.
[1505:1208291328:1221/142251.445950:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response.

and that's just opening the home page 8-)

/etc/rc.conf contains
hald_enable="YES"
dbus_enable="YES"

Both hald and dbus are visible to pgrep:
bob at www:~ % pgrep dbus
1250
1254
1255
955
bob at www:~ % pgrep hald
1127
1131
1100
1101
1103

Are there some other services that need to be turned on?

Thanks for reading,

bob prohaska



More information about the freebsd-ports mailing list