How do I properly add Chromium to my Yocto linux distribution

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












Built Yocto (Poky fido branch) linux distro for Raspberry Pi 2 following this excellent tutorial Part 1.



Now trying to run Chromium.



Added meta-browser to my bblayers.conf



Added chromium recipes to my .bb image file.



Was able to compile and build my image but getting these errors when trying to run:



root@raspberrypi2:/usr/bin/chromium# ./chrome
[527:527:0624/195537:FATAL:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
Aborted


--no-sandbox



root@raspberrypi2:/usr/bin/chromium# ./chrome --no-sandbox
[528:528:0624/195641:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[528:528:0624/195641:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display:
root@raspberrypi2:/usr/bin/chromium# [530:530:0624/195641:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
[530:530:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
^C


DISPLAY=:0.0



root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox
[531:531:0624/195652:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[531:531:0624/195652:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
root@raspberrypi2:/usr/bin/chromium# [533:533:0624/195652:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
[533:533:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
^C


--use-gl=egl




I'd be very interested to have it working with hardware acceleration




root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox --use-gl=egl 
[534:534:0624/195901:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
[534:534:0624/195901:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
root@raspberrypi2:/usr/bin/chromium# [536:536:0624/195901:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
[536:536:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
^C


Any pointers are welcome.










share|improve this question



























    up vote
    1
    down vote

    favorite












    Built Yocto (Poky fido branch) linux distro for Raspberry Pi 2 following this excellent tutorial Part 1.



    Now trying to run Chromium.



    Added meta-browser to my bblayers.conf



    Added chromium recipes to my .bb image file.



    Was able to compile and build my image but getting these errors when trying to run:



    root@raspberrypi2:/usr/bin/chromium# ./chrome
    [527:527:0624/195537:FATAL:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
    Aborted


    --no-sandbox



    root@raspberrypi2:/usr/bin/chromium# ./chrome --no-sandbox
    [528:528:0624/195641:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
    [528:528:0624/195641:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display:
    root@raspberrypi2:/usr/bin/chromium# [530:530:0624/195641:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
    [530:530:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
    ^C


    DISPLAY=:0.0



    root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox
    [531:531:0624/195652:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
    [531:531:0624/195652:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
    root@raspberrypi2:/usr/bin/chromium# [533:533:0624/195652:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
    [533:533:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
    ^C


    --use-gl=egl




    I'd be very interested to have it working with hardware acceleration




    root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox --use-gl=egl 
    [534:534:0624/195901:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
    [534:534:0624/195901:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
    root@raspberrypi2:/usr/bin/chromium# [536:536:0624/195901:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
    [536:536:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
    ^C


    Any pointers are welcome.










    share|improve this question

























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      Built Yocto (Poky fido branch) linux distro for Raspberry Pi 2 following this excellent tutorial Part 1.



      Now trying to run Chromium.



      Added meta-browser to my bblayers.conf



      Added chromium recipes to my .bb image file.



      Was able to compile and build my image but getting these errors when trying to run:



      root@raspberrypi2:/usr/bin/chromium# ./chrome
      [527:527:0624/195537:FATAL:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      Aborted


      --no-sandbox



      root@raspberrypi2:/usr/bin/chromium# ./chrome --no-sandbox
      [528:528:0624/195641:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      [528:528:0624/195641:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display:
      root@raspberrypi2:/usr/bin/chromium# [530:530:0624/195641:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
      [530:530:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
      ^C


      DISPLAY=:0.0



      root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox
      [531:531:0624/195652:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      [531:531:0624/195652:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
      root@raspberrypi2:/usr/bin/chromium# [533:533:0624/195652:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
      [533:533:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
      ^C


      --use-gl=egl




      I'd be very interested to have it working with hardware acceleration




      root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox --use-gl=egl 
      [534:534:0624/195901:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      [534:534:0624/195901:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
      root@raspberrypi2:/usr/bin/chromium# [536:536:0624/195901:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
      [536:536:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
      ^C


      Any pointers are welcome.










      share|improve this question















      Built Yocto (Poky fido branch) linux distro for Raspberry Pi 2 following this excellent tutorial Part 1.



      Now trying to run Chromium.



      Added meta-browser to my bblayers.conf



      Added chromium recipes to my .bb image file.



      Was able to compile and build my image but getting these errors when trying to run:



      root@raspberrypi2:/usr/bin/chromium# ./chrome
      [527:527:0624/195537:FATAL:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      Aborted


      --no-sandbox



      root@raspberrypi2:/usr/bin/chromium# ./chrome --no-sandbox
      [528:528:0624/195641:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      [528:528:0624/195641:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display:
      root@raspberrypi2:/usr/bin/chromium# [530:530:0624/195641:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
      [530:530:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
      ^C


      DISPLAY=:0.0



      root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox
      [531:531:0624/195652:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      [531:531:0624/195652:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
      root@raspberrypi2:/usr/bin/chromium# [533:533:0624/195652:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
      [533:533:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
      ^C


      --use-gl=egl




      I'd be very interested to have it working with hardware acceleration




      root@raspberrypi2:/usr/bin/chromium# export DISPLAY=:0.0 && ./chrome --no-sandbox --use-gl=egl 
      [534:534:0624/195901:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
      [534:534:0624/195901:ERROR:browser_main_loop.cc(210)] Gtk: cannot open display: :0.0
      root@raspberrypi2:/usr/bin/chromium# [536:536:0624/195901:ERROR:image_metadata_extractor.cc(111)] Couldn't load libexif.
      [536:536:0100/000000:ERROR:zygote_linux.cc(587)] write: Broken pipe
      ^C


      Any pointers are welcome.







      raspberry-pi chrome arm yocto






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 24 '15 at 22:31

























      asked Jun 24 '15 at 22:00









      zabumba

      21261744




      21261744




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          Perhaps this helps....from my "ps" slightly different platform.



           /bin/sh /usr/bin/google-chrome 


          2009 root 2424 S google-chrome /bin/sh /usr/bin/google-chrome
          2010 root 378m S /usr/bin/chrome/chrome --use-gl=egl --user-data-dir=/home/root/.chromium/
          2012 root 1956 S /usr/sbin/chrome-devel-sandbox /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/
          2013 root 100m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
          2016 root 108m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
          2069 root 212m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan
          2078 root 175m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan


          This was launched from a desktop icon "/bin/sh /usr/bin/google-chrome" which in turn set all the variables seen in the following threads.






          share|improve this answer






















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f211963%2fhow-do-i-properly-add-chromium-to-my-yocto-linux-distribution%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            Perhaps this helps....from my "ps" slightly different platform.



             /bin/sh /usr/bin/google-chrome 


            2009 root 2424 S google-chrome /bin/sh /usr/bin/google-chrome
            2010 root 378m S /usr/bin/chrome/chrome --use-gl=egl --user-data-dir=/home/root/.chromium/
            2012 root 1956 S /usr/sbin/chrome-devel-sandbox /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/
            2013 root 100m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
            2016 root 108m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
            2069 root 212m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan
            2078 root 175m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan


            This was launched from a desktop icon "/bin/sh /usr/bin/google-chrome" which in turn set all the variables seen in the following threads.






            share|improve this answer


























              up vote
              0
              down vote













              Perhaps this helps....from my "ps" slightly different platform.



               /bin/sh /usr/bin/google-chrome 


              2009 root 2424 S google-chrome /bin/sh /usr/bin/google-chrome
              2010 root 378m S /usr/bin/chrome/chrome --use-gl=egl --user-data-dir=/home/root/.chromium/
              2012 root 1956 S /usr/sbin/chrome-devel-sandbox /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/
              2013 root 100m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
              2016 root 108m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
              2069 root 212m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan
              2078 root 175m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan


              This was launched from a desktop icon "/bin/sh /usr/bin/google-chrome" which in turn set all the variables seen in the following threads.






              share|improve this answer
























                up vote
                0
                down vote










                up vote
                0
                down vote









                Perhaps this helps....from my "ps" slightly different platform.



                 /bin/sh /usr/bin/google-chrome 


                2009 root 2424 S google-chrome /bin/sh /usr/bin/google-chrome
                2010 root 378m S /usr/bin/chrome/chrome --use-gl=egl --user-data-dir=/home/root/.chromium/
                2012 root 1956 S /usr/sbin/chrome-devel-sandbox /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/
                2013 root 100m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
                2016 root 108m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
                2069 root 212m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan
                2078 root 175m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan


                This was launched from a desktop icon "/bin/sh /usr/bin/google-chrome" which in turn set all the variables seen in the following threads.






                share|improve this answer














                Perhaps this helps....from my "ps" slightly different platform.



                 /bin/sh /usr/bin/google-chrome 


                2009 root 2424 S google-chrome /bin/sh /usr/bin/google-chrome
                2010 root 378m S /usr/bin/chrome/chrome --use-gl=egl --user-data-dir=/home/root/.chromium/
                2012 root 1956 S /usr/sbin/chrome-devel-sandbox /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/
                2013 root 100m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
                2016 root 108m S /usr/bin/chrome/chrome --type=zygote --user-data-dir=/home/root/.chromium/
                2069 root 212m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan
                2078 root 175m S /usr/bin/chrome/chrome --type=renderer --use-gl=egl --enable-deferred-image-decoding --lan


                This was launched from a desktop icon "/bin/sh /usr/bin/google-chrome" which in turn set all the variables seen in the following threads.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Aug 25 '15 at 15:28

























                answered Aug 25 '15 at 15:20









                wwright

                1111




                1111



























                     

                    draft saved


                    draft discarded















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f211963%2fhow-do-i-properly-add-chromium-to-my-yocto-linux-distribution%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Displaying single band from multi-band raster using QGIS

                    How many registers does an x86_64 CPU actually have?