Github messages for voidlinux
 help / color / mirror / Atom feed
From: rilysh <rilysh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Google Chrome isn't responding correctly.
Date: Sat, 06 May 2023 19:29:11 +0200	[thread overview]
Message-ID: <20230506172911.ftT6AjpbMWM8Y0kbGdrxd7ZqkB8ZTfSLS6nJ5Or6bIE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43755@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

New comment by rilysh on void-packages repository

https://github.com/void-linux/void-packages/issues/43755#issuecomment-1537187200

Comment:
> The error message is below: [11352:11352:0505/165733.707250:ERROR:browser_dm_token_storage_linux.cc(100)] Error: /etc/machine-id contains 0 characters (32 were expected). INFO: Created TensorFlow Lite XNNPACK delegate for CPU.

This usually means that chrome couldn't be able to find your `machine-id` which should be generated on installation. Either it's there but contains nothing or it was generated but somehow it's snot under non-root user privilege.

I just tested this out and for me, chrome just only shows an warning message regarding this but everything seems working just fine.

Can you provide some more relevant information, like if chrome crashes or something?

  parent reply	other threads:[~2023-05-06 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05  1:57 [ISSUE] " Programuserbash
2023-05-05  9:54 ` biopsin
2023-05-05 16:31 ` Programuserbash
2023-05-05 17:38 ` biopsin
2023-05-05 21:55 ` Programuserbash
2023-05-06 17:29 ` rilysh [this message]
2023-05-06 17:30 ` rilysh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230506172911.ftT6AjpbMWM8Y0kbGdrxd7ZqkB8ZTfSLS6nJ5Or6bIE@z \
    --to=rilysh@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).