On Tuesday 27 April 2010 04:55:44 you wrote: > Hi lelamal, > > This bug was reported a while ago and there hasn't been any activity in it > recently. Hi, "merely" two months, but this is basically because, although I made myself available to add any more details about the problem, the problem was completely ignored up to the next important release, probably hoping that would solve the issue (as it happens with many unsolved bugs, unfortunately), although a serious kernel problem is involved. However, using the machine in a working environment, I can't afford losing data and wasting time after a broken release which contains several critical regressions. As a result, I first changed machine, from my previous laptop (see exchange at Bug 488673) to the present desktop, but the issue was still there (see also Bug 562987). Then, lately I uninstalled everything, reformatted, and fresh-installed another flavor (kubuntu), which finally guaranteed me unstopped, reliable work-flow. In addition, many users must have felt the same, and resorted to the same, or other solutions, and this, coupled with lack of serious response from developers in a timely fashion, would finally account for the lack of activity in this bug, recently.
> We were wondering if this is still an issue? Can you try with > the latest development release of Ubuntu? ISO CD images are available > from http://cdimage.ubuntu.com/releases/ . I am sorry, but both machines I use are now on kubuntu (currently, lucid), so I cannot try that now. This bug may even be set to "incomplete", but since it was filed under karmic, I can swear it was still very active till the point I had to switch machine, desktop manager, and release (RC). So, no one actively fixed it until RC came out. Besides, I do not see a clear point in testing (now!) a development release when all I needed was (back then!) the OS to work in a stable environment and with a stable release. This is a rather convoluted way to fix things, and to those who insist that ubuntu is different from Windows in that you can actually report bugs and have them fixed before a new release comes out I would like to point out that it's not entirely true, and I could verify that numerous times. > If it remains an issue, could you run the following command from a Terminal > (Applications->Accessories->Terminal). It will automatically gather and > attach updated debug information to this report. > > apport-collect -p linux 526369 Sorry, I could not, for I am not running that flavor (and will not anytime soon) and machine anymore. > Also, if you could test the latest upstream kernel available that would be > great. It will allow additional upstream developers to examine the issue. > Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've > tested the upstream kernel, please remove the 'needs-upstream-testing' > tag. This can be done by clicking on the yellow pencil icon next to the > tag located at the bottom of the bug description and deleting the > 'needs-upstream-testing' text. Please let us know your results. For the same reasons already discussed, unfortunately I cannot test my machines with the latest upstream kernel available, because I need a stable working environment, and all my contributions to the ubuntu project may be limited to reporting bugs and to a few translations. So, I was pretty much waiting for developers to look into the issue, and update you on that. Lack of activity on both sides left the bug to stall, and me to pursue stability elsewhere. Just a final, personal thought: chasing change "just for the hell of it", trying "to be different" at all costs at every new release, and releasing twice a year an unstable OS may not the best way forward, if Canonical is seriously considering to fix Bug 1. To me, is more important to have old bugs fixed and no regressions when I upgrade to new versions, rather than having a shiny new piece of OS half-baked twice a year just in time for its schedule just because it had to be released regardless. You can keep pushing dirt under the carpet, but sooner or later someone has to clean underneath. Thanks in advance. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] -- [ASUSTeK Computer Inc. P4P800] hibernate/resume failure https://bugs.launchpad.net/bugs/526369 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
