Upstream developers have already stated in comment 4 of the relative bug (https://bugzilla.gnome.org/show_bug.cgi?id=617222) that:
"it turns out that cdrdao 1.2.2 recognizes "cdrdao version" as an illegal command and since brasero expect a precise string for parsing version, and in the case of 1.2.2 it does not get it, it fails."
and that:
"The plugin associated with cdda2wav was designed to work with the cdda2wav coming from the cdrtools package. Up until now, it would refuse to work if it turned out cdda2wav was a symlink.... Now I turned off this mechanism just for cdda2wav plugin in next version which means that it should work with a symlink to icedax now".
So it seems that the kernel has nothing to do with this bug and we need updated versions of brasero and cdrdao to solve it.
Upstream developers have already stated in comment 4 of the relative bug (https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 617222) that:
"it turns out that cdrdao 1.2.2 recognizes "cdrdao version" as an illegal command and since brasero expect a precise string for parsing version, and in the case of 1.2.2 it does not get it, it fails."
and that:
"The plugin associated with cdda2wav was designed to work with the cdda2wav coming from the cdrtools package. Up until now, it would refuse to work if it turned out cdda2wav was a symlink.... Now I turned off this mechanism just for cdda2wav plugin in next version which means that it should work with a symlink to icedax now".
So it seems that the kernel has nothing to do with this bug and we need updated versions of brasero and cdrdao to solve it.