The bug report looks like it has been done against a cdrecord version from 2004. No real cdrecord output has been attached, do it cannot be even called a confirmed bug.
Please test again with the new original cdrecord package from gutsy/multiverse If the problem goes away, this was a problem that has been fixed in cdrecord.. If the problem goes away with cdrecord ts=30k, this is a Linux kernel bug as noted before. If there is no report within some time from a recent cdrecord, I propose to close this bug -- cdrecord hangs with kernel >= 2.6.10 and cyberdrive cdrw https://bugs.launchpad.net/bugs/28210 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
