Hi Giuseppe, I'm setting the title back here, as it's not helpful to mix
different hardware models in the same report. (That's why this one was
started in the first place.)
Opening a kernel bug for this would have no effect, though--it would
just be closed as Won't Fix. It's not a high enough
Also, there's an immediate second suspend when I suspend via means other
than the lid and then close the lid. The problem is likely that the lid
is reported on wakeup as being closed, and upower or whichever part of
the stack is responsible for suspending thinks that the lid was closed
again.
--
