su -c /usr/bin/google-chrome-stable guest

Technical issues/questions of an intermediate or advanced nature.
Post Reply
User avatar
francois
Contributor
Contributor
Posts: 5643
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

su -c /usr/bin/google-chrome-stable guest

Post#1 by francois » 15 Apr 2019, 00:11

Code: Select all

su -c /usr/bin/google-chrome-stable guest
command will work at first instance or bootup of the browser, but not then. Here are the output messages. Maybe you will have a cue about the why it will not boot after first bootup.

Code: Select all

root@porteus:~# su -c /usr/bin/google-chrome-stable guest
[2720:2720:0414/195854.530809:ERROR:browser_dm_token_storage_linux.cc(93)] Error: /etc/machine-id contains 0 characters (32 were expected).
[2760:2760:0414/195855.766887:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
Gkr-Message: 19:58:56.035: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[2720:2783:0414/195856.420148:ERROR:bus.cc(396)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(google-chrome-stable:2720): LIBDBUSMENU-GLIB-WARNING **: 19:58:57.144: Unable to get session bus: The connection is closed
[2720:2720:0414/195857.149854:ERROR:gpu_process_transport_factory.cc(967)] Lost UI shared context.
[2720:2720:0414/195857.634360:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const base::string16 &, const gfx::Range &)
Gkr-Message: 19:59:29.025: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[2720:2720:0414/195930.226756:ERROR:CONSOLE(1)] "Uncaught ReferenceError: inline is not defined", source: chrome://sync-confirmation/ (1)
[2720:3581:0414/195940.325575:ERROR:process_updates_util.cc(116)] Zero length name in non-deleted update
[2720:2720:0414/200022.291285:ERROR:CONSOLE(6)] "Uncaught ReferenceError: gbar is not defined", source: https://clients5.google.com/pagead/drt/dn/ (6)
[2720:2720:0414/200024.928499:ERROR:CONSOLE(6)] "Uncaught ReferenceError: gbar is not defined", source: https://clients5.google.com/pagead/drt/dn/ (6)
[2720:2720:0414/200026.445694:ERROR:CONSOLE(6)] "Uncaught ReferenceError: gbar is not defined", source: https://clients5.google.com/pagead/drt/dn/ (6)
[4697:4697:0414/200035.600050:ERROR:ppapi_thread.cc(326)] Failed to load Pepper module from internal-not-yet-present (error: internal-not-yet-present: cannot open shared object file: No such file or directory)
[2720:2720:0414/200043.970309:ERROR:http_bridge.cc(126)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived()
root@porteus:~# su -c /usr/bin/google-chrome-stable guest
[4758:4758:0414/200050.849091:ERROR:browser_dm_token_storage_linux.cc(93)] Error: /etc/machine-id contains 0 characters (32 were expected).
[4795:4795:0414/200051.074184:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.
Killed
root@porteus:~# 
Thanks.
Prendre son temps, profiter de celui qui passe.

jssouza
DEV Team
DEV Team
Posts: 918
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

su -c /usr/bin/google-chrome-stable guest

Post#2 by jssouza » 15 Apr 2019, 01:50

Try

Code: Select all

su -c "dbus-launch --exit-with-session /usr/bin/google-chrome-stable guest"
No guarantees.

User avatar
francois
Contributor
Contributor
Posts: 5643
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

su -c /usr/bin/google-chrome-stable guest

Post#3 by francois » 15 Apr 2019, 13:45

Glad you came out to the rescue! :)

Code: Select all

root@porteus:~# su -c "dbus-launch --exit-with-session /usr/bin/google-chrome-stable guest"
[4684:4684:0415/094348.781390:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
root@porteus:~# 
Did not work. Thanks nonetheless.
Prendre son temps, profiter de celui qui passe.

jssouza
DEV Team
DEV Team
Posts: 918
Joined: 09 Jul 2015, 14:17
Distribution: Porteus x86 arm
Location: Liechtenstein

su -c /usr/bin/google-chrome-stable guest

Post#4 by jssouza » 15 Apr 2019, 14:23

Why not also try with what it complains about? Or do you want the sandboxing?

Code: Select all

su -c "dbus-launch --exit-with-session /usr/bin/google-chrome-stable --no-sandbox guest"

User avatar
francois
Contributor
Contributor
Posts: 5643
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

su -c /usr/bin/google-chrome-stable guest

Post#5 by francois » 16 Apr 2019, 08:09

Without sandbox is not an issue, unless it is one. What does it do to your knowledge? I never got a satisfactory answer about the role of the sandbox.

For the record, I use:

Code: Select all

root@porteus:~# /usr/bin/google-chrome-stable --no-sandbox
Prendre son temps, profiter de celui qui passe.

User avatar
francois
Contributor
Contributor
Posts: 5643
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

su -c /usr/bin/google-chrome-stable guest

Post#6 by francois » 21 Apr 2019, 12:07

Everybody will be happy. I am dropping root mode. :hammer:
Prendre son temps, profiter de celui qui passe.

Post Reply