K3B + -current permission problems...

arfon · 07-14-2021, 01:30 PM

What am I missing here?-

I've loaded several machines recently with -current (64 & 32bit) and none have the K3B permissions set correctly by default. When I go into k3b configuration and use the 'let k3b set the permissions' option, it says that it fixed the issue but, it doesn't. The permission issue persists even over reboots.

I can manually set the permissions and it works but, this issue seems to be new.

gauchao · 07-15-2021, 03:50 PM

Have you previously done the following, as root, and included the user in the cdrom group?

Quote:

#chown root:cdrom /usr/bin/cdrecord /usr/bin/cdrdao
#chmod 4750 /usr/bin/cdrecord /usr/bin/cdrdao

FTIO · 07-15-2021, 06:57 PM

Every new version of Slackware (and the few other distro's I used before Slackware), *ALL* made me mess with the permissions in the settings at first use of K3b. Always. It was only a PITA because it was of course the once, and I could then use k3b as 'user'. I just learned to not think much about it and accept it as it is since it really is just a one time thing at the first-use of it.

arfon · 07-18-2021, 12:57 AM

"Have you previously done the following, as root, and included the user in the cdrom group?"

Yes, manually updating the groups makes it work.

On previous versions of K3B/Slackware the K3B setup tool worked to do that. Just wondering why it's broken now.

3rensho · 07-18-2021, 01:27 AM

I have never gotten the K3B tool to set the permissions correctly. I always have had to do it manually when there was a problem.

Aerwyk · 09-23-2022, 01:16 PM

Quote:
#chown root:cdrom /usr/bin/cdrecord /usr/bin/cdrdao
#chmod 4750 /usr/bin/cdrecord /usr/bin/cdrdao

Now the system does not recognize the drive.
I'm running KDE on Fedora FC35 latest update

And you say ???????

Thanks,

Aerwyk

gauchao · 09-23-2022, 05:35 PM

Quote:

And you say ???????

I can't say anything about it since I don't run Fedora. Under Slackware, the solution is presented above.

Good luck.