k3b Sees Blank BD-R, but will not Burn to it, but cdrecord Will
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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:
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.
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.
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:ostEvent: 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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.