Laptop screen stays blank after lid is reopened











up vote
3
down vote

favorite
1












I have an Acer Aspire One KAV60. Beginning with 11.10 through 12.10, every version of Ubuntu causes the screen to stay blank after I open the lid. The only way I can get out of the problem is a hard restart. Hitting the esc key or left mouse button causes the screen to flash on for a fraction of a second and I can see a working display when this happens, but I can't keep it on with any keystroke combination I have tried.



I have turned off all power saving options, disabled standby, and selected do nothing when the lid is closed. Nothing has any effect.



To avoid this problem (which often results in lost data if the lid is accidently closed before a program save) I have to stay with 11.04 even though it is now no longer supported.



There seem to be some bug fixes shown for this problem, but they specify non-intel graphics cards. My laptop has an on-board intel video driver. Under any circumstances, there seems to be no timeframe for fixing the bugs that are shown to exist.



Any suggestions will be greatly appreciated.










share|improve this question


























    up vote
    3
    down vote

    favorite
    1












    I have an Acer Aspire One KAV60. Beginning with 11.10 through 12.10, every version of Ubuntu causes the screen to stay blank after I open the lid. The only way I can get out of the problem is a hard restart. Hitting the esc key or left mouse button causes the screen to flash on for a fraction of a second and I can see a working display when this happens, but I can't keep it on with any keystroke combination I have tried.



    I have turned off all power saving options, disabled standby, and selected do nothing when the lid is closed. Nothing has any effect.



    To avoid this problem (which often results in lost data if the lid is accidently closed before a program save) I have to stay with 11.04 even though it is now no longer supported.



    There seem to be some bug fixes shown for this problem, but they specify non-intel graphics cards. My laptop has an on-board intel video driver. Under any circumstances, there seems to be no timeframe for fixing the bugs that are shown to exist.



    Any suggestions will be greatly appreciated.










    share|improve this question
























      up vote
      3
      down vote

      favorite
      1









      up vote
      3
      down vote

      favorite
      1






      1





      I have an Acer Aspire One KAV60. Beginning with 11.10 through 12.10, every version of Ubuntu causes the screen to stay blank after I open the lid. The only way I can get out of the problem is a hard restart. Hitting the esc key or left mouse button causes the screen to flash on for a fraction of a second and I can see a working display when this happens, but I can't keep it on with any keystroke combination I have tried.



      I have turned off all power saving options, disabled standby, and selected do nothing when the lid is closed. Nothing has any effect.



      To avoid this problem (which often results in lost data if the lid is accidently closed before a program save) I have to stay with 11.04 even though it is now no longer supported.



      There seem to be some bug fixes shown for this problem, but they specify non-intel graphics cards. My laptop has an on-board intel video driver. Under any circumstances, there seems to be no timeframe for fixing the bugs that are shown to exist.



      Any suggestions will be greatly appreciated.










      share|improve this question













      I have an Acer Aspire One KAV60. Beginning with 11.10 through 12.10, every version of Ubuntu causes the screen to stay blank after I open the lid. The only way I can get out of the problem is a hard restart. Hitting the esc key or left mouse button causes the screen to flash on for a fraction of a second and I can see a working display when this happens, but I can't keep it on with any keystroke combination I have tried.



      I have turned off all power saving options, disabled standby, and selected do nothing when the lid is closed. Nothing has any effect.



      To avoid this problem (which often results in lost data if the lid is accidently closed before a program save) I have to stay with 11.04 even though it is now no longer supported.



      There seem to be some bug fixes shown for this problem, but they specify non-intel graphics cards. My laptop has an on-board intel video driver. Under any circumstances, there seems to be no timeframe for fixing the bugs that are shown to exist.



      Any suggestions will be greatly appreciated.







      laptop screen aspire-one






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 29 '13 at 12:44









      user127015

      1613




      1613






















          4 Answers
          4






          active

          oldest

          votes

















          up vote
          4
          down vote













          There is a post from devilkin that solved my problem, here is the solution:



          It requires the ACPI VIDEO module loaded.





          Create the file /etc/acpi/lidswitch.sh with these lines (don't forget to chmod +x on it):



          #!/bin/sh
          # /etc/acpi/lidswitch.sh
          # Re-activates the screen when the lid is opened again

          LID_STATE="/proc/acpi/button/lid/LID/state"
          LCD_STATE="/proc/acpi/video/VID1/LCD/state"

          grep -q open $LID_STATE

          if [ $? -eq 0 ]; then
          echo 0x80000001 > $LCD_STATE
          fi




          Then put these lines in /etc/acpi/events/lidswitch (lidswitch not being a folder, but a file without a file extension):



          # /etc/acpi/events/lidswitch
          # This is called when the lid is closed or opened and calls
          # /etc/acpi/lidswitch.sh for further processing.

          event=button[ /]lid
          action=/etc/acpi/lidswitch.sh


          Extra help:



          (1) Use gedit to create these files. So open up Terminal, then type in 'sudo gedit' (without quotes) and copy and paste the lines above.



          (2) Use nautilus to apply the "chmod +x" property to the file. To do this, open up Terminal, then type in 'sudo nautilus' (without quotes) and the navigate to etc, acpi, then right-click on lidswitch.sh, navigate to Properties, then Permissions, then Allow executing file as program, then click Close.






          share|improve this answer























          • Thanks for the clear answer, however I have some trouble with it.. since I dont have a /acpi/video folder... so I cant get the LCD state. Is there any other way?
            – zwep
            Oct 17 at 7:28


















          up vote
          1
          down vote













          Create the file /etc/acpi/lidswitch.sh with content (don't forget to chmod +x on it):



          #!/bin/sh
          # /etc/acpi/lidswitch.sh
          # Re-activates the screen when the lid is opened again

          LID_STATE="/proc/acpi/button/lid/LID/state"
          LCD_STATE="/proc/acpi/video/VID1/LCD/state"

          grep -q open $LID_STATE

          if [ $? -eq 0 ]; then
          echo 0x80000001 > $LCD_STATE
          fi


          Place a new script inside this folder?--->>/etc/acpi/events/lidswitch



          Then put this in /etc/acpi/events/lidswitch:



          # /etc/acpi/events/lidswitch
          # This is called when the lid is closed or opened and calls
          # /etc/acpi/lidswitch.sh for further processing.

          event=button[ /]lid
          action=/etc/acpi/lidswitch.sh





          share|improve this answer






























            up vote
            0
            down vote













            I had the same issue even in Ubuntu 10.04, but,



            With me, changing the value from "blank" to "nothing" in the lid close options solved the issue.



            There is some difference with the two options though.



            With "blank" if I close the lid, video playback stopped (No audio of the video playback in mplayer while the lid was closed), however pure audio playback still continued (e.g. in Rhythmbox). If i now open the lid, i only get a blank screen and the only way out was to press the power button. this will cause the system to suspend and then i have to again wake it up to get a display.



            With "nothing", both audio and video files continues to play even with the lid closed. And when i open the lid, i see the normal display again:)



            To automatically set the values from blank to nothing, i did this in terminal:



            sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_ac -s "nothing"

            sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_battery -s "nothing"


            To do this manually, open the gconf-editor by hiting alt+F2 and then enter gconf-editor. Then, browse to apps->gnome-power-manager->buttons and change the values of lid_ac and lid_battery manually



            Hope it helps in the newer versions also.






            share|improve this answer






























              up vote
              0
              down vote













              None of the solutions worked for me, but the solution provided by ubuntu faqs worked for me. I followed this and it worked smoothly.



              'INFO: This will not work for 12.04, resume from hibernate work differently in 12.04.'



              Pull up a Terminal again and run cat /proc/swaps and hopefully you see the path to your swap partition listed there. If not chances are something went wrong in the steps above. Here's my output: 


              Filename Type Size Used Priority
              /dev/sda2 partition 2676732 73380 -1



              gksu gedit /etc/default/grub & to pull up the boot loader configuration

              Look for the line GRUB_CMDLINE_LINUX="" and make sure it looks like this (using your UUID of course) GRUB_CMDLINE_LINUX="resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7" and save the file

              sudo update-grub and wait for it to finish

              gksu gedit /etc/initramfs-tools/conf.d/resume & and make sure its contents are resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7 (with your UUID of course in place of mine). Save the file!

              sudo update-initramfs -u
              Reboot!


              Now you should be able to hibernate and resume!



              found solution here https://help.ubuntu.com/community/SwapFaq






              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: 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%2faskubuntu.com%2fquestions%2f248967%2flaptop-screen-stays-blank-after-lid-is-reopened%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                4 Answers
                4






                active

                oldest

                votes








                4 Answers
                4






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes








                up vote
                4
                down vote













                There is a post from devilkin that solved my problem, here is the solution:



                It requires the ACPI VIDEO module loaded.





                Create the file /etc/acpi/lidswitch.sh with these lines (don't forget to chmod +x on it):



                #!/bin/sh
                # /etc/acpi/lidswitch.sh
                # Re-activates the screen when the lid is opened again

                LID_STATE="/proc/acpi/button/lid/LID/state"
                LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                grep -q open $LID_STATE

                if [ $? -eq 0 ]; then
                echo 0x80000001 > $LCD_STATE
                fi




                Then put these lines in /etc/acpi/events/lidswitch (lidswitch not being a folder, but a file without a file extension):



                # /etc/acpi/events/lidswitch
                # This is called when the lid is closed or opened and calls
                # /etc/acpi/lidswitch.sh for further processing.

                event=button[ /]lid
                action=/etc/acpi/lidswitch.sh


                Extra help:



                (1) Use gedit to create these files. So open up Terminal, then type in 'sudo gedit' (without quotes) and copy and paste the lines above.



                (2) Use nautilus to apply the "chmod +x" property to the file. To do this, open up Terminal, then type in 'sudo nautilus' (without quotes) and the navigate to etc, acpi, then right-click on lidswitch.sh, navigate to Properties, then Permissions, then Allow executing file as program, then click Close.






                share|improve this answer























                • Thanks for the clear answer, however I have some trouble with it.. since I dont have a /acpi/video folder... so I cant get the LCD state. Is there any other way?
                  – zwep
                  Oct 17 at 7:28















                up vote
                4
                down vote













                There is a post from devilkin that solved my problem, here is the solution:



                It requires the ACPI VIDEO module loaded.





                Create the file /etc/acpi/lidswitch.sh with these lines (don't forget to chmod +x on it):



                #!/bin/sh
                # /etc/acpi/lidswitch.sh
                # Re-activates the screen when the lid is opened again

                LID_STATE="/proc/acpi/button/lid/LID/state"
                LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                grep -q open $LID_STATE

                if [ $? -eq 0 ]; then
                echo 0x80000001 > $LCD_STATE
                fi




                Then put these lines in /etc/acpi/events/lidswitch (lidswitch not being a folder, but a file without a file extension):



                # /etc/acpi/events/lidswitch
                # This is called when the lid is closed or opened and calls
                # /etc/acpi/lidswitch.sh for further processing.

                event=button[ /]lid
                action=/etc/acpi/lidswitch.sh


                Extra help:



                (1) Use gedit to create these files. So open up Terminal, then type in 'sudo gedit' (without quotes) and copy and paste the lines above.



                (2) Use nautilus to apply the "chmod +x" property to the file. To do this, open up Terminal, then type in 'sudo nautilus' (without quotes) and the navigate to etc, acpi, then right-click on lidswitch.sh, navigate to Properties, then Permissions, then Allow executing file as program, then click Close.






                share|improve this answer























                • Thanks for the clear answer, however I have some trouble with it.. since I dont have a /acpi/video folder... so I cant get the LCD state. Is there any other way?
                  – zwep
                  Oct 17 at 7:28













                up vote
                4
                down vote










                up vote
                4
                down vote









                There is a post from devilkin that solved my problem, here is the solution:



                It requires the ACPI VIDEO module loaded.





                Create the file /etc/acpi/lidswitch.sh with these lines (don't forget to chmod +x on it):



                #!/bin/sh
                # /etc/acpi/lidswitch.sh
                # Re-activates the screen when the lid is opened again

                LID_STATE="/proc/acpi/button/lid/LID/state"
                LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                grep -q open $LID_STATE

                if [ $? -eq 0 ]; then
                echo 0x80000001 > $LCD_STATE
                fi




                Then put these lines in /etc/acpi/events/lidswitch (lidswitch not being a folder, but a file without a file extension):



                # /etc/acpi/events/lidswitch
                # This is called when the lid is closed or opened and calls
                # /etc/acpi/lidswitch.sh for further processing.

                event=button[ /]lid
                action=/etc/acpi/lidswitch.sh


                Extra help:



                (1) Use gedit to create these files. So open up Terminal, then type in 'sudo gedit' (without quotes) and copy and paste the lines above.



                (2) Use nautilus to apply the "chmod +x" property to the file. To do this, open up Terminal, then type in 'sudo nautilus' (without quotes) and the navigate to etc, acpi, then right-click on lidswitch.sh, navigate to Properties, then Permissions, then Allow executing file as program, then click Close.






                share|improve this answer














                There is a post from devilkin that solved my problem, here is the solution:



                It requires the ACPI VIDEO module loaded.





                Create the file /etc/acpi/lidswitch.sh with these lines (don't forget to chmod +x on it):



                #!/bin/sh
                # /etc/acpi/lidswitch.sh
                # Re-activates the screen when the lid is opened again

                LID_STATE="/proc/acpi/button/lid/LID/state"
                LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                grep -q open $LID_STATE

                if [ $? -eq 0 ]; then
                echo 0x80000001 > $LCD_STATE
                fi




                Then put these lines in /etc/acpi/events/lidswitch (lidswitch not being a folder, but a file without a file extension):



                # /etc/acpi/events/lidswitch
                # This is called when the lid is closed or opened and calls
                # /etc/acpi/lidswitch.sh for further processing.

                event=button[ /]lid
                action=/etc/acpi/lidswitch.sh


                Extra help:



                (1) Use gedit to create these files. So open up Terminal, then type in 'sudo gedit' (without quotes) and copy and paste the lines above.



                (2) Use nautilus to apply the "chmod +x" property to the file. To do this, open up Terminal, then type in 'sudo nautilus' (without quotes) and the navigate to etc, acpi, then right-click on lidswitch.sh, navigate to Properties, then Permissions, then Allow executing file as program, then click Close.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Dec 2 '13 at 15:06









                user221358

                32




                32










                answered Feb 8 '13 at 18:14









                Adriano P

                1414




                1414












                • Thanks for the clear answer, however I have some trouble with it.. since I dont have a /acpi/video folder... so I cant get the LCD state. Is there any other way?
                  – zwep
                  Oct 17 at 7:28


















                • Thanks for the clear answer, however I have some trouble with it.. since I dont have a /acpi/video folder... so I cant get the LCD state. Is there any other way?
                  – zwep
                  Oct 17 at 7:28
















                Thanks for the clear answer, however I have some trouble with it.. since I dont have a /acpi/video folder... so I cant get the LCD state. Is there any other way?
                – zwep
                Oct 17 at 7:28




                Thanks for the clear answer, however I have some trouble with it.. since I dont have a /acpi/video folder... so I cant get the LCD state. Is there any other way?
                – zwep
                Oct 17 at 7:28












                up vote
                1
                down vote













                Create the file /etc/acpi/lidswitch.sh with content (don't forget to chmod +x on it):



                #!/bin/sh
                # /etc/acpi/lidswitch.sh
                # Re-activates the screen when the lid is opened again

                LID_STATE="/proc/acpi/button/lid/LID/state"
                LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                grep -q open $LID_STATE

                if [ $? -eq 0 ]; then
                echo 0x80000001 > $LCD_STATE
                fi


                Place a new script inside this folder?--->>/etc/acpi/events/lidswitch



                Then put this in /etc/acpi/events/lidswitch:



                # /etc/acpi/events/lidswitch
                # This is called when the lid is closed or opened and calls
                # /etc/acpi/lidswitch.sh for further processing.

                event=button[ /]lid
                action=/etc/acpi/lidswitch.sh





                share|improve this answer



























                  up vote
                  1
                  down vote













                  Create the file /etc/acpi/lidswitch.sh with content (don't forget to chmod +x on it):



                  #!/bin/sh
                  # /etc/acpi/lidswitch.sh
                  # Re-activates the screen when the lid is opened again

                  LID_STATE="/proc/acpi/button/lid/LID/state"
                  LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                  grep -q open $LID_STATE

                  if [ $? -eq 0 ]; then
                  echo 0x80000001 > $LCD_STATE
                  fi


                  Place a new script inside this folder?--->>/etc/acpi/events/lidswitch



                  Then put this in /etc/acpi/events/lidswitch:



                  # /etc/acpi/events/lidswitch
                  # This is called when the lid is closed or opened and calls
                  # /etc/acpi/lidswitch.sh for further processing.

                  event=button[ /]lid
                  action=/etc/acpi/lidswitch.sh





                  share|improve this answer

























                    up vote
                    1
                    down vote










                    up vote
                    1
                    down vote









                    Create the file /etc/acpi/lidswitch.sh with content (don't forget to chmod +x on it):



                    #!/bin/sh
                    # /etc/acpi/lidswitch.sh
                    # Re-activates the screen when the lid is opened again

                    LID_STATE="/proc/acpi/button/lid/LID/state"
                    LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                    grep -q open $LID_STATE

                    if [ $? -eq 0 ]; then
                    echo 0x80000001 > $LCD_STATE
                    fi


                    Place a new script inside this folder?--->>/etc/acpi/events/lidswitch



                    Then put this in /etc/acpi/events/lidswitch:



                    # /etc/acpi/events/lidswitch
                    # This is called when the lid is closed or opened and calls
                    # /etc/acpi/lidswitch.sh for further processing.

                    event=button[ /]lid
                    action=/etc/acpi/lidswitch.sh





                    share|improve this answer














                    Create the file /etc/acpi/lidswitch.sh with content (don't forget to chmod +x on it):



                    #!/bin/sh
                    # /etc/acpi/lidswitch.sh
                    # Re-activates the screen when the lid is opened again

                    LID_STATE="/proc/acpi/button/lid/LID/state"
                    LCD_STATE="/proc/acpi/video/VID1/LCD/state"

                    grep -q open $LID_STATE

                    if [ $? -eq 0 ]; then
                    echo 0x80000001 > $LCD_STATE
                    fi


                    Place a new script inside this folder?--->>/etc/acpi/events/lidswitch



                    Then put this in /etc/acpi/events/lidswitch:



                    # /etc/acpi/events/lidswitch
                    # This is called when the lid is closed or opened and calls
                    # /etc/acpi/lidswitch.sh for further processing.

                    event=button[ /]lid
                    action=/etc/acpi/lidswitch.sh






                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Sep 12 '13 at 7:59









                    Warren Hill

                    15.2k165376




                    15.2k165376










                    answered Sep 12 '13 at 7:01









                    user192225

                    111




                    111






















                        up vote
                        0
                        down vote













                        I had the same issue even in Ubuntu 10.04, but,



                        With me, changing the value from "blank" to "nothing" in the lid close options solved the issue.



                        There is some difference with the two options though.



                        With "blank" if I close the lid, video playback stopped (No audio of the video playback in mplayer while the lid was closed), however pure audio playback still continued (e.g. in Rhythmbox). If i now open the lid, i only get a blank screen and the only way out was to press the power button. this will cause the system to suspend and then i have to again wake it up to get a display.



                        With "nothing", both audio and video files continues to play even with the lid closed. And when i open the lid, i see the normal display again:)



                        To automatically set the values from blank to nothing, i did this in terminal:



                        sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_ac -s "nothing"

                        sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_battery -s "nothing"


                        To do this manually, open the gconf-editor by hiting alt+F2 and then enter gconf-editor. Then, browse to apps->gnome-power-manager->buttons and change the values of lid_ac and lid_battery manually



                        Hope it helps in the newer versions also.






                        share|improve this answer



























                          up vote
                          0
                          down vote













                          I had the same issue even in Ubuntu 10.04, but,



                          With me, changing the value from "blank" to "nothing" in the lid close options solved the issue.



                          There is some difference with the two options though.



                          With "blank" if I close the lid, video playback stopped (No audio of the video playback in mplayer while the lid was closed), however pure audio playback still continued (e.g. in Rhythmbox). If i now open the lid, i only get a blank screen and the only way out was to press the power button. this will cause the system to suspend and then i have to again wake it up to get a display.



                          With "nothing", both audio and video files continues to play even with the lid closed. And when i open the lid, i see the normal display again:)



                          To automatically set the values from blank to nothing, i did this in terminal:



                          sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_ac -s "nothing"

                          sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_battery -s "nothing"


                          To do this manually, open the gconf-editor by hiting alt+F2 and then enter gconf-editor. Then, browse to apps->gnome-power-manager->buttons and change the values of lid_ac and lid_battery manually



                          Hope it helps in the newer versions also.






                          share|improve this answer

























                            up vote
                            0
                            down vote










                            up vote
                            0
                            down vote









                            I had the same issue even in Ubuntu 10.04, but,



                            With me, changing the value from "blank" to "nothing" in the lid close options solved the issue.



                            There is some difference with the two options though.



                            With "blank" if I close the lid, video playback stopped (No audio of the video playback in mplayer while the lid was closed), however pure audio playback still continued (e.g. in Rhythmbox). If i now open the lid, i only get a blank screen and the only way out was to press the power button. this will cause the system to suspend and then i have to again wake it up to get a display.



                            With "nothing", both audio and video files continues to play even with the lid closed. And when i open the lid, i see the normal display again:)



                            To automatically set the values from blank to nothing, i did this in terminal:



                            sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_ac -s "nothing"

                            sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_battery -s "nothing"


                            To do this manually, open the gconf-editor by hiting alt+F2 and then enter gconf-editor. Then, browse to apps->gnome-power-manager->buttons and change the values of lid_ac and lid_battery manually



                            Hope it helps in the newer versions also.






                            share|improve this answer














                            I had the same issue even in Ubuntu 10.04, but,



                            With me, changing the value from "blank" to "nothing" in the lid close options solved the issue.



                            There is some difference with the two options though.



                            With "blank" if I close the lid, video playback stopped (No audio of the video playback in mplayer while the lid was closed), however pure audio playback still continued (e.g. in Rhythmbox). If i now open the lid, i only get a blank screen and the only way out was to press the power button. this will cause the system to suspend and then i have to again wake it up to get a display.



                            With "nothing", both audio and video files continues to play even with the lid closed. And when i open the lid, i see the normal display again:)



                            To automatically set the values from blank to nothing, i did this in terminal:



                            sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_ac -s "nothing"

                            sudo gconftool-2 -t string /apps/gnome-power-manager/buttons/lid_battery -s "nothing"


                            To do this manually, open the gconf-editor by hiting alt+F2 and then enter gconf-editor. Then, browse to apps->gnome-power-manager->buttons and change the values of lid_ac and lid_battery manually



                            Hope it helps in the newer versions also.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Sep 21 '14 at 17:22









                            hmayag

                            1,97831318




                            1,97831318










                            answered Sep 21 '14 at 15:53









                            Stuffed with Apps

                            1




                            1






















                                up vote
                                0
                                down vote













                                None of the solutions worked for me, but the solution provided by ubuntu faqs worked for me. I followed this and it worked smoothly.



                                'INFO: This will not work for 12.04, resume from hibernate work differently in 12.04.'



                                Pull up a Terminal again and run cat /proc/swaps and hopefully you see the path to your swap partition listed there. If not chances are something went wrong in the steps above. Here's my output: 


                                Filename Type Size Used Priority
                                /dev/sda2 partition 2676732 73380 -1



                                gksu gedit /etc/default/grub & to pull up the boot loader configuration

                                Look for the line GRUB_CMDLINE_LINUX="" and make sure it looks like this (using your UUID of course) GRUB_CMDLINE_LINUX="resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7" and save the file

                                sudo update-grub and wait for it to finish

                                gksu gedit /etc/initramfs-tools/conf.d/resume & and make sure its contents are resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7 (with your UUID of course in place of mine). Save the file!

                                sudo update-initramfs -u
                                Reboot!


                                Now you should be able to hibernate and resume!



                                found solution here https://help.ubuntu.com/community/SwapFaq






                                share|improve this answer

























                                  up vote
                                  0
                                  down vote













                                  None of the solutions worked for me, but the solution provided by ubuntu faqs worked for me. I followed this and it worked smoothly.



                                  'INFO: This will not work for 12.04, resume from hibernate work differently in 12.04.'



                                  Pull up a Terminal again and run cat /proc/swaps and hopefully you see the path to your swap partition listed there. If not chances are something went wrong in the steps above. Here's my output: 


                                  Filename Type Size Used Priority
                                  /dev/sda2 partition 2676732 73380 -1



                                  gksu gedit /etc/default/grub & to pull up the boot loader configuration

                                  Look for the line GRUB_CMDLINE_LINUX="" and make sure it looks like this (using your UUID of course) GRUB_CMDLINE_LINUX="resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7" and save the file

                                  sudo update-grub and wait for it to finish

                                  gksu gedit /etc/initramfs-tools/conf.d/resume & and make sure its contents are resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7 (with your UUID of course in place of mine). Save the file!

                                  sudo update-initramfs -u
                                  Reboot!


                                  Now you should be able to hibernate and resume!



                                  found solution here https://help.ubuntu.com/community/SwapFaq






                                  share|improve this answer























                                    up vote
                                    0
                                    down vote










                                    up vote
                                    0
                                    down vote









                                    None of the solutions worked for me, but the solution provided by ubuntu faqs worked for me. I followed this and it worked smoothly.



                                    'INFO: This will not work for 12.04, resume from hibernate work differently in 12.04.'



                                    Pull up a Terminal again and run cat /proc/swaps and hopefully you see the path to your swap partition listed there. If not chances are something went wrong in the steps above. Here's my output: 


                                    Filename Type Size Used Priority
                                    /dev/sda2 partition 2676732 73380 -1



                                    gksu gedit /etc/default/grub & to pull up the boot loader configuration

                                    Look for the line GRUB_CMDLINE_LINUX="" and make sure it looks like this (using your UUID of course) GRUB_CMDLINE_LINUX="resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7" and save the file

                                    sudo update-grub and wait for it to finish

                                    gksu gedit /etc/initramfs-tools/conf.d/resume & and make sure its contents are resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7 (with your UUID of course in place of mine). Save the file!

                                    sudo update-initramfs -u
                                    Reboot!


                                    Now you should be able to hibernate and resume!



                                    found solution here https://help.ubuntu.com/community/SwapFaq






                                    share|improve this answer












                                    None of the solutions worked for me, but the solution provided by ubuntu faqs worked for me. I followed this and it worked smoothly.



                                    'INFO: This will not work for 12.04, resume from hibernate work differently in 12.04.'



                                    Pull up a Terminal again and run cat /proc/swaps and hopefully you see the path to your swap partition listed there. If not chances are something went wrong in the steps above. Here's my output: 


                                    Filename Type Size Used Priority
                                    /dev/sda2 partition 2676732 73380 -1



                                    gksu gedit /etc/default/grub & to pull up the boot loader configuration

                                    Look for the line GRUB_CMDLINE_LINUX="" and make sure it looks like this (using your UUID of course) GRUB_CMDLINE_LINUX="resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7" and save the file

                                    sudo update-grub and wait for it to finish

                                    gksu gedit /etc/initramfs-tools/conf.d/resume & and make sure its contents are resume=UUID=41e86209-3802-424b-9a9d-d7683142dab7 (with your UUID of course in place of mine). Save the file!

                                    sudo update-initramfs -u
                                    Reboot!


                                    Now you should be able to hibernate and resume!



                                    found solution here https://help.ubuntu.com/community/SwapFaq







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Dec 4 at 13:03









                                    iamTAK

                                    1




                                    1






























                                        draft saved

                                        draft discarded




















































                                        Thanks for contributing an answer to Ask Ubuntu!


                                        • 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%2faskubuntu.com%2fquestions%2f248967%2flaptop-screen-stays-blank-after-lid-is-reopened%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

                                        Mouse cursor on multiple screens with different PPI

                                        Agildo Ribeiro

                                        Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”