LinuxQuestions.org - k3b Sees Blank BD-R, but will not Burn to it, but cdrecord Will

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - k3b Sees Blank BD-R, but will not Burn to it, but cdrecord Will (https://www.linuxquestions.org/questions/slackware-14/k3b-sees-blank-bd-r-but-will-not-burn-to-it-but-cdrecord-will-4175431755/)

k3b Sees Blank BD-R, but will not Burn to it, but cdrecord Will

As the topic implies, having issues with k3b. I typically use it to create an iso, then burn the iso in a separate instance.

It will create an iso just fine, but whenever I want to actually burn the disc, it will allow me to start, but then produces a pop up window asking me to put in a blank disc. It will even say there is one there, but refuses to actually proceed with the burning process. This is despite ejecting and loading again at that window.
I should note that using cdrecord works just fine when I tried it from the command line. I also tried burning as root (yes I know that's bad practice, but I did it to make sure permissions weren't it) and that had the same problem.

For reference, the cdrecord command that worked is as follows:

Quote:

cdrecord -v -driveropts=burnfree -dev=/dev/sr2 /home/s3phir0th115/Desktop/Games.iso

I needed to add -driveopts=burnfree for it to go, otherwise it refused to burn and suggested using that option.

Any help on this would be appreciated. I'm told I'm not the only one having this problem when I asked on ##slackware.

What does

Code:

wodim --devices

say?

Maybe need to adjust device name.

You could try burning from command line with wodim to see if it works.

Quote:

Originally Posted by etech3 (Post 4803537)

What does

Code:

wodim --devices

say?

Maybe need to adjust device name.

You could try burning from command line with wodim to see if it works.

It does nothing, as wodim doesn't ship with slackware. However, it does ship with cdrecord, which is what it is based on, but that just says you need at least one track specified.

As said, cdrecord burning does work when I tried it from the command line, and when I tried forcing k3b to use that, it still didn't work, having the same error I mentioned before.

Quote:

Originally Posted by etech3 (Post 4803537)

What does

Code:

wodim --devices

say?

Code:

wodim: Command not found.

Slackware has the real thing, not the Debian fork.

Quote:

Originally Posted by s3phir0th115 (Post 4803434)

K3b creates a log, please post it.

Hmm, strange... I tried it again now and it got past the prompt, though this time it was with a much smaller test image that I cancelled before it actually did the burning, but after where the prompt would be. (Also tried a simulation prior to that, which was apparently not what I thought it was since I got a coaster.) All I would have done since last time I tried is reboot, so I don't know what might have messed it up.

In any case, I suppose the problem is solved. Sorry for the time waste.

Actually, I am having the same problem. It appears that a blank DVD, while recognized by KDE, and even ejectable and "loadable" by k3b, will not be written by k3b. I'll report more after I have a chance to dig a bit.

Any chance you have a TSSTcorp CD/DVDW SH-S183A SB02 drive?

I think it may have worked because of the smaller size of your test image. If i try to burn larger than what a dvd will hold k3b refuses.

Actually, you're right enine. Having tried a larger image closer to size again, it isn't working yet again.

Regarding what jtsn requested:

Quote:

[System] K3b Version: 2.0.2
[System] KDE Version: 4.8.5 (4.8.5)
[System] QT Version: 4.8.2
[System] Kernel: 3.2.29
[Devices] HL-DT-ST DVD+-RW GSA-H21N 1.00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]
[Devices] _NEC DVD_RW ND-3550A 1.05 (/dev/sr1, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96R, RAW/R96R, Restricted Overwrite] [%7]
[Devices] HL-DT-ST BD-RE WH10LS30 1.00 (/dev/sr2, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] [%7]

That's my lastlog.log

And as for having run it from a terminal:

Quote:

k3b
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QGtkStyle was unable to detect the current GTK+ theme.
sh-4.2$ k3b(28179)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory!
k3b(28179)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory!
k3b(28179)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory!
k3b(28179)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory!
QLayout: Attempting to add QLayout "" to QFrame "", which already has a layout
QCoreApplication::postEvent: Unexpected null receiver

Not sure if there are logs anywhere else, as there is nothing in /var/log that I can see for it. But please let me know if I'm missing something.

I'll hold off on burning this time in favor of seeing if we can actually fix it for good this time.