https://bugs.kde.org/show_bug.cgi?id=382754

--- Comment #11 from Leslie Zhai <lesliez...@llvm.org.cn> ---
(In reply to Leslie Zhai from comment #10)
> (In reply to Wolfgang Bauer from comment #9)
> > (In reply to Leslie Zhai from comment #6)
> > > but just show the problem messages if the user choose other utilities
> > > and libraries which not maintained any more and deprecated.
> > 
> > But cdrecord is maintained and not deprecated.
> > 
> > Maybe the message should be reworded to state that cdrskin is *optional*,
> > and k3b will use it in place of cdrecord *if it is installed*. I.e. make it
> > clear that burning will still be possible without cdrskin installed.
> > 
> > One thing though: I tried to install cdrskin here. This removed the message
> > on startup, but k3b (17.04.3) still seems to use cdrecord according to its
> > output.
> > Uninstalling cdrecord gave an error message on startup that it is missing
> > and broke burning completely even with cdrskin installed (and it is detected
> > in the settings dialog).
> > 
> > So apparently cdrskin is not even used currently for some reason?
> 
> BUG 137436
> 
> but Cristian Aravena Romero helped us to test cdrskin see BUG 380067
> 
> and of course I can enable cdrskin as default writter to take place of
> cdrecord, or even totally disable it.

disable cdrecord, but if the user prefer to use it, please though command line,
not k3b, thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to