> > > I'm not sure if this problem
specifically concerns Trinity. I
> > > generally burn CDs and DVDs with k3b, and almost never use any other
> > > program.
> > >
> > > (I'm using the k3b-trinity packages.) I considered trying to use the
> > > non-Trinity version of k3b, or to boot into a KDE desktop instead of
> > > TDE, to see if that works. However, I also tried with Brasero, and
> > > had similar problems, so I'm guessing that the problem is not just
> > > with Trinity.
> > >
> > > No problem at all burning DVDs, including dual-layer. (I don't know
>> >
>> > about Blu-Ray, but I don't use them.) Whenever I try to burn CDs,
>> > however, k3b goes through the whole process, creating image,
>> > normalisation, etc., then crashes before it actually burns the CD.
>> >
> > > I ought to say that these are audio CDs. I've tried burning flac and
> > > wav files to CD, both with the same bad results. Also, a few weeks
> > > back, I tried to copy a large collection of mp3 files to a DVD as a
> > > data disc, but the program crashed before it could complete, and
> > > ruined the disc. I don't know if that incident could be related or
> > > not.
> > >
> > > It occurs to me to try to write a CD from the command-line, using
> > > growisofs or the like, but I've never done that before.
> > >
> > > I'm running Debian Jessie 8.8.0 and Trinity r14.04.
> > >
> > > Any help or observations would be appreciated.
> > >
> > > Bill
On Thu, Jun 7, 2018 at 7:59 PM, Kate Draven <borglabs4(a)gmail.com> wrote:
> 1. You
likely did this but just in case, just k3b's perms setup/
> 2. Check all related perms (dvdrecord, cdr* etc).
> 3. See if you can complete a burn as root (if you can, it's a perm
> problem) 4. Also try burning at half the adverted speed.
> Because of today's corner cutting standards, disks are not always
> adverted speeds.
>
> Let us know what happens and good luck,
>
> Kate
I tried everything on your list except burning as root. I try to avoid
that, but I suppose if I disconnect from the Internet, I can minimize any
risk.
Right now I am going through my permissions, to see if maybe I am not in
the burning group, etc. I looked at the help file, but there seem to be a
lot of instructions that refer to legacy items from the old KDE3 desktop,
so I need to find where it is in TDE.
Anyway, I've been using k3b since about 2006, never with any problems. Once
I had got it set up just right, in fact, I haven't changed anything in my
configuration since then ... until now. I have always just cloned all my
settings from one home folder to another, from one computer to another, and
kept running either KDE3 or TDE. Now I have some weird issues: like how k3b
refuses to use my preferred theme, and keeps reverting to the default after
every reboot (except that every once in a totally random while it *does*
use it, just to tease me, and then again reverts to default).
I never had to mess round with k3b, so now it's like I am a total n00bie
all over again. There used to be some configuration files kept in
/home/~/.kde/share/config/
(k3brc, etc), but I don't know if they affect the k3b-trinity package or
not. I've looked for the corresponding file in
/opt/trinity/share/config.kcfg/ (I think ...?)
but nothing seems to fit.
By the way, this kind of thing only happens to me whenever I starting
bragging on the virtues of GNU/Linux, or the TDE desktop, or something like
that. Then, when I want to show off what I can do, I immediately have
issues, and must excuse myself for a month or two, while I go into
seclusion to resolve my technical problems. I believe that there is some
kind of moral lesson here, but that I stubbornly keep trying to spread the
gospel of
enlightenment / liberation / free software to the ungrateful masses.
GNU/Linux is not really an operating system or type of software, but rather
a lifestyle, a secret cult, a mystical experience, reserved only to the
relatively pure of heart.
Bill
Okay, now this is new: In k3b settings, under external programs, both sox and
eMovix are listed as not found. I don't know about eMovix, as I can't find
any packages that mention it, but sox is definitely installed; yet k3b
persists in telling me that sox is not found.
And here's another disconcerting detail. When I click on search path (still in
k3b settings), I find that /opt/trinity/bin/ is not listed as a search path,
but something called /opt/schily/bin/ *is listed*; I've looked round, but
there is nothing I can find that corresponds to schily. Moreover, I delete
the line to search the path for /opt/schily/bin/, and add the
path /opt/trinity/bin/, yet when I restart I find that trinity is no longer
there, but schily has returned.
Apparently schily (or something related to it) is somehow connected to this
problem. Also it seems that I need whatever schily provides (cdrkit,
cdrtools, etc.), so for the time being, I've put this line back in for the
search path. However, this schily seems to the a controversial topic:
https://en.wikipedia.org/wiki/Talk:List_of_software_forks
https://en.wikipedia.org/wiki/Talk:Cdrkit
What the *$?%!&~ is schily? It seems to refer to a person named Joerg
Schilling (see links above). In any case, I have no folders named schily, so
the path points to nowhere that I can find in my system.
Bill