From: Thomas Huth <1890545@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1890545] Re: (ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML
Date: Thu, 13 May 2021 12:15:19 -0000 [thread overview]
Message-ID: <162090811946.6710.4839854626025428661.malone@gac.canonical.com> (raw)
In-Reply-To: 159670025270.3099.13280483088179052036.malonedeb@gac.canonical.com
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/280
** Changed in: qemu
Status: New => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #280
https://gitlab.com/qemu-project/qemu/-/issues/280
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1890545
Title:
(ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and
can't load HTML
Status in QEMU:
Expired
Bug description:
First I creat a file system that is debian(bullseye amd64)on arm64
machine,then I download google-chrome,however, when I ran Google
browser, some errors occurred.
$ google-chrome --no-sandbox
or
$ qemu-x86_64-static google-chrome --no-sandbox
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[1661:1661:0806/074307.502638:ERROR:nacl_fork_delegate_linux.cc(323)] Bad NaCl helper startup ack (0 bytes)
[1664:1664:0806/074307.504159:ERROR:nacl_fork_delegate_linux.cc(323)] Bad NaCl helper startup ack (0 bytes)
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[1637:1678:0806/074308.337567:ERROR:file_path_watcher_linux.cc(315)] inotify_init() failed: Function not implemented (38)
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
qemu: unknown option 'type=utility'
[1637:1680:0806/074313.598432:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
Trace/breakpoint trap
Why?
And then I run firefox,it can be opened, but it can't load any web pages and HTML.
I really need help!
Thank.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1890545/+subscriptions
prev parent reply other threads:[~2021-05-13 12:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 7:50 [Bug 1890545] [NEW] (ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML Tony.LI
2020-08-10 6:24 ` [Bug 1890545] " Tony.LI
2020-08-10 10:02 ` Tony.LI
2020-08-10 10:12 ` Peter Maydell
2020-08-10 10:24 ` Tony.LI
2020-08-10 10:36 ` Tony.LI
2020-08-10 11:06 ` Alex Bennée
2020-08-10 11:06 ` Alex Bennée
2020-08-11 1:17 ` Tony.LI
2020-08-11 8:41 ` Alex Bennée
2020-08-11 8:41 ` Alex Bennée
2020-08-11 8:58 ` Tony.LI
2020-08-11 10:00 ` Tony.LI
2020-08-11 10:04 ` Tony.LI
2020-08-11 11:13 ` Peter Maydell
2020-08-12 9:56 ` Tony.LI
2020-08-13 7:41 ` Tony.LI
2020-08-14 10:06 ` Tony.LI
2020-08-16 11:23 ` Laurent Vivier
2020-08-17 8:40 ` Tony.LI
2020-08-18 7:46 ` Tony.LI
2020-08-18 7:50 ` Tony.LI
2020-08-19 1:24 ` Tony.LI
2020-08-19 2:15 ` Tony.LI
2021-04-27 7:27 ` Wind Li
2021-05-13 12:15 ` Thomas Huth [this message]
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=162090811946.6710.4839854626025428661.malone@gac.canonical.com \
--to=1890545@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.