K3B vs. permissions problem

Rocky Linux Help & Support
21

OK, so I’ve downloaded and installed xorriso. Now what? k3b still complains it can’t find cdrecord. how do I make this work? (clearly not out of the box.)

Fred

22

Use alternatives to adjust the symlinks. Usually you first run alternatives --list to figure out the toolname (left side of the list), then alternatives --config <toolname> to do the actual change.

23

As @felfert says:

root@rocky9:~# alternatives --config cdrecord

There are 2 programs which provide 'cdrecord'.

  Selection    Command
-----------------------------------------------
*+ 1           /usr/bin/cdrskin
   2           /usr/bin/xorrecord

Enter to keep the current selection[+], or type selection number:

then choose the one you want to use by selecting with the number.

24

Thanks for the instructions!

Unfortunately,…
K3b still says it can’t find cdrecord. The system shouldn’t need a reboot for this, should it? (after all, this ain’t Windoze! :nerd_face: )

here’s what alternatives --config cdrecord looks like:

$ sudo alternatives --config cdrecord

There are 2 programs which provide 'cdrecord'.

  Selection    Command
-----------------------------------------------
*  1           /usr/bin/cdrskin
 + 2           /usr/bin/xorrecord

Enter to keep the current selection[+], or type selection number:

and /var/lib/alternatives/cdrecord:

manual
/usr/bin/cdrecord
cdrecord-wodim
/usr/bin/wodim
cdrecord-cdrecordman
/usr/share/man/man1/cdrecord.1.gz
cdrecord-wodimman
/usr/share/man/man1/wodim.1.gz

/usr/bin/cdrskin
60
/usr/bin/cdrskin
/usr/share/man/man1/cdrskin.1.gz
/usr/share/man/man1/cdrskin.1.gz
/usr/bin/xorrecord
50
/usr/bin/xorrecord
/usr/share/man/man1/xorrecord.1.gz
/usr/share/man/man1/xorrecord.1.gz

25

I can see a small difference on my system; the first line in your file says “manual”, but on my system it says “auto”.

26

That’s because he’s changed it to use the xorriso provided one as he has two to choose from. Otherwise, it would have said auto as well. But that’s not the cause of the permission problem.

27

still getting the failure to find cdrecord, but the symlinks have changed:

$ which cdrecord
/usr/bin/cdrecord

$ ls -l /usr/bin/cdrecord
lrwxrwxrwx. 1 root root 26 Apr 27 19:29 /usr/bin/cdrecord → /etc/alternatives/cdrecord

$ ls -l /etc/alternatives/cdrecord
lrwxrwxrwx. 1 root root 18 Apr 29 10:07 /etc/alternatives/cdrecord → /usr/bin/xorrecord

so, the chain of links for cdrecord now points to xorrecord. which one would expect to now WORK, if in fact xorrecord actually does act like cdrecord.

I’m stumped! :grimacing:

Fred

28

curious, why did you use xorriso? did you also have trouble with cdrecord that was fixed by using xorriso?

Fred

29

Yes, higher up in this post, @stevemowbray said K3B was working on his system using xorriso; I thought it might make a difference.

30

yeah, me too. I’d like to know why he used xorrisso given that it is not the default… did cdrecord not work for him?

Fred

31

I think I’d already installed xorriso for some reason before k3b, and had no reason to change it.

32

To @fredex and @stevemowbray

In the tests above, can you confirm that you are both using the same “project type” within K3B. Different project types should give different errors.

33

Tests? what tests above?

34

any project type fails for me.

35

Hey guys,

Here’s the definitive guide on how to make K3B work on Rocky Linux 8.x and 9.x.

  • Install k3b.
  • Install cdrskin and wodim.
  • Set permissions for cdrdao, wodim and growisofs according to K3B’s Permissions tab.
  • Add your non-root user to the cdrom system group.

Here’s what this looks like in my Ansible playbook (ignore the extra stuff) :

---  # tasks/main.yml

- name: Applications > DVD/RW
  ansible.builtin.dnf:
    name:
      - asunder
      - cdrskin
      - k3b
      - normalize
      - wodim
    state: present
    install_weak_deps: false

- name: Install HandBrake
  community.general.flatpak:
    name: fr.handbrake.ghb
    state: present

- name: Fix permissions for cdrdao and wodim
  ansible.builtin.file:
    path: "{{item}}"
    owner: root
    group: cdrom
    mode: '4710'
  with_items:
    - /usr/bin/cdrdao
    - /usr/bin/wodim

- name: Fix permissions for growisofs
  ansible.builtin.file:
    path: /usr/bin/growisofs
    owner: root
    group: cdrom
    mode: '0750'

- name: "Add user {{firstuser_login}} to cdrom system group"
  ansible.builtin.user:
    name: "{{firstuser_login}}"
    groups: cdrom
    append: true

...

Cheers,

Niki

36

Niki, thanks for the detailed information. I hadn’t look here in a while, but was pleased to see it.

at first k3b still didn’t work so I rechecked my changes. I’m sure I restarted k3b more than once, but finally the last time it allowed me to write an ISO image to a CD!

Whooooooo! Hoooo!!

So it looks as if it is working. thank you!

I’ll repost if other problems occur.

Fred

PS:
should the dev team be aware of these issues so they can adjust the installation so it’ll work in the future?

Fred

37

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.