“Low graphics mode” + “system error detected” have started to display on boot only sometimes - can't identify the cause

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








up vote
0
down vote

favorite












After a recent update (kernel?), I have begun to occasionally receive the message "Running in Low Graphics Mode" at boot (maybe half the time). I can tell it to use Default setting from the options it offers, and get by it, after which things look and work normally, even after some reboots.



I also usually get "System error detected, Report? at the same time, so I agree to report it.



Please note that I'm using 16.04 (fully updated), Gnome Flashback Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] .
This problem shows up no matter which of the above I'm using, or Unity.



roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


I've seen some suggestions like:




  • sudo apt-get update


  • sudo apt-get remove ubuntu-desktop


  • sudo apt-get install ubuntu-desktop


  • sudo shutdown -r now

but these are all quite old, at least 3 years, up to 6 or more years, and some of the simple items in some of these (boot while holding (shift), just don't work, so I'm afraid of them.



It's unclear to me if this would wipe out my GNOME and Cinnamon, etc. installations, or if that is separate and safe. Please advise.



There appears to be plenty of memory and storage available.



roger@roger-desktop:~$ free -m
total used free shared buff/cache available
Mem: 16013 3880 10410 363 1722 11443
Swap: 16348 0 16348

roger@roger-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 9.6M 1.6G 1% /run
/dev/sda1 902G 77G 779G 9% /
tmpfs 7.9G 127M 7.7G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 52K 1.6G 1% /run/user/1000


Also, if I simply go to 18.04 (I don't really want to just yet.) will it likely fix this or might this block or damage the upgrade?







share|improve this question


















  • 1




    Possible duplicate of How to fix "The system is running in low-graphics mode" error?
    – David Foerster
    Jul 23 at 16:25














up vote
0
down vote

favorite












After a recent update (kernel?), I have begun to occasionally receive the message "Running in Low Graphics Mode" at boot (maybe half the time). I can tell it to use Default setting from the options it offers, and get by it, after which things look and work normally, even after some reboots.



I also usually get "System error detected, Report? at the same time, so I agree to report it.



Please note that I'm using 16.04 (fully updated), Gnome Flashback Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] .
This problem shows up no matter which of the above I'm using, or Unity.



roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


I've seen some suggestions like:




  • sudo apt-get update


  • sudo apt-get remove ubuntu-desktop


  • sudo apt-get install ubuntu-desktop


  • sudo shutdown -r now

but these are all quite old, at least 3 years, up to 6 or more years, and some of the simple items in some of these (boot while holding (shift), just don't work, so I'm afraid of them.



It's unclear to me if this would wipe out my GNOME and Cinnamon, etc. installations, or if that is separate and safe. Please advise.



There appears to be plenty of memory and storage available.



roger@roger-desktop:~$ free -m
total used free shared buff/cache available
Mem: 16013 3880 10410 363 1722 11443
Swap: 16348 0 16348

roger@roger-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 9.6M 1.6G 1% /run
/dev/sda1 902G 77G 779G 9% /
tmpfs 7.9G 127M 7.7G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 52K 1.6G 1% /run/user/1000


Also, if I simply go to 18.04 (I don't really want to just yet.) will it likely fix this or might this block or damage the upgrade?







share|improve this question


















  • 1




    Possible duplicate of How to fix "The system is running in low-graphics mode" error?
    – David Foerster
    Jul 23 at 16:25












up vote
0
down vote

favorite









up vote
0
down vote

favorite











After a recent update (kernel?), I have begun to occasionally receive the message "Running in Low Graphics Mode" at boot (maybe half the time). I can tell it to use Default setting from the options it offers, and get by it, after which things look and work normally, even after some reboots.



I also usually get "System error detected, Report? at the same time, so I agree to report it.



Please note that I'm using 16.04 (fully updated), Gnome Flashback Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] .
This problem shows up no matter which of the above I'm using, or Unity.



roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


I've seen some suggestions like:




  • sudo apt-get update


  • sudo apt-get remove ubuntu-desktop


  • sudo apt-get install ubuntu-desktop


  • sudo shutdown -r now

but these are all quite old, at least 3 years, up to 6 or more years, and some of the simple items in some of these (boot while holding (shift), just don't work, so I'm afraid of them.



It's unclear to me if this would wipe out my GNOME and Cinnamon, etc. installations, or if that is separate and safe. Please advise.



There appears to be plenty of memory and storage available.



roger@roger-desktop:~$ free -m
total used free shared buff/cache available
Mem: 16013 3880 10410 363 1722 11443
Swap: 16348 0 16348

roger@roger-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 9.6M 1.6G 1% /run
/dev/sda1 902G 77G 779G 9% /
tmpfs 7.9G 127M 7.7G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 52K 1.6G 1% /run/user/1000


Also, if I simply go to 18.04 (I don't really want to just yet.) will it likely fix this or might this block or damage the upgrade?







share|improve this question














After a recent update (kernel?), I have begun to occasionally receive the message "Running in Low Graphics Mode" at boot (maybe half the time). I can tell it to use Default setting from the options it offers, and get by it, after which things look and work normally, even after some reboots.



I also usually get "System error detected, Report? at the same time, so I agree to report it.



Please note that I'm using 16.04 (fully updated), Gnome Flashback Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] .
This problem shows up no matter which of the above I'm using, or Unity.



roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


I've seen some suggestions like:




  • sudo apt-get update


  • sudo apt-get remove ubuntu-desktop


  • sudo apt-get install ubuntu-desktop


  • sudo shutdown -r now

but these are all quite old, at least 3 years, up to 6 or more years, and some of the simple items in some of these (boot while holding (shift), just don't work, so I'm afraid of them.



It's unclear to me if this would wipe out my GNOME and Cinnamon, etc. installations, or if that is separate and safe. Please advise.



There appears to be plenty of memory and storage available.



roger@roger-desktop:~$ free -m
total used free shared buff/cache available
Mem: 16013 3880 10410 363 1722 11443
Swap: 16348 0 16348

roger@roger-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 9.6M 1.6G 1% /run
/dev/sda1 902G 77G 779G 9% /
tmpfs 7.9G 127M 7.7G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 52K 1.6G 1% /run/user/1000


Also, if I simply go to 18.04 (I don't really want to just yet.) will it likely fix this or might this block or damage the upgrade?









share|improve this question













share|improve this question




share|improve this question








edited May 17 at 7:30









Zanna

47.9k13117227




47.9k13117227










asked May 16 at 23:30









Roger Davis

325




325







  • 1




    Possible duplicate of How to fix "The system is running in low-graphics mode" error?
    – David Foerster
    Jul 23 at 16:25












  • 1




    Possible duplicate of How to fix "The system is running in low-graphics mode" error?
    – David Foerster
    Jul 23 at 16:25







1




1




Possible duplicate of How to fix "The system is running in low-graphics mode" error?
– David Foerster
Jul 23 at 16:25




Possible duplicate of How to fix "The system is running in low-graphics mode" error?
– David Foerster
Jul 23 at 16:25










1 Answer
1






active

oldest

votes

















up vote
0
down vote













I too experience this problem, a lot of googling and the following seems to have fixed it - but as you say it is intermittent, so I cant be certain yet.



cd /etc/default/
sudo gedit grub


Comment the line



#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


and add line below turn off the splash screen and inspect boot log



GRUB_CMDLINE_LINUX_DEFAULT=""


then run



sudo update-grub


and restart.






share|improve this answer






















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    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: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2faskubuntu.com%2fquestions%2f1037169%2flow-graphics-mode-system-error-detected-have-started-to-display-on-boot-on%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













    I too experience this problem, a lot of googling and the following seems to have fixed it - but as you say it is intermittent, so I cant be certain yet.



    cd /etc/default/
    sudo gedit grub


    Comment the line



    #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


    and add line below turn off the splash screen and inspect boot log



    GRUB_CMDLINE_LINUX_DEFAULT=""


    then run



    sudo update-grub


    and restart.






    share|improve this answer


























      up vote
      0
      down vote













      I too experience this problem, a lot of googling and the following seems to have fixed it - but as you say it is intermittent, so I cant be certain yet.



      cd /etc/default/
      sudo gedit grub


      Comment the line



      #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


      and add line below turn off the splash screen and inspect boot log



      GRUB_CMDLINE_LINUX_DEFAULT=""


      then run



      sudo update-grub


      and restart.






      share|improve this answer
























        up vote
        0
        down vote










        up vote
        0
        down vote









        I too experience this problem, a lot of googling and the following seems to have fixed it - but as you say it is intermittent, so I cant be certain yet.



        cd /etc/default/
        sudo gedit grub


        Comment the line



        #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


        and add line below turn off the splash screen and inspect boot log



        GRUB_CMDLINE_LINUX_DEFAULT=""


        then run



        sudo update-grub


        and restart.






        share|improve this answer














        I too experience this problem, a lot of googling and the following seems to have fixed it - but as you say it is intermittent, so I cant be certain yet.



        cd /etc/default/
        sudo gedit grub


        Comment the line



        #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"


        and add line below turn off the splash screen and inspect boot log



        GRUB_CMDLINE_LINUX_DEFAULT=""


        then run



        sudo update-grub


        and restart.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jul 23 at 21:26









        Stephen Rauch

        1,1546716




        1,1546716










        answered Jul 23 at 15:43









        Rex Sutton

        1




        1






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037169%2flow-graphics-mode-system-error-detected-have-started-to-display-on-boot-on%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491