On Sun, Mar 17, 2019 at 02:09:08PM -0700, Ryan Freeman wrote:
> On Fri, Mar 15, 2019 at 07:52:50PM +0000, Bryan Everly wrote:
> > Hi Ports@,
> > 
> > Below is the terminal output I get when I try to launch the chromium build 
> > (latest & greatest package from snapshots) on the latest snapshot:
> > 
> > $ chrome
> > [40668:1870462320:0315/155107.446613:ERROR:process_metrics_openbsd.cc(126)] 
> > Not implemented reached in bool 
> > base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *)
> > [40668:1870462320:0315/155107.464615:ERROR:process_posix.cc(388)] Not 
> > implemented reached in base::Time base::Process::CreationTime() const
> > Abort trap (core dumped)
> > 
> > Any suggestions?
> > 
> > Thanks!
> 
> I still haven't been able to figure out what is causing this, my post here:
> https://marc.info/?l=openbsd-ports&m=155181090804746&w=2
> 
> Since iridium had unveil/pledge patches synced with chromium a few days ago,
> I can no-longer fall back on iridium either as it now crashes similarily:

One more datapoint: if i just disable gdm and enable xenodm, and start with
a .xsession that launches cwm, chrome does indeed launch:

ryan@insomniac ~ $ chrome
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: Version 4 or later of flush extension not found
libGL error: failed to load driver: i915
libGL error: failed to open drm device: No such file or directory
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
[26631:-1666849928:0317/154723.888117:ERROR:process_metrics_openbsd.cc(126)] 
Not implemented reached in bool 
base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *)
[26631:-1666849928:0317/154723.889965:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:1816873024:0317/154724.138608:ERROR:bus.cc(396)] Failed to connect to 
the bus: Could not parse server address: Unknown address type (examples of 
valid types are "tcp" and on UNIX "unix")
[26631:-1666849928:0317/154724.179239:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154724.181297:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154724.440994:ERROR:process_metrics_openbsd.cc(126)] 
Not implemented reached in bool 
base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *)
[26631:-1666849928:0317/154724.703262:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154724.714426:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154724.869231:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154724.909121:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154724.970124:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154727.648659:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.130078:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.135081:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.138799:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.141584:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.148690:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.152911:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.160600:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.162926:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.178123:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.181157:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const
[26631:-1666849928:0317/154730.183964:ERROR:process_posix.cc(388)] Not 
implemented reached in base::Time base::Process::CreationTime() const

>From here it seems to work just fine, and all tabs I previously had open
months ago reopen.


> 
> ryan@insomniac ~ 390 $ chrome
> [71406:523860800:0317/140337.483161:ERROR:process_metrics_openbsd.cc(126)] 
> Not implemented reached in bool 
> base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *)
> [71406:523860800:0317/140337.485690:ERROR:process_posix.cc(388)] Not 
> implemented reached in base::Time base::Process::CreationTime() const
> The process was killed by SIGABRT: Abort trap
> 
> ryan@insomniac ~ 390 $ iridium
> [77657:521386816:0317/140326.520304:ERROR:process_metrics_openbsd.cc(126)] 
> Not implemented reached in bool 
> base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *)
> *** autoupdate was enabled, overriding with false
> The process was killed by SIGABRT: Abort trap
> 
> My linked post has more data points, including running from a separate user
> does seem to work, but it doesn't get to talk to system dbus or use DRM stuff
> when run as test user.
> 
> I am starting to think this is tied to running chromium/iridium within gnome
> desktop, as most other folks I've talked to without this problem aren't 
> running
> gnome.
> 
> I've run pkg_check -f and used mtree to verify every file in the base system
> and make sure there aren't some weird symlink issues causing this as some
> have suggested in other channels.
> 
> Cheers,
> -Ryan
> 

Reply via email to