On 2008-09-01 23:15, Leann Ogasawara wrote : > Hi Andre, > > Would you be willing to confirm if this issue will exist with the > upcoming Intrepid Ibex 8.10 release? The Ubuntu Kernel Team is planning > to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 > release. As a result, the kernel team would appreciate it if you could > please test this newer 2.6.27 Ubuntu kernel. You should be able to test > using the upcoming Alpha5 release for Intrepid Ibex 8.10 will contain > this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday > Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be > announced. You should then be able to test via a LiveCD. > > Please let us know immediately if this newer 2.6.27 kernel resolves the > bug reported here or if the issue remains. More importantly, please open > a new bug report for each new bug/regression introduced by the 2.6.27 > kernel and tag the bug report with 'linux-2.6.27'. Thanks again, we > really appreicate your help and feedback. > Thanks for your fast reply. Nice to cooperate. I plan to stay with 8.04 LTS because I support people using it without Internet access. I have too little time to install 8.10 right now, I'll probably make a partition in the future. But testing with a live CD is all-right. In hope to see the problem solved in 8.04, though, not only 8.10.
I would like to do those tests and I'll try, but : 1) As I don't know how the conditions that produce these errors arise and as the chances are that they will disappear when I reboot, I fear that the test you ask is impossible to do. 2) I always wondered how Ubuntu improves if every move I see is testing if perchance "someone else" would have caused a correction. That's a lot of time spent for nothing. I would have appreciated to, for example, receive an USB diagnostic program to run when the conditions arise. Then we would have more chances than with burning holy candles to have a clear answer where the problem is. And then to be sure that either the correction is already on the way or to be started, instead of waiting forever to see it come by pure luck, like the Suspend problem I have had for more than one year. In short, I'd prefer to be "someone else" :-) Best regards, André. -- usb device invisible until lsusb command issued https://bugs.launchpad.net/bugs/263139 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
