Re: Flood of non-fatal www/chromium errors
- Reply: Tatsuki Makino : "Re: Flood of non-fatal www/chromium errors"
- In reply to: Tatsuki Makino : "Re: Flood of non-fatal www/chromium errors"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 13 Apr 2023 06:08:30 UTC
On Thu, Apr 13, 2023 at 6:22 AM Tatsuki Makino <tatsuki_makino@hotmail.com> wrote: > > bob prohaska wrote on 2023/04/13 11:18: > > Running www/chromium (from ports via poudriere) on a Pi4 > > reports a stream of > > [30033:1100602368:0412/190147.848068:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") > > messages. > > > > That is because there is a setenv("DBUS_SESSION_BUS_ADDRESS","disabled:" somewhere :) Most likely, this is https://bugs.chromium.org/p/chromium/issues/detail?id=918234 > The workaround is DBUS_SESSION_BUS_ADDRESS below. DBUS_SESSION_BUS_ADDRESS="auto Yep, this is the same as what I did in https://github.com/freebsd/freebsd-ports/blob/main/textproc/obsidian/files/obsidian.in launch:" ; export DBUS_SESSION_BUS_ADDRESS