Version: 0.10.3 (using KDE 3.2.0 RC1, Gentoo) Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice) OS: Linux (i686) release 2.4.20-gentoo-r9 k3b automatically ejects and reloads the CD/DVD between burning and verifying, no matter if "Eject after burn" is selected or not. As my notebook-drive is not able to reload the medium automatically, I have to be at the computer when burning is finished to manually reload the medium. It would be good to start verifying after burning without ejecting the CD/DVD.
*** Bug 92935 has been marked as a duplicate of this bug. ***
Ejecting the CD is reuquired by some disc drives to properly burn the media. If your drive is not one of these, just disable ejecting after the burn and your problem will go away, will it not ?
Yes, it will. But wait, I *like* the ejection, makes me feel comfortable to do something else while the CD is been burned. I just think that, if it's feasable to eject it only once, it would be better.
*** This bug has been confirmed by popular vote. ***
*** Bug 81056 has been marked as a duplicate of this bug. ***
As far as I know linux still needs the cd/dvd to be ejected after burning to return to a proper state. That's why I kepp this eject between stuff.
> As far as I know linux still needs the cd/dvd to be ejected after burning to > return to a proper state. That's why I kepp this eject between stuff. One could still implement the option, but discourage its use. This way the users would have the option to find out if this is still necessary and to check if it perhaps works for them.
I also think that this is an extremely annoying problem - when I leave my laptop to burn a disc, it cannot verify until I return to it. I have "Do not eject after burn" set, but the disc is still ejected after burn, before verify. What is the reason for linux needing to eject the disc? Can this be circumvented?
On Thursday 17 August 2006 18:09, Jim Broadhead wrote: > What is the reason for linux needing to eject the disc? Can this be > circumvented? not to my knowledge.
There is yet another reason why this annoying. I use Linux on my desktop, and although the opening/closing of the tray is automatic (unlike laptops) when the medium goes back in, with the recorded data, it will be detected by the hal deamon, which will then prompt me on what to, and having to close that pop-up window easily becomes very annoying... If the intermediate eject cannot be avoided, at least is there a way of bypassing medium detection when closing back the tray?
When I run the following command the result is the same as if I'd have with K3b, _but_ doesn't eject the disk between burning and verifying (and it still works), Why can I do this manually but K3b can't ? wodim cd.iso;md5sum cd.iso;md5sum /dev/hdb;eject /dev/hdb
the problem is not that k3b cannot do it. All I would have to do is remove the reload command but I just think it is necessary in most situations. Maybe that changed with a later kernel version. I don't know.
I don't quite understand the problem, doesn't the command in my last post work on older kernels? Is it possible to get a checked radiobox in the GUI that says something like "Reload the disk before verification (recommended)" and disable it if the "verify after burn" is unchecked? If that's not possible the very least would be to have a optional compiler flag like --noreload
I just commited a fix to this bug which bounced since you already closed this as WONTFIX. Actually you were right and the only problem is with mounting. It seems linux does some caching or whatever so new data will not show up until reloaded. However, K3b does not mount for verification and does not use any filesystem drivers either but reads the plain data from the disk. Thus, no reloading necessary and K3b svn (soon to become 1.1) does not do it anymore. Thanks for insisting. :)
this is really fixed.
*** Bug has been marked as fixed ***.
Thanks for fixing this bug, I really appreciate it! So the disk still needs to be reloaded after the verification to be able to mount it and see the content, I'll have a look into it and see if there's solution to this too. Ps. You closed it as WONTFIX, not me :)
> Thanks for fixing this bug, I really appreciate it! > So the disk still needs to be reloaded after the verification to be able to > mount it and see the content, I'll have a look into it and see if there's yes, exactly. But that is no longer a problem as far as K3b is concerned since you can always disable the automatic ejection in K3b. > solution to this too. Maybe there is some kernel call to reset the drives data or whatever, I don't know. > Ps. You closed it as WONTFIX, not me :) ups, sorry... my bad.