Ok, as this seems the original bug report: Until this is fixed, I am thinking about using a new kernel, but
a) which problems could this cause - there must be a reason that kernels are never replaced during a release cycle b) how would I do this - apt-get typically hangs after a few packages are downloaded, and the file system quickly gets read-only. could I install the new kernel to intrepid and then dist-upgrade to jaunty? how is the correct procedure c)If this bug was known march 20, and confirmed some days before the release, why is there not even at least some remark in the release notes ? -- jaunty kernel 2.6.28-11 kernel update renders the system un-usable. https://bugs.launchpad.net/bugs/346691 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
