Greg Steuck <[email protected]> wrote: > The problem seems to be due to Chromium doing a readlink (likely at > [1]) on /etc/localtime, which fails.
If that is what it is doing, then it should stop doing so.
Greg Steuck <[email protected]> wrote: > The problem seems to be due to Chromium doing a readlink (likely at > [1]) on /etc/localtime, which fails.
If that is what it is doing, then it should stop doing so.