On Fri, Nov 14, 2025 at 2:28 PM D. R. Evans <[email protected]> wrote: > I find a solution that worked at: > > https://askubuntu.com/questions/1032903/problem-with-k3b-in-18-04-releases-cdrecord-has-no-permission-to-open-the-devi > > The actual solution: > sudo chmod 4711 /usr/bin/wodim; sudo chmod 4711 /usr/bin/cdrdao
That's an incredibly bad idea. Setting programs to be SUID and/or SGID when they weren't intended to be set and run so, typically opens up major security vulnerabilities. Yeah, don't follow random crud advice you find on the Interwebs. Heck, very first security vulnerability I ever found and reported was when a particular *nix provider made exactly that mistake, and in so doing, opened up a significant security hole.
