** Description changed:

+ If a resume hangs late enough in the resume cycle then the resume may
+ appear to the user in front of the machine to have completed
+ successfully.  Their screen saver may appear, they can login and use the
+ machine quite normally.  However the suspend really is not complete and
+ really is broken.  Any attempt to suspend again will apparently do
+ nothing (other than perhaps lock the screen).  When the user next
+ reboots the suspend will be detected as failed and reported.  Although
+ accurate this is likely to make the reporting user think it is a false
+ report.
+ 
+ We really need to detect the difference and report it differently to
+ prevent it being confusing.  It also provides us with a good opportunity
+ to record more information as the machine is likely functional.  This
+ implies that the original report which I am hijacking here likely is
+ showing a real failure.  But we are unlikely to figure out what from
+ this report as the information is long gone by the time the user sees
+ the problem.
+ 
+ ===
+ 
  I think this is actually a false positive, but I'm reporting it as I
  think that would indicate a bug as well.  This report was created on a
  fresh boot after a successful shutdown:
  
  -rw------- 1 root root 520082 2009-02-27 08:13
  /var/crash/susres.2009-02-27_08:08:59.566718.crash
  
  I don't think there was any failure in this case.
  
  ProblemType: KernelOops
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InterpreterPath: /usr/bin/python2.5
  MachineType: LENOVO 6465CTO
  Package: linux-image-2.6.28-8-generic 2.6.28-8.26
  ProcAttrCurrent: unconfined
  ProcCmdLine: User Name=UUID=305dde78-d20a-4248-aaf4-09447b7c5791 ro quiet 
splash
  ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
  ProcEnviron: PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
  SourcePackage: linux
  Tags: resume suspend
  Title: [LENOVO 6465CTO] suspend/resume failure
  UserGroups:

-- 
resume hangs late in the process appear working and yet report failure on next 
reboot
https://bugs.launchpad.net/bugs/335323
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to