Thats truly strange. Apport picked up a failed suspend. There really
was a suspend _marked_ as in progress on this machine when this apport
script was run. We can tell this because of the entry below which is
simply the contents of the flag file. As to why that file would ever
exist if there
** Tags added: false-report
--
kernel bug reported by apport - no obvious crash or undesired activity.
https://bugs.launchpad.net/bugs/321556
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Heh, then I'd definitely consider this an issue with the apport bug
reporting functionality. I'll notify the kernel team. Thanks.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Triaged
--
kernel bug reported by apport - no obvious crash or
Never done any suspend/resuming actually, it's a desktop machine. I can
certainly try. Do you want suspend-to-ram, suspend-to-disk or both?
On 27 Jan 2009, 1:55 AM, Leann Ogasawara leann.ogasaw...@canonical.com
wrote:
Thanks gnudoc.
So it's safe to assume you haven't had any suspend/resume or
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/21651532/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/21651533/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/21651535/Dependencies.txt
**
Thanks gnudoc.
So it's safe to assume you haven't had any suspend/resume or hibernate
issues? Some hooks were added to apport to try to automatically detect
suspend/resume issues and it's likely incorrectly detecting an error and
filing a false bug report. Thanks.
** Changed in: linux (Ubuntu)
