Resume from standby total freeze on Dapper Drake 6.06, Toshiba M35-S3592

Bug #53591 reported by dennis1200
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Set system to go into suspend (s3), which functions correctly. Upon re-opening the lid it freezes at a black screen (no image, no backlight, no response from key combinations, though the led lights on the keyboard work). when attempting to run suspend in s1 after altering acpi-support (not exactly sure what the difference is supposed to be, just that there is one), it goes to a password prompt with a fair amount of hard drive activity (comparable, if not the same as normal when I'm not doing anything). Upon resume (from "s1" - not sure if i get there) everything works fine, but there is a small notification box in the lower right hand corner (a bit off screen, unfortunately), saying that the entry into suspend has failed. The failure of s3 is my main problem though, and the only thing keeping me from a total switch from windows.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

Changed in linux-source-2.6.15:
importance: Undecided → High
status: Unconfirmed → Needs Info
Revision history for this message
dennis1200 (dennis-fiser) wrote : Re: [Bug 53591] Re: Resume from standby total freeze on Dapper Drake 6.06, Toshiba M35-S3592

No, this problem has been resolved. I run Feisty with 2.6.20-16. Suspend
works just fine. Good job team!

<email address hidden> wrote:
> Thank you for your bug report. Do you still have this issue with the
> latest release of Ubuntu ?
>
> ** Changed in: linux-source-2.6.15 (Ubuntu)
> Importance: Undecided => High
> Status: Unconfirmed => Needs Info
>

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Ok thank you, I'm marking this as fixed.

Changed in linux-source-2.6.15:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.