It seems instead that the bug is fixed by upgrading cdrdao to the latest version (1.2.3), which is already 6+ months old.
It seems instead that the bug is fixed by upgrading cdrdao to the latest version (1.2.3), which is already 6+ months old.