[macbook 8,2] Closing lid doesn't suspend

[Alan Ott]

Closing the lid of my Macbook 8,2 does not cause it to go into suspend in 12.04 beta 1 of Xubuntu. However, if I select "Suspend" from the "log out" menu, it will properly go into suspend.

I expect the system to go into suspend when I close the lid.

This is the AMD64 version.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 945248

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Alan Ott (alan-signal11)]

I tried running apport-collect 945248. It didn't appear to work. Here is the stdout log:

alan@ato-lappy:~$ apport-collect 945248

Gtk-WARNING **: Theme parsing error: misc.css:13:17: Not using units is deprecated. Assuming 'px'.

Gtk-WARNING **: Theme parsing error: misc.css:15:16: Not using units is deprecated. Assuming 'px'.

Gtk-WARNING **: Theme parsing error: misc.css:16:11: Not using units is deprecated. Assuming 'px'.
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=bVfl3p5H8TjvM8zQtHSv&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...
Waiting to hear from Launchpad about your decision...
No packages found matching linux.
ERROR: KeyError('ProblemType',)
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called

Gdk-WARNING **: apport-gtk: Fatal IO error 0 (Success) on X server :0.0.

If I try running it again, I eventually get a non-refreshing window that says "invalid problem report" in its title, and the CPU shoots up to 200% for several minutes until I kill apport-gtk.

I'm happy to manually attach any logs. I will attach syslog. Are there any other logs which would be of interest?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc6 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc6'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc6-precise/

[Alan Ott (alan-signal11)]

Not a problem. I'll let you know.

[Alan Ott (alan-signal11)]

I built and booted with 3.3.0-rc6+ (revision 4f262acfde22b63498b5e4f165) from git using the existing Ubuntu /boot/config-3.2.0-17-generic (via make oldconfig) and I still have the same problem.

[Alan Ott (alan-signal11)]

Ok, so I realized I didn't read the directions very well.....

I have since also tried the kernel in http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc6-precise/ and the result is the same.

To be clear, I tried both the latest kernel from kernel.org and the kernel from kernel.ubuntu.com (listed above) with the same results.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Bruno Beaufils (beaufils)]

Affects me on Macbookpro6,2 with precise-beta1.

It is **very** annoying...

[Sergei Genchev (sgenchev)]

Affects me on Macbook pro 5.5.

 Is that a kernel driver that detects lid open and closed?

Lid is detected on my laptop:
 dmesg | grep Lid
[ 0.648725] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input0
[ 0.648748] ACPI: Lid Switch [LID0]

But then /proc/acpi/button/lid/LID0/state never changes it's state.

[Dražen Lučanin (kermit666)]

Affects me on a Macbook pro 8.2 in Ubuntu 12.10

[Aaron Fuleki (dendrochronology)]

Affects me on a MacBook2,1 in Ubuntu 12.10. Yes, I know it's older than dirt, but it still runs :-)

[penalvch (penalvch)]

Alan Ott, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Alan Ott (alan-signal11)]

This was fixed in some mainline kernel some time ago, but I don't remember which version.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]