John is on the right path here. I every reason to believe that everyone at Canonical is doing their job with passion, sincerity and competence. The issue is the process. A process exhibiting a pattern of failures (unstable major releases in this case) is a strong signal of an opportunity. And I hasten to say that I believe the majority of people on the Ubuntu team are already focused on that because they know that user experience matters (this is a very disconcerting bug even if harmless) and they know that finite manpower and triage are facts of life which do not absolve leaders of the consequences of decisions to release.
Defects describe us. How we react to defects defines us. ~M P.S. I don't believe this defect is rare or obscure. I have it on three quite varied x64 systems ranging in age from two months to two years. On 10/12/10, John Stewart <642...@bugs.launchpad.net> wrote: > Michael, > > Again, I'm totally sympathetic with what you're saying, but I don't > believe this case is comparable to the experience you have in your > organization. Here we don't have a minor bug that some bunch of free- > loaders are whinging about. In fact, as far as my own usage is > concerned, I could care less whether this gets fixed -- it's not yet > clear whether it affects the operation of the system, and in any case I > can just stick to LTS. The point is: how can it be that such monster > bugs make it into a final release? The real bug is the process, not > this particular exemplar. And yet one sees little effort on the part of > Canonical to alter the process to prevent this sort of thing. And thus > potential users turn away. That is the frustration. > > -- > Maverick could not load /lib/modules/2.6.35-22-generic/modules.dep > https://bugs.launchpad.net/bugs/642421 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: Confirmed > > Bug description: > When I turn on my computer I can read this on my screen > > "modprobe: Fatal: Could not load /lib/modules/2.6.35-22-generic/modules.dep: > no such file or directory" > > After 4-5 seconds, plymouth starts and the system works fine. > > salve, ho lo stesso problema, mi chiede la psw del portachiavi e poi rimane > con lo schermo nero..ed è impossibile lavorare...! grazie > > hi, I have the same problem, I asked the psw keychain and then left with a > black screen .. and it is impossible to work ...! thanks > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642421/+subscribe > -- Maverick could not load /lib/modules/2.6.35-22-generic/modules.dep https://bugs.launchpad.net/bugs/642421 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
