Google Chrome GPU Driver Issues on Ubuntu 18.04












0














I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.



I tried google-chrome from the command line, and it gave me the following;



theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!


Some important things to note:




  1. There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.

  2. There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.

  3. This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.


EDIT:



Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:



[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.









share|improve this question
























  • Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
    – user88036
    Oct 4 at 0:38










  • @Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
    – Theodore Weld
    Oct 4 at 0:44






  • 1




    Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
    – Theodore Weld
    Oct 4 at 0:55










  • @Goro I did check this—doesn’t seem to be there.
    – Theodore Weld
    Oct 4 at 0:59










  • There are many different releases of libgles2-mesa for Ubuntu 18.04 try the closest to your system.
    – user88036
    Oct 4 at 1:02
















0














I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.



I tried google-chrome from the command line, and it gave me the following;



theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!


Some important things to note:




  1. There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.

  2. There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.

  3. This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.


EDIT:



Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:



[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.









share|improve this question
























  • Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
    – user88036
    Oct 4 at 0:38










  • @Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
    – Theodore Weld
    Oct 4 at 0:44






  • 1




    Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
    – Theodore Weld
    Oct 4 at 0:55










  • @Goro I did check this—doesn’t seem to be there.
    – Theodore Weld
    Oct 4 at 0:59










  • There are many different releases of libgles2-mesa for Ubuntu 18.04 try the closest to your system.
    – user88036
    Oct 4 at 1:02














0












0








0







I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.



I tried google-chrome from the command line, and it gave me the following;



theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!


Some important things to note:




  1. There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.

  2. There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.

  3. This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.


EDIT:



Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:



[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.









share|improve this question















I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.



I tried google-chrome from the command line, and it gave me the following;



theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!


Some important things to note:




  1. There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.

  2. There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.

  3. This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.


EDIT:



Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:



[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.






ubuntu drivers chrome gpu






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 4 at 0:56

























asked Oct 4 at 0:20









Theodore Weld

1135




1135












  • Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
    – user88036
    Oct 4 at 0:38










  • @Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
    – Theodore Weld
    Oct 4 at 0:44






  • 1




    Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
    – Theodore Weld
    Oct 4 at 0:55










  • @Goro I did check this—doesn’t seem to be there.
    – Theodore Weld
    Oct 4 at 0:59










  • There are many different releases of libgles2-mesa for Ubuntu 18.04 try the closest to your system.
    – user88036
    Oct 4 at 1:02


















  • Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
    – user88036
    Oct 4 at 0:38










  • @Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
    – Theodore Weld
    Oct 4 at 0:44






  • 1




    Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
    – Theodore Weld
    Oct 4 at 0:55










  • @Goro I did check this—doesn’t seem to be there.
    – Theodore Weld
    Oct 4 at 0:59










  • There are many different releases of libgles2-mesa for Ubuntu 18.04 try the closest to your system.
    – user88036
    Oct 4 at 1:02
















Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– user88036
Oct 4 at 0:38




Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– user88036
Oct 4 at 0:38












@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44




@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44




1




1




Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55




Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55












@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59




@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59












There are many different releases of libgles2-mesa for Ubuntu 18.04 try the closest to your system.
– user88036
Oct 4 at 1:02




There are many different releases of libgles2-mesa for Ubuntu 18.04 try the closest to your system.
– user88036
Oct 4 at 1:02










2 Answers
2






active

oldest

votes


















2














I would suggest that you do the following:



1) Check whether you have "libgles2-mesa" installed? If not, then install it.



2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:



google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests 





share|improve this answer





























    0














    Install NVidia drivers:



    1) ubuntu-drivers devices



    2) sudo apt install nvidia-driver-(your device)
    -or-
    sudo ubuntu-drivers autoinstall



    3) reboot






    share|improve this answer








    New contributor




    guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.


















    • Is ubuntu-drivers devices a command to be typed?   Please do not respond in comments; edit your answer to make it clearer and more complete.
      – G-Man
      yesterday











    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    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%2f473115%2fgoogle-chrome-gpu-driver-issues-on-ubuntu-18-04%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    I would suggest that you do the following:



    1) Check whether you have "libgles2-mesa" installed? If not, then install it.



    2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:



    google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests 





    share|improve this answer


























      2














      I would suggest that you do the following:



      1) Check whether you have "libgles2-mesa" installed? If not, then install it.



      2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:



      google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests 





      share|improve this answer
























        2












        2








        2






        I would suggest that you do the following:



        1) Check whether you have "libgles2-mesa" installed? If not, then install it.



        2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:



        google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests 





        share|improve this answer












        I would suggest that you do the following:



        1) Check whether you have "libgles2-mesa" installed? If not, then install it.



        2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:



        google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests 






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 4 at 0:48







        user88036
































            0














            Install NVidia drivers:



            1) ubuntu-drivers devices



            2) sudo apt install nvidia-driver-(your device)
            -or-
            sudo ubuntu-drivers autoinstall



            3) reboot






            share|improve this answer








            New contributor




            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.


















            • Is ubuntu-drivers devices a command to be typed?   Please do not respond in comments; edit your answer to make it clearer and more complete.
              – G-Man
              yesterday
















            0














            Install NVidia drivers:



            1) ubuntu-drivers devices



            2) sudo apt install nvidia-driver-(your device)
            -or-
            sudo ubuntu-drivers autoinstall



            3) reboot






            share|improve this answer








            New contributor




            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.


















            • Is ubuntu-drivers devices a command to be typed?   Please do not respond in comments; edit your answer to make it clearer and more complete.
              – G-Man
              yesterday














            0












            0








            0






            Install NVidia drivers:



            1) ubuntu-drivers devices



            2) sudo apt install nvidia-driver-(your device)
            -or-
            sudo ubuntu-drivers autoinstall



            3) reboot






            share|improve this answer








            New contributor




            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            Install NVidia drivers:



            1) ubuntu-drivers devices



            2) sudo apt install nvidia-driver-(your device)
            -or-
            sudo ubuntu-drivers autoinstall



            3) reboot







            share|improve this answer








            New contributor




            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            share|improve this answer



            share|improve this answer






            New contributor




            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.









            answered yesterday









            guest

            1




            1




            New contributor




            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.





            New contributor





            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.






            guest is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.












            • Is ubuntu-drivers devices a command to be typed?   Please do not respond in comments; edit your answer to make it clearer and more complete.
              – G-Man
              yesterday


















            • Is ubuntu-drivers devices a command to be typed?   Please do not respond in comments; edit your answer to make it clearer and more complete.
              – G-Man
              yesterday
















            Is ubuntu-drivers devices a command to be typed?   Please do not respond in comments; edit your answer to make it clearer and more complete.
            – G-Man
            yesterday




            Is ubuntu-drivers devices a command to be typed?   Please do not respond in comments; edit your answer to make it clearer and more complete.
            – G-Man
            yesterday


















            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473115%2fgoogle-chrome-gpu-driver-issues-on-ubuntu-18-04%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Accessing regular linux commands in Huawei's Dopra Linux

            Can't connect RFCOMM socket: Host is down

            Kernel panic - not syncing: Fatal Exception in Interrupt