Activity log for bug #64439

Date Who What changed Old value New value Message
2006-10-06 21:47:01 LarryGrover bug added bug
2006-10-13 12:22:23 LarryGrover linux-source-2.6.17: statusexplanation I originally filed this bug against the kernel because I thought it was a problem with hibernation or recovery from hibernation, but I have had the chance to observe this bug several more times and I think this may not be a kernel bug after all. When my laptop get "stuck" resuming (blank screen with cursor only) I am able to ssh in to the machine. When I do this I consistently see that these processes are running: gdmopen, sh and whiptail. Running strace against the gdmopen processes revealed it was hung at: waitpid(11654, the processes with pid # 11654 was whiptail, running strace against whiptail revealed: select(1, [0], [], [], NULL Whiptail is apparently some type of dialog display program, and it seems that it may be stuck waiting for input. However, at the time that the gdmopen, sh and whiptail processes are running the screen is totally blank and dark except for an X cursor which is sometimes in a normal state (arrow) and sometimes in a busy state (timer). The system does not respond to keyboard input at this point (one of the reasons I originally thought this was a kernel bug).
2006-10-17 19:22:23 towsonu2003 None: statusexplanation I originally filed this bug against the kernel because I thought it was a problem with hibernation or recovery from hibernation, but I have had the chance to observe this bug several more times and I think this may not be a kernel bug after all. When my laptop get "stuck" resuming (blank screen with cursor only) I am able to ssh in to the machine. When I do this I consistently see that these processes are running: gdmopen, sh and whiptail. Running strace against the gdmopen processes revealed it was hung at: waitpid(11654, the processes with pid # 11654 was whiptail, running strace against whiptail revealed: select(1, [0], [], [], NULL Whiptail is apparently some type of dialog display program, and it seems that it may be stuck waiting for input. However, at the time that the gdmopen, sh and whiptail processes are running the screen is totally blank and dark except for an X cursor which is sometimes in a normal state (arrow) and sometimes in a busy state (timer). The system does not respond to keyboard input at this point (one of the reasons I originally thought this was a kernel bug).
2006-10-18 00:14:14 Paul Sladen marked as duplicate 56365
2006-10-23 20:04:41 Nicolas DERIVE acpi-support: status Unconfirmed Fix Released
2006-10-23 20:04:41 Nicolas DERIVE acpi-support: statusexplanation As the reporter said it is fixed now, marked as "fix released". Thanks Larry for your information about the bug status on your computer.