Version: Current SVN (20080807) (using KDE 4.1.0) Installed from: Gentoo Packages Compiler: gcc (Gentoo 4.3.1-r1 p1.1) 4.3.1 AMD64 OS: Linux K3B for KDE4 just plain refuses to burn CD's. This doesn't appear to be a permissions problem as it WILL correctly erase CDRW's on the same drive. Trying to burn a data CD brings up the status dialog which shows: "Using Wodim 1.1.8"[... etc.] "Starting TAO writing at 4x speed" (the maximum speed the media I'm using at the moment supports) "Could not open for writing" The program stalls here. There is no evidence of drive activity but K3B appears to think burning is still going on, as it doesn't pop up a failure notice, and there doesn't seem to be any way to pull up a full log of what's going on up to this point. "Cancel" works, however. Attempting to exit K3B and restart doesn't change the behavior, however if I instead load the old KDE3 version of K3B (v1.0.5), it will successfully burn the same file to the same disk on the same drive. (Minor note: 1.0.5 also doesn't seem to recognize that the process has stopped - after closing the session it successfully finishes and ejects the CD, but K3B sits there with the "successful" message in the dialog but the progres bars still showing as though the session closing was still ongoing. Possibly related problem?)
I have the exact same problem trying to burn CDs. I'm using KDE 4.1.1 on Arch Linux and my K3B version shows 1.95-SVN. *"Using Wodim 1.1.8"*, using same version here.
Created attachment 27677 [details] k3b error log This is my attempt to create a Data DVD.I started the program, selected new Data DVD, inserted a directory to the project and hit burn with the default settings.
With the attachment above, i am also confirming this bug. I can't write any cd/dvd.
Any thoughts on this bug? I'd like to add that burning with gnomebeaker, wodim, growisofs, works fine.
K3b for KDE4 is NOT EVEN ALPHA. It has NOT been released. Nothing has been tested yet. It is NOT intended to be used. Do NOT expect it to work.
*** Bug 175906 has been marked as a duplicate of this bug. ***
SVN commit 911613 by mmalek: - K3bProcess::stdinFd() returns correct descriptor now (it caused "Could not open for writing" error) - K3bProcess::writeToFd() started to work - K3bActivePipe now ignores a situation when ::write() returns -1 (input pipe to wodim process for some reason returns -1 on wodim's initialization) BUG:168660 M +5 -6 core/k3bprocess.cpp M +0 -5 tools/k3bactivepipe.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=911613