Scientific Linux Gnome desktop not loading












0















About half a month ago, I installed Scientific Linux 7.6 on a computer that has shut down and restarted daily as expected until today. Details of the operating system are below.




  1. Full version number: (3.10.0-957.1.3.el7.x86_64) 7.6 (Nitrogen)

  2. Desktop: Gnome


Today when I turn back on the computer, the gnome desktop won't load. The boot up proceeds as expected until the grey-blue screen showing a spinning wheel (the one with radial lines). Then about when the wheel is supposed to pick up speed and take you to the login page with usernames to select from, it breaks into the terminal mode text with status messages. They all show [ OK ] in green except for these lines repeated once:



[ INFO ] dev-virtiox2dports-com.redhat.spice.0.device is not active.
[DEPEND] Dependency failed for Activation socket for spice guest agent daemon
.....


Also the last line (before the display manager load hangs) reads thus:



  OK  ] Started Crash recovery kernel arming.. to Quit.........ice.emon.549..progress polling....


As you can see the messages there are garbled and the [ OK ] label is missing the leading bracket too.



It looks horrid so far, but I am able to navigate to a login screen and appropriate a terminal with (Alt,F2) through (Alt, F6), and then log in as one of the users or as root, likewise.



So I am hoping that more than the window manager is not malfunctioning. When I check on the status of gdm.service, I find that it shows as 'active (running)' but there are also these messages.



<Datetime> <hostname> systemd[1]: Starting GNOME Display Manager...
<Datetime> <hostname> systemd[1]: Started GNOME Display Manager.
<Datetime> <hostname> gdm[5517]: GdmDisplay: display lasted <n> seconds
.....
<Datetime> <hostname> gdm[5517]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors


The third line repeats five more times with different values for n seconds.



If it is relevant, I am using the nouveau driver on an Nvidia GTX GeForce 660 (OEM) card, and there is also an Intel on-board graphics cotroller driven by the i915 module, as informed by the output of the 'lspci -k' command.



My questions are:
(1) Is my hunch that only the window manager has crashed and the rest of the system is still functioning correct?
(2) Where can I find the X server log cited above?
(3) I read that it is possible to reinstall the display manager on distributions other than Scientific Linux and want to know if that is a possibility here?
(4) Is there a way to recover display functionality without taking the step of reinstallation if that is an option?



Thank you many times.










share|improve this question





























    0















    About half a month ago, I installed Scientific Linux 7.6 on a computer that has shut down and restarted daily as expected until today. Details of the operating system are below.




    1. Full version number: (3.10.0-957.1.3.el7.x86_64) 7.6 (Nitrogen)

    2. Desktop: Gnome


    Today when I turn back on the computer, the gnome desktop won't load. The boot up proceeds as expected until the grey-blue screen showing a spinning wheel (the one with radial lines). Then about when the wheel is supposed to pick up speed and take you to the login page with usernames to select from, it breaks into the terminal mode text with status messages. They all show [ OK ] in green except for these lines repeated once:



    [ INFO ] dev-virtiox2dports-com.redhat.spice.0.device is not active.
    [DEPEND] Dependency failed for Activation socket for spice guest agent daemon
    .....


    Also the last line (before the display manager load hangs) reads thus:



      OK  ] Started Crash recovery kernel arming.. to Quit.........ice.emon.549..progress polling....


    As you can see the messages there are garbled and the [ OK ] label is missing the leading bracket too.



    It looks horrid so far, but I am able to navigate to a login screen and appropriate a terminal with (Alt,F2) through (Alt, F6), and then log in as one of the users or as root, likewise.



    So I am hoping that more than the window manager is not malfunctioning. When I check on the status of gdm.service, I find that it shows as 'active (running)' but there are also these messages.



    <Datetime> <hostname> systemd[1]: Starting GNOME Display Manager...
    <Datetime> <hostname> systemd[1]: Started GNOME Display Manager.
    <Datetime> <hostname> gdm[5517]: GdmDisplay: display lasted <n> seconds
    .....
    <Datetime> <hostname> gdm[5517]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors


    The third line repeats five more times with different values for n seconds.



    If it is relevant, I am using the nouveau driver on an Nvidia GTX GeForce 660 (OEM) card, and there is also an Intel on-board graphics cotroller driven by the i915 module, as informed by the output of the 'lspci -k' command.



    My questions are:
    (1) Is my hunch that only the window manager has crashed and the rest of the system is still functioning correct?
    (2) Where can I find the X server log cited above?
    (3) I read that it is possible to reinstall the display manager on distributions other than Scientific Linux and want to know if that is a possibility here?
    (4) Is there a way to recover display functionality without taking the step of reinstallation if that is an option?



    Thank you many times.










    share|improve this question



























      0












      0








      0








      About half a month ago, I installed Scientific Linux 7.6 on a computer that has shut down and restarted daily as expected until today. Details of the operating system are below.




      1. Full version number: (3.10.0-957.1.3.el7.x86_64) 7.6 (Nitrogen)

      2. Desktop: Gnome


      Today when I turn back on the computer, the gnome desktop won't load. The boot up proceeds as expected until the grey-blue screen showing a spinning wheel (the one with radial lines). Then about when the wheel is supposed to pick up speed and take you to the login page with usernames to select from, it breaks into the terminal mode text with status messages. They all show [ OK ] in green except for these lines repeated once:



      [ INFO ] dev-virtiox2dports-com.redhat.spice.0.device is not active.
      [DEPEND] Dependency failed for Activation socket for spice guest agent daemon
      .....


      Also the last line (before the display manager load hangs) reads thus:



        OK  ] Started Crash recovery kernel arming.. to Quit.........ice.emon.549..progress polling....


      As you can see the messages there are garbled and the [ OK ] label is missing the leading bracket too.



      It looks horrid so far, but I am able to navigate to a login screen and appropriate a terminal with (Alt,F2) through (Alt, F6), and then log in as one of the users or as root, likewise.



      So I am hoping that more than the window manager is not malfunctioning. When I check on the status of gdm.service, I find that it shows as 'active (running)' but there are also these messages.



      <Datetime> <hostname> systemd[1]: Starting GNOME Display Manager...
      <Datetime> <hostname> systemd[1]: Started GNOME Display Manager.
      <Datetime> <hostname> gdm[5517]: GdmDisplay: display lasted <n> seconds
      .....
      <Datetime> <hostname> gdm[5517]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors


      The third line repeats five more times with different values for n seconds.



      If it is relevant, I am using the nouveau driver on an Nvidia GTX GeForce 660 (OEM) card, and there is also an Intel on-board graphics cotroller driven by the i915 module, as informed by the output of the 'lspci -k' command.



      My questions are:
      (1) Is my hunch that only the window manager has crashed and the rest of the system is still functioning correct?
      (2) Where can I find the X server log cited above?
      (3) I read that it is possible to reinstall the display manager on distributions other than Scientific Linux and want to know if that is a possibility here?
      (4) Is there a way to recover display functionality without taking the step of reinstallation if that is an option?



      Thank you many times.










      share|improve this question
















      About half a month ago, I installed Scientific Linux 7.6 on a computer that has shut down and restarted daily as expected until today. Details of the operating system are below.




      1. Full version number: (3.10.0-957.1.3.el7.x86_64) 7.6 (Nitrogen)

      2. Desktop: Gnome


      Today when I turn back on the computer, the gnome desktop won't load. The boot up proceeds as expected until the grey-blue screen showing a spinning wheel (the one with radial lines). Then about when the wheel is supposed to pick up speed and take you to the login page with usernames to select from, it breaks into the terminal mode text with status messages. They all show [ OK ] in green except for these lines repeated once:



      [ INFO ] dev-virtiox2dports-com.redhat.spice.0.device is not active.
      [DEPEND] Dependency failed for Activation socket for spice guest agent daemon
      .....


      Also the last line (before the display manager load hangs) reads thus:



        OK  ] Started Crash recovery kernel arming.. to Quit.........ice.emon.549..progress polling....


      As you can see the messages there are garbled and the [ OK ] label is missing the leading bracket too.



      It looks horrid so far, but I am able to navigate to a login screen and appropriate a terminal with (Alt,F2) through (Alt, F6), and then log in as one of the users or as root, likewise.



      So I am hoping that more than the window manager is not malfunctioning. When I check on the status of gdm.service, I find that it shows as 'active (running)' but there are also these messages.



      <Datetime> <hostname> systemd[1]: Starting GNOME Display Manager...
      <Datetime> <hostname> systemd[1]: Started GNOME Display Manager.
      <Datetime> <hostname> gdm[5517]: GdmDisplay: display lasted <n> seconds
      .....
      <Datetime> <hostname> gdm[5517]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors


      The third line repeats five more times with different values for n seconds.



      If it is relevant, I am using the nouveau driver on an Nvidia GTX GeForce 660 (OEM) card, and there is also an Intel on-board graphics cotroller driven by the i915 module, as informed by the output of the 'lspci -k' command.



      My questions are:
      (1) Is my hunch that only the window manager has crashed and the rest of the system is still functioning correct?
      (2) Where can I find the X server log cited above?
      (3) I read that it is possible to reinstall the display manager on distributions other than Scientific Linux and want to know if that is a possibility here?
      (4) Is there a way to recover display functionality without taking the step of reinstallation if that is an option?



      Thank you many times.







      linux boot gnome login-screen scientific-linux






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 6 at 16:38







      Psmith

















      asked Feb 6 at 6:40









      PsmithPsmith

      11




      11






















          1 Answer
          1






          active

          oldest

          votes


















          0














          I've been able to restore access to the Gnome desktop by black listing the i915 driver for the Intel (on-board) controller.



          I read (1) that this might result in interference, and though the context there is different, I tried it. These are the commands I ran in a terminal window.



          vi /etc/modprobe.d/blacklist.conf
          mv /boot/initramfs-$(uname -r).img /boot/initramfs-Intel-i915-$(uname -r).img
          dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
          reboot


          When the machine restarts it proceeds beyond the blue-grey screen and the spinning wheel right through to the login screen for the Gnome desktop this time.



          I don't know if this is the last of the problem, since I am still using the nouveau driver, which is reported here and there as being unreliable, but for now the problem has been evaded temporarily at least. Any comments on the case would still be helpful.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2fsuperuser.com%2fquestions%2f1402538%2fscientific-linux-gnome-desktop-not-loading%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I've been able to restore access to the Gnome desktop by black listing the i915 driver for the Intel (on-board) controller.



            I read (1) that this might result in interference, and though the context there is different, I tried it. These are the commands I ran in a terminal window.



            vi /etc/modprobe.d/blacklist.conf
            mv /boot/initramfs-$(uname -r).img /boot/initramfs-Intel-i915-$(uname -r).img
            dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
            reboot


            When the machine restarts it proceeds beyond the blue-grey screen and the spinning wheel right through to the login screen for the Gnome desktop this time.



            I don't know if this is the last of the problem, since I am still using the nouveau driver, which is reported here and there as being unreliable, but for now the problem has been evaded temporarily at least. Any comments on the case would still be helpful.






            share|improve this answer




























              0














              I've been able to restore access to the Gnome desktop by black listing the i915 driver for the Intel (on-board) controller.



              I read (1) that this might result in interference, and though the context there is different, I tried it. These are the commands I ran in a terminal window.



              vi /etc/modprobe.d/blacklist.conf
              mv /boot/initramfs-$(uname -r).img /boot/initramfs-Intel-i915-$(uname -r).img
              dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
              reboot


              When the machine restarts it proceeds beyond the blue-grey screen and the spinning wheel right through to the login screen for the Gnome desktop this time.



              I don't know if this is the last of the problem, since I am still using the nouveau driver, which is reported here and there as being unreliable, but for now the problem has been evaded temporarily at least. Any comments on the case would still be helpful.






              share|improve this answer


























                0












                0








                0







                I've been able to restore access to the Gnome desktop by black listing the i915 driver for the Intel (on-board) controller.



                I read (1) that this might result in interference, and though the context there is different, I tried it. These are the commands I ran in a terminal window.



                vi /etc/modprobe.d/blacklist.conf
                mv /boot/initramfs-$(uname -r).img /boot/initramfs-Intel-i915-$(uname -r).img
                dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
                reboot


                When the machine restarts it proceeds beyond the blue-grey screen and the spinning wheel right through to the login screen for the Gnome desktop this time.



                I don't know if this is the last of the problem, since I am still using the nouveau driver, which is reported here and there as being unreliable, but for now the problem has been evaded temporarily at least. Any comments on the case would still be helpful.






                share|improve this answer













                I've been able to restore access to the Gnome desktop by black listing the i915 driver for the Intel (on-board) controller.



                I read (1) that this might result in interference, and though the context there is different, I tried it. These are the commands I ran in a terminal window.



                vi /etc/modprobe.d/blacklist.conf
                mv /boot/initramfs-$(uname -r).img /boot/initramfs-Intel-i915-$(uname -r).img
                dracut -v /boot/initramfs-$(uname -r).img $(uname -r)
                reboot


                When the machine restarts it proceeds beyond the blue-grey screen and the spinning wheel right through to the login screen for the Gnome desktop this time.



                I don't know if this is the last of the problem, since I am still using the nouveau driver, which is reported here and there as being unreliable, but for now the problem has been evaded temporarily at least. Any comments on the case would still be helpful.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 6 at 17:51









                PsmithPsmith

                11




                11






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1402538%2fscientific-linux-gnome-desktop-not-loading%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

                    How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

                    is 'sed' thread safe

                    How to make a Squid Proxy server?