Lenovo Thinkpad Twist: Suspend does not work

This problem only occurs in XMir mode, when deactivating XMir as described in the section "Removing unity-system-compositor", subsection "temporarily", suspend works.

Status changed to 'Confirmed' because the bug affects multiple users.

After doing the tests I got asked for in bug 1213239, suspend started to work correctly with all kernels, especially with the newest ones of Saucy (3.11.0-3-generic and 3.11.0-2-generic). So with the current, fully up-to-date Saucy suspend works.

This bug report is being closed due to your last comment.

I had the same problem, with Lenovo Thinkpad Twist and Saucy Salamander. It's kind of intermittent, I'm now trying to understand whether "echo LID0 | sudo tee /proc/acpi/wakeup" solves the problem.

The problem happens after every reboot. The computer would go in standby mode only once. Doing

echo EHC1 | sudo tee /proc/acpi/wakeup

solves this.

I reopened the bug (I hope I did it right). The bug is still present on the released Saucy, and I fixed it on my laptop by adding

if grep -q "EHC1.*enabled" /proc/acpi/wakeup then
 echo EHC1 > /proc/acpi/wakeup
fi

to /etc/rc.local.

The problem happens when I'm not running Mir, but rather a default Saucy installation. I guess this bug should be moved to a different package.

Just a minor note: missing semicolon in the above snippet. The correct snippet is

if grep -q "EHC1.*enabled" /proc/acpi/wakeup; then
 echo EHC1 > /proc/acpi/wakeup
fi

Hi, just to note: this is not just Saucy, not just Unity. I am running 12.04.3 with the backport of kernel 3.11 from Saucy, and I am using KDE. I *still* get the same issue and the same fix from Matteo works for me!

Status changed to 'Confirmed' because the bug affects multiple users.

As per https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1213233/comments/4 .

I don't know why you marked this invalid, Christopher. This is definitely affecting me still on kernel 3.11.0-11. There was no indication of a fix.

Aaron Wolf, thank you for your comment. I marked this Invalid as per the original reporter's comments that this is resolved for him. Given this, the fact you are not the original reporter, this is not your bug, and this report is not tracking your problem, this report is closed.

Despite this, if you have a bug in Ubuntu, please feel free to file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs