blank screen for terminal shell when coming back from sleep

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still an issue for you? Thanks in advance.

Yes, problem is still very annoying. The situation has gotten worse as now even xrandr stopped functioning when returning from sleep.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in recently. We were wondering if this is still an issue for you? Thanks in advance.

I have added this comment to the bug

Yes, problem is still very annoying. The situation has gotten worse as
now even xrandr stopped functioning when returning from sleep.

On Dec 7, 2007 1:46 PM, Brian Murray <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in recently. We were wondering if this is still an issue
> for you? Thanks in advance.
>
>
> --
> blank screen for terminal shell when coming back from sleep
> https://bugs.launchpad.net/bugs/119901
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

$uname -a
Linux vader 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

After boot:

joseph@vader:~/119901$ xrandr -q
Screen 0: minimum 640 x 480, current 2960 x 1050, maximum 2960 x 1050
default connected 2960x1050+0+0 0mm x 0mm
   2960x1050 50.0*
   1680x1050 51.0
   1024x768 52.0
   800x600 53.0
   640x480 54.0
joseph@vader:~/119901$ xrandr -s 1
joseph@vader:~/119901$ xrandr -q
Screen 0: minimum 640 x 480, current 1680 x 1050, maximum 2960 x 1050
default connected 1680x1050+0+0 0mm x 0mm
   2960x1050 50.0
   1680x1050 51.0*
   1024x768 52.0
   800x600 53.0
   640x480 54.0

After return from suspend:

joseph@vader:~/119901$ xrandr -q
Screen 0: minimum 640 x 480, current 2960 x 1050, maximum 2960 x 1050
default connected 2960x1050+0+0 0mm x 0mm
   2960x1050 50.0*
   1680x1050 51.0
   1024x768 52.0
   800x600 53.0
   640x480 54.0
joseph@vader:~/119901$ xrandr -s 1
joseph@vader:~/119901$ xrandr -q
Screen 0: minimum 640 x 480, current 2960 x 1050, maximum 2960 x 1050
default connected 2960x1050+0+0 0mm x 0mm
   2960x1050 50.0*
   1680x1050 51.0
   1024x768 52.0
   800x600 53.0
   640x480 54.0

Thank you for taking the time to report this bug and helping to make Ubuntu better. The Hardy Heron Alpha series was recently released. Alpha2 and subsequent releases contain an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . Please note that Alpha3 will be released within the next day or two so you many want to wait. You should be able to then test this bug with the new kernel on the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks!

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I am closing this report against the old linux-source package since it is open and Incomplete for the current linux package.

Can you please let us know if this problem still exists in Intrepid (which is now stable)? If the problem still exists, please attach the information again that was requested in Comment 5 - https://wiki.ubuntu.com/KernelTeamBugPolicies - this time from Intrepid. Then we can re-mark this bug as Triaged.

Thank you in advance!

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!