K3B checks if cdrecord and cdrdao are run with root privileges. If this is not the case K3B offers to run K3Bsetup (need to enter root password). K3Bsetup chmods /usr/bin/cdrdao and /usr/bin/cdrecord to 4711. Considering cdrtools and/or cdrdao are frequently bumped the users have to run K3Bsetup everytime after this. I assume that not everybody would like these binaries to be suid out of the box so I suggest te make a useflag for this. Thank you very much in advance for the support. cdrecord will be run without root privileges It is highly recommended to configure cdrecord to run with root privileges. Only then cdrecord runs with high priority which increases the overall stability of the burning process. Apart from that it allows changing the size of the used burning buffer. A lot of user problems could be solved this way. This is also true when using SuSE's resmgr. Solution: Use K3bSetup to solve this problem. cdrdao will be run without root privileges It is highly recommended to configure cdrdao to run with root privileges to increase the overall stability of the burning process. Solution: Use K3bSetup to solve this problem. Reproducible: Always Steps to Reproduce:
*** This bug has been marked as a duplicate of bug 163457 ***
(In reply to comment #1) > *** This bug has been marked as a duplicate of bug 163457 *** Hi Jakub, I'm sorry for the duplicate, I have really searched but could't the bug, hmmm strange. Anyway, there is a difference between what the K3B developers think what is the best situation and what you think is the best situation. The result for the users is that they are constanly annoyed with running k3bsetup. I really have no idea what the best situation is. I value both you insights. Is it really a problem to add an _optional_ possibility to provide a system that the K3B-developers think is best? Is it possible to ask for a third opinion by for example assigning the bug to the maintainers? Maybe they can tell us if they agree with you or the K3B-developers. Thanks!
Well, as said, I've been using k3b w/ cdrtools (no setuid) for ages, no problem whatsoever. If you are just complaining about the pointless warning, should be probably taken upstream. You can disable it just fine in Settings - Configure K3b - Misc - Check system configuration and it will never ask again.
