Comment 122 for bug 417842

I did not intend to offend. In fact I would like all bugs to be fixed. While attempting to give each unique issue a chance to not be buried in another bug. Even if you report it and it some gets labeled a dupe, or mislabeled. You can exert that it is not. I just believe it is advantageous to make each unique bug in it's own report. That way others who get the same issue can work together and get a fix for the specific issue. I would honestly hate to see anyone be lost in the crowd of one bug and hope someone sees it and gets a fix out.

I am not all that happy with how the bug reposting works right now. I get time outs a lot, plus get mail for bugs I have no reason for getting.

To add past what Timothy mentioned. If you are getting the KernelOOPS and it prompts Apport. When you see the final part, just make a comment of the issue and it is not a dupe of this bug. I do see it is not this bug. But it may appear to be. I was having strange issues after the OOPS, it is gone now. After I received the fix. I make sure the repo I am pulling from is also up to date. If after you receive it. It is pretty much not this same issue. Not saying your not having an issue.

After receiving the fix. My machine does not have any odd behavior related to resuming. I can only hope others experience it working for them.

"I do not believe that Michael meant any offense, it's just that at times things get in the wrong place, and need to get sorted out.

1: I've had the same issue. We could try sending Launchpad a suggestion, or as a workaround, try copying and pasting into another window to have the system report available as a reference.

2: Go to System > Administration > Update Manager. Check and Install Updates (your password will probably be required). I like to keep the Pre-released updates (karmic-proposed) box checked under "Settings" to get the updates sooner. I also check for updates Daily.

Thank you for your work to help make Ubuntu better.

Timothy Wilson"