Hi Slaven, I apologize for taking so long to answer you.
I've been thinking about this bug for a while and I think you're right in saying that K3b should work out of the box. So what I am thinkin of doing is removing k3bsetup from the Debian package and replacing the cdrecord warning with a "do a dpkg-reconfigure cdrecord and set it as SUID if you are having problems" message (some people report success with a non-SUID cdrecord). Afterall, that's the proper fix on Debian. I feel like k3bsetup makes perfect sense in the upstream package since K3b is designed to work on all systems and this tool helps solve that problem. However, on a specific distro, it shouldn't be necessary and should be replaced by a more specialized mechanism. What are your thoughts on that? Francois -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
