Mailinglist Archive: opensuse-bugs (4794 mails)

< Previous Next >
[Bug 1050715] K3b complains about missing cdrskin at start up
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 26 Jul 2017 15:21:37 +0000
  • Message-id: <bug-1050715-21960-28mILJXEok@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1050715
http://bugzilla.opensuse.org/show_bug.cgi?id=1050715#c6

--- Comment #6 from Frank Kruger <fkrueger@xxxxxxxxxxx> ---
(In reply to Wolfgang Bauer from comment #5)
(In reply to Frank Kruger from comment #3)
(In reply to Frank Kruger from comment #2)
(In reply to Dave Plater from comment #0)
See https://bugs.kde.org/show_bug.cgi?id=382754
On start up k3b gives this message:
Unable to find cdrskin executable
K3b uses cdrskin in place of cdrecord.
Solution: Install the libburn package which contains cdrskin
Forcing unsuspecting users to use a development alternative to cdrecord
which works fine for years.

I can confirm your observation. However, libburn4-1.4.4-3.1.x86_64 is
installed.

The above "Solution: Install the libburn package which contains cdrskin" is
at least misleading, since it does not work for me. I had to install the
package cdrskin, which solves the issue.

Yes, k3b actually uses the cdrskin executable which is in the package
cdrskin in openSUSE.

But the main question IMHO is, should we make k3b require cdrskin (which
would remove that message, but make it impossible to use cdrecord instead),
or rather stick to cdrecord.

cdrskin is a limited cdrecord compatibility wrapper, so I would stick to
cdrecord. Is there any good reason against it?

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >