The -current chromium (updated yesterday) produces the error as:
ci5hp2$
[95250:-478283696:0227/100638.919493:ERROR:process_metrics_openbsd.cc(126)]
Not implemented reached in bool
base::GetSystemMemoryInfo(base::SystemMemoryInfoKB *)
[95250:-478283696:0227/100638.921060:ERROR:process_posix.cc(388)] Not
implemented reached in base::Time base::Process::CreationTime() const
Gkr-Message: 10:06:42.180: secret service operation failed: The name
org.freedesktop.secrets was not provided by any .service files

After this error, if I remove all the files under .config/chromium, I can
restart chromium.

I don't know it also related or not, Gnucash also has problem where she
cannnot remember the previous status
of windows size, position, what iterms are opened etc.

Kenji



2019年2月26日(火) 6:43 Stuart Henderson <s...@spacehopper.org>:

> On 2019/02/25 14:28, Theo de Raadt wrote:
> > >There is another issue here. I'm not sure if it is because me or all
> > >are experiencing it.
> > >
> > >Each run after install, chromium is not able to cd into the designed
> > >~/Downloads/
> > >It looks like I am thrown into ~ and I can't move from there because
> > >of that error message.
> > >A good setup for this is run chrome --disable-unveil and set up the
> > >download directory, then run it normally with unveil and be able to
> > >use it.
> > >
> > >Also a big confusion with iridium is when the downloaded files are not
> > >accessible / are deleted / are not shown because of some potential
> > >danger to your computer. Seriously, Internet Explorer style? Didn't
> > >bother to investigate this, I don't run iridium anymore. It looks to
> > >me like chromium with some check marks disabled in settings.
> >
> > please try a very recent set of packages.  robert has been working
> > on resolving that mess.
> >
>
> Current status for chromium 72.0.3626.109p0 or newer: you can get to
> ~/Downloads via buttons (as long as it's a directory not a symlink),
> and you can get to /tmp if you type in the path.
>
> This isn't ported to iridium yet.
>
>

Reply via email to