Ubuntu
linux package

System suspends immediately after wake up without user interaction

Bug #278729 reported by Ante Karamatić
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I'm not sure this is a bug in kernel, but it is my best guess at the moment.

After pressing Fn+F3 on my Toshiba SatellitePro U200, system goes to sleep. After wake up, it immediately goes to back to sleep. I don't even see screensaver.

If I use System -> Shutdown -> Suspend, it goes to sleep and wakes up perfectly normal.

The difference from user point of view is that during menu initiated procedure, screen get's slowly dimmed. In the other case, if I press Fn+F3, system waits for couple of seconds and then just powers off the display.

This in on up to date Intrepid on 2008-10-05.

See original description
Ante Karamatić (ivoks)
description: updated
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

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 didn't include enough information.

Please include the information as separate attachments:
 * Output of uname -a
    * uname -a > uname.txt
 * Output of sudo lspci -vvnn
    * sudo lspci -vvnn > lspci.txt
 * Output of sudo dmidecode
    * sudo dmidecode > dmidecode.txt
 * Try to suspend/hibernate and then restart the system and attach /var/log/kern.log and /var/log/kern.log.0
 * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
    * cp -r /proc/acpi /tmp
    * tar -cvjf ~/acpi.tar.bz /tmp/acpi
    * attach acpi.tar.bz from your home directory
 * Are you running Ubuntu/Kubuntu/Xubuntu?

Changed in linux:
assignee: nobody → chrisccoulson
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Ante Karamatić (ivoks) wrote :

I can't reproduce this bug anymore. In the meantime I did an upgrade and bug became worse. Fn+F3 doesn't work at all any more. This is related to bug 261318 - almost total loss of functionality on toshiba laptops.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks for the feedback. As the original suspend issue is now resolved, I'm going to close this bug report.

For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux:
assignee: chrisccoulson → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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