tmp for 2.6.27-3-generic is 99% full but that's still 1 G left. That should have been pretty sufficient. And the upgrade should have stopped before it fails.
But that's *not* the problem I am reporting here. When I booted 2.6.27-4-generic (notice the 4, not the 3), /tmp had a new entry in df -k output (that doesn't show up here, as this is the output I got from 2.6.27-3... when I reported the bug). And unfortunately I don't have an explanation for this new entry. It looked like this ????? 1024 1024 0 /tmp Because of it, no package installation requiring /tmp worked. That borked my kernel 2.6.27-4-generic upgrade. It couldn't boot at all after the tentative installation (fatal error during the first seconds of the boot). I know I probably don't give enough information for this bug to be fixed, but if I find more, I will add to it. -- package linux-image-2.6.27-4-generic 2.6.27-4.6 [modified: lib/modules/2.6.27-4-generic/modules.pcimap lib/modules/2.6.27-4-generic/modules.dep lib/modules/2.6.27-4-generic/modules.ieee1394map lib/modules/2.6.27-4-generic/modules.usbmap lib/modules/2.6.27-4-generic/modules.isapnpmap lib/modules/2.6.27-4-generic/modules.seriomap lib/modules/2.6.27-4-generic/modules.alias lib/modules/2.6.27-4-generic/modules.symbols] failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/273889 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
