Version: 2.0.2 (using KDE 4.6.5) OS: Linux Inserted a standard 'R' DVD with 4,7 G capacity. Created an ISO image with only 40 Kbyte below the disk capacity of 4,7 G. k3b status bar indicates that size was ok. 'Burn' aborts with unknown error 255. I shortened the image to be 2 M below the 4,7G. Now it works. I only found this resolve after starting Gnome Braseros, which immediately said that it won't work even with overburn. So, somehow the calculation of k3b seems to be insufficient. Reproducible: Didn't try Steps to Reproduce: Created an ISO image with only about 40 Kbyte below the disk capacity of 4,7 G, so that k3b does not report an exceed. (The actual critical size range unknown to me, i only tried 40K.) Actual Results: Burning starts but wuits with error 255. Expected Results: At least, error 255 should have been explained. That is the main problem. But clearly the capacity indicator in the status bar should have told in the first place that it won't work. OS: Linux (x86_64) release 2.6.39-2-amd64 Compiler: gcc
Oh, forgot to check 'reproducible'. It was like this with 3 different DVD brands, and many tries. I also had the burning permissions verified (all OK). The drive is not-too-old but IDE, managed by scsi kernel driver, generally working ok. Burning at dynamic speed of >16x with k3b.
Clarify: Burning any different DVD brand works flawless with my drive and k3b. My problem was that error 255 was not explained so i tried to find the reason for several days.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!