k3b errors out while burning
Bo Berglund
bo.berglund at gmail.com
Fri Feb 12 16:19:56 UTC 2021
On Mon, 27 Feb 2006 22:14:52 -0800, Ed Fletcher <ed at fletcher.ca> wrote:
>C Hamel wrote:
>> On Monday 27 February 2006 14:23, Ed Fletcher wrote:
>>
>>>C Hamel wrote:
>>>
>>>>Both Breezy & Dapper Flight4 are having a problem burning using k3b. If
>>>>I disconnect from the internet, at least Breezy will burn that same info
>>>>to CD (haven't tried it on Dapper, yet). Is there a connection between
>>>>burning & being on the internet? I don't remember having that problem
>>>>before switching to ubuntu.
>>>>
>>>>Thanks!
>>>
>>>I'm using Ubuntu 5.10 and k3b. I've had no problems with burning either
>>>CDs or DVDs while connected to the net. What exactly is happening when
>>>you try to burn something?
>>>
>>>Ed
>>>--
>>>Ed Fletcher
>>>ed at fletcher.ca
>>>
>>>You live and learn. At any rate, you live.
>>>- Douglas Adams
>>
>> I get a tremendously long pause... then, "I/O error, not necessarily
>> serious" (what a bogus msg!). Of course, 100% of them _are_ serious enough
>> to render a coaster each and every time rather than a completed CD/DVD of
>> whatever type. So far I've had so many coasters as to have lost count but
>> this morning, alone, rendered at least three.
>>
>That's pretty bizarre. To start with, you might want to consider using
>rewritables until you get this solved.
>
>If k3b works when the connection to the internet is down but fails when
>the connection is up, then maybe you have something using the connection
>that is using too much memory/processor resources to allow k3b to
>operate. Do you see any (unexplained) activity on the ethernet
>connection when it's up? Also, run 'top' in a terminal window to check
>on resource usage by k3b when the net is up and when it's down.
>
>HTH,
>Ed
You are hi-jacking my thread "Change ls datetime format - how?" by replying to a
message in that thread and then replacing the subject and body of the message...
It screws up threading in newsreaders and mail agents since they use a hidden
thread ID value in the headers.
Please don't do this...
--
Bo Berglund
Developer in Sweden
More information about the ubuntu-users
mailing list