Version: 1.92.0 (using Devel) OS: Linux k3b 1.92.0 RC3-2, KDE 4.4.4, Kubuntu 10.04. The "Waiting for Disc" dialog box flashes on screen and disappears on its own before I can react, when burning with Data Validation. The box appears just after burn while closing the session and re-opening the DVD for read. I think the problem occurs 100%, though unless I'm looking directly at the area of screen where it appears, I don't always see the box, it's so brief. It's disconcerting to a user to not get to do something when a user-choice dialog appears. I suggest maybe waiting 3-5 seconds after a burn for the disc to be detected, somewhere in EmptyDiscWaiter so the dialog display will be suppressed. Or better yet, remember that we just burned and there's data validation pending, so wait invisibly (don't display dialog). Reproducible: Always Steps to Reproduce: Burn Data project with Data Validation on DVD-R, watch screen closely at end of burn. Actual Results: "You see the Waiting on Disc" dialog flash by. Expected Results: As long as the user doesn't eject the disk or something else, suppress the dialog (there's nothing to do).
It's not bug, it's a feature ;) This dialog appears just after the burn, when drive (and system) tries to read newly burned medium. In most cases everything goes fine, medium gets detected so this dialog simply disappears. The dialog is valuable for the user when somethings goes wrong (and she can, for example, reload medium). What's your case? Everything gone fine or there are some problem with medium detection?
In my case, everything apparently went fine. As a UI issue, we shouldn't have the dialog, which normally requires a button push to disappear, simply go away by itself. When I first saw it, I didn't even have time to read it, and it alarmed me that something might have gone wrong, I was told about it and didn't get a chance to take some action in the box. I'm not fooled - but if you want to improve the UI, it should behave predictably.
Michal, I didn't disappear after surfacing a couple of months ago to fix K3b bugs. I had a simple mission then: burn a BDR on my new blu-ray drive with K3b on Kubuntu. I still cannot. I've filed numerous bug reports against K3b and dvd+rw-tools 7.1(in ubuntu launchpad), and fixed some number as were necessary to my purpose. I have a tale of woe as regards dvd+rw-tools package. Kubuntu/Ubuntu inherits it from the Debian repositories. The "reference" copy appears to be owned by Andy Polyakov, appro@fy.chalmers.se. It's a one-man show, and always has been. He does not take input from others, and in the last several years, has not even responded to developer's queries. I have not communicated with him (yet). About 2003, he turned support for dvd+rw-tools over to a debian mailing list cdwrite@other.debian.org. The list is effectively dead, and has been for a couple of years. The last entry in the changelog for the product was March 3, 2008. Nothing has changed in 2-1.2 years. Mr. Polyakov has effectively retired. I inquired on the named list, and received two replies from "Thomas Schmitt" <scdbackup@gmx.net> and "Schily" <joerg.schilling@fokus.fraunhofer.de. These are the developers of competing products, xorriso and cdrecord. There is a long and contentious history among these three developers, (including Mr. Polyakov). All three products are one-man shows, and all three developers are brash and egoistic. Schilly referred me to two support mailing lists for his cdrecord cdrecord-support@berlios.de and cdrecord-developers@berlios.de. All three developers have been berated in the Linux world for their ideosyncratic ways, and for that reason, all three products remain one-man shows. dvd+rw-tools is orphaned, and we absolutely rely on it. The package has bare-bones support for BDR (none for RRM mode for example). There's also no support for the new LTH disks, and multi-layer (>2) disks coming out this year. The package was not written by a professional programmer, and needs a revamp before further development. It's written in C/C++, but lacks C++ structure: data encapsulation, abstraction and modularity. Andy was probably an electrical engineer or firmware developer, to be fair. The question is what do we do now? The debian host of the dvd+rw-tools is not where support and development occur. I don't know where the archive is, or who has write authority over it. That would be the place to start. I've filed my bugs against the Ubuntu package, and there's no support there, either. Somewhere we need to split the package, and put it where someone is willing to support it. If we make an ubuntu split, we futher splinter an already splintered landscape. What do you think we ought to do? K3b can't support anything not supported/implemented in dvd+rw-tools, so further progress depends on active development in the upstream package(s). I'm willing to go at least as far as the work I've already done in dvd+rw-tools. I've got 10 patches, including some of the revamp I mentioned above. How do I get the patches in the package? Who approves them (don't say Andy, he's a no-show). Stuart --- On Thu, 7/1/10, Michał Małek <michalm@jabster.pl> wrote:
Hi Stuart. The situation is not easy, indeed. You haven't mentioned cdrkit (the fork of cdrtools) which is ubiquitous at the moment but poorly maintained (if not dead). Cdrtools is well maintained and its author (Joerg Schiller) is willing to collaborate with us (I've already talked to him). That having said there is controversy around cdrtools' license which prevents some distribution from distributing it. I think the good thing for us would be to integrate libburnia with K3b as a new backend. It seems to be maintained and is available in every distribution. As for dvd+rw-tools patches: you already know more than me :) I think you should try to contact Andy. Forking a project is always a measure of last resort.
Version 2.0.80, KDE 4.5.1 An error message states, after writing and before verifying data, that no suitable medium can be found. My gripe with this behaviour is that the message dialogue grabs the focus. I would prefer to be left in peace working on something on a different virtual desktop. The 'error' is quite inappropriate because the disc it needs to verify is the disc to which it has just written.
I think this report is still valid. The dialog referenced in description should appear only if the disc is not correctly detected/read after burning process. So manual user intervation is required to eject/re-insert the disc and in this case makes sense to show the dialog. One ore problem: this dialog steals focus under Wayland. K3b comes to foreground when the dialog is shown.
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!
Can reproduce with K3b 22.12 beta on Arch Linux.