[kde-linux] K3B and DVDs?

Dennis Veatch dveatch at woh.rr.com
Wed Dec 28 22:21:26 UTC 2005

On Wednesday 28 December 2005 15:34, Paul Smith wrote:
> On 12/28/05, Liath Bodach <klgc at tds.net> wrote:
> > > > So you understand I'm at the early learning stage:
> > > > In the last few days I have expunged MS from the PC on my LAN and
> > > > installed Debian.  Being very happy with my Mac, I went with KDE to
> > > > allow a somewhat similar desktop.
> > > >
> > > > Now it's time to backup what I've done before I screw it up :-)  so I
> > > > also installed K3B to use optical media.  In my trials today I've had
> > > > no problem creating and restoring a data CD,  but I can't get K3B to
> > > > do anything with DVDs.  I've tried DVD-R and DVD-RW, and even
> > > > different brands of each (Verbatim, hp and imation).  I hate to use
> > > > umpteen CDs when one or two DVDs will do the trick :-(
> > > >
> > > > I have a Benq 32x10x40 CD R/W in an internal bay (hdc) and a Pioneer
> > > > DVD-RW DVR-103 in another internal bay (hdd).  If I load a DVD with
> > > > contents K3B lists what is on it and if I load a blank DVD it says it
> > > > knows that also.
> > > >
big snip
> > > I have had a similar problem here on Fedora Core 4. I suspect that the
> > > problem is caused by the fact that growisofs uses /dev/hdd instead of
> > > /dev/dvd.
> >
> > Is there anything I can do about that as a test ??
> I do not know, but since k3b is NOT a reliable program, I suggest that
> you use the command line:
> http://www.yolinux.com/TUTORIALS/LinuxTutorialCDBurn.html
> Paul

Hmm. I think you are *way* off base with that remark and the problems noted in 
this thread are strictly related to the distros being used. K3b *is* a 
reliable program and works just fine here burning DVDs. In fact I cannot 
remember that last time k3b made a coaster of either CDs or DVDs or the last 
time I had a problem with it.

It makes no difference to k3b which /dev growisofs uses so long as /dev/blah 
points to the correct device. Since in this thread it was
reported  /media/cdrom1 is busy, then obviously you have to find who has that 
device mounted. 

If you are using hal that is another area you should explore, particularly the 
*.fdi files and even possibly /etc/fstab if you are not using pmount. All 
those items are distro specific. As such you might want to visit your distros 
forums for the particulars.

You can tuna piano but you can't tune a fish.

More information about the kde-linux mailing list