MBP still sleeping after 2.0.2 installed

Bug #501083 reported by wfaulk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
InsomniaT
Won't Fix
Undecided
Unassigned

Bug Description

As requested, I'm opening a new bug. I don't see anything in kernel.log that would indicate why it went to sleep, but I've attached it as also requested.

The laptop went to sleep at 06:42, and wasn't touched again until 13:05. It apparently woke up and went back to sleep a few times during that period.

Revision history for this message
wfaulk (wfaulk) wrote :

The logs probably weren't enabled, since I was using the broken version of 2.0.2. I'll wait for it to happen again.

Changed in insomniat:
status: New → Invalid
Revision history for this message
wfaulk (wfaulk) wrote :

Okay, it happened again, this time with the logs enabled. I'm not as sure what time it went to sleep this time, beyond sometime between 2PM on Jan 2 and 2AM on Jan 3. I'm attaching the log.

Changed in insomniat:
status: Invalid → New
Revision history for this message
Archimedes Trajano (trajano) wrote :

Around this time in the logs.

Jan 3 13:33:51 mass kernel[0]: InsomniaT: sleep is disabled by system
Jan 3 13:56:01 mass kernel[0]: InsomniaT: handleSleepWakeInterest invoked with message type e0034130.
Jan 3 13:56:31: --- last message repeated 51 times ---
Jan 3 13:56:31 mass kernel[0]: InsomniaT: handleSleepWakeInterest invoked with message type e0034130.
Jan 3 13:57:01: --- last message repeated 49 times ---

it looks like you opened and closed the lid over a hundred times in a minute. That's what's probably confusing the tool. However, it does not really narrow down the root cause.

Changed in insomniat:
status: New → In Progress
Revision history for this message
wfaulk (wfaulk) wrote :

Wow. To be probably unnecessarily obvious, I don't open and close the lid twice a second for extended periods of time. ;)

I wonder if my sensor is broken.

Revision history for this message
Archimedes Trajano (trajano) wrote :

Created a new release. Not much has changed in the core code, but the UI has been updated see if it helps. But it sounds like a hardware issue unless someone else can confirm that it happens on their machine.

Revision history for this message
Archimedes Trajano (trajano) wrote :

Closing due to inactivity

Changed in insomniat:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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