Hi there,
K3B woes again, this time on Rocky Linux 8. Permissions are OK now, only this time K3B can’t seem to find my optical drive. When I start it up, I have a warning message about a missing optical drive.
Curiously enough, both of these commands work in a terminal:
$ eject
And then:
$ eject -t
On a side note, I’ve been using K3B since the days of Slackware 7.1, and as far as I can remember, every single release of this piece of software had to be potty-trained for the last 25 years. 
Any suggestions ?
Probably you need to check the settings and find out what device it’s pointing to, like /dev/cdrom, /dev/sr0 or whatever. Find out what the CD device is known as under /dev and then configure K3B accordingly to use it.
root@rocky9:~# ls -lha /dev | grep cd
lrwxrwxrwx. 1 root root 3 May 2 11:52 cdrom -> sr0
crw-rw----. 1 root cdrom 21, 1 May 2 11:52 sg1
brw-rw----. 1 root cdrom 11, 0 May 2 11:52 sr0
and for Rocky 8:
[root@rocky8 ~]# ls -lha /dev | grep cd
lrwxrwxrwx. 1 root root 3 May 2 11:52 cdrom -> sr0
crw-rw----. 1 root cdrom 21, 1 May 2 11:52 sg1
brw-rw----. 1 root cdrom 11, 0 May 2 11:52 sr0
results may vary depending on what devices installed.
Here’s what I have on my box running Rocky Linux 8:
# ls -lha /dev/ | grep cd
lrwxrwxrwx. 1 root root 3 May 20 09:07 cdrom -> sr0
crw-rw----+ 1 root cdrom 21, 1 May 20 09:07 sg1
brw-rw----+ 1 root cdrom 11, 0 May 20 09:07 sr0
When I launch K3B I simply get a “No optical drive found” error message. And there seems to be no way to explain to K3B that I do have an optical drive.
On a side note: K3B works perfectly on that same sandbox PC under Rocky Linux 9. It’s just that some of my clients (at the local school for example) still run Rocky Linux 8 due to some legacy software compatibility reasons, so I’d like to solve that problem.
OK, found the culprit.
The udisks2 package was missing under the hood. As soon as I installed it, K3B worked perfectly.
Now go figure why such a fundamental piece of software hasn’t been pulled in automatically.
I started with a minimal installation, added some command-line tools, then X11, then KDE from EPEL.
Cheers,
Niki
1 Like
It seems that “Minimal install” of (AlmaLinux) 9 on EFI system pulls the udisks2, but on legacy system does not. (Yet, I have one EFI system, where udisks2 was not in transaction 1. Perhaps 9.0 installer/packages had different pull list – quite possibly continuation from el8.)
Gnome wants gvfs, which wants udisks2. KDE has no such needs?
This is probably due to the fact that even though I’m running KDE, I’ve replaced SDDM (buggy with NVidia drivers) with GDM. Hence some GNOME voodoo under the hood.