k3b is persistently telling me that I have no DVD-RAM drives present. This is surprising because Wodim -scanbus has been doing so for many hours now. k3b keeps wanting me to start hal, which is in fact running already -- it ha sbeen since I deleted my chroot stack a couple of weeks ago after K3B told me that it was inhibited by the presence of a running chroot.

N.B.: Deleting a chroot stack does not appear to be the innocuous easy operation I expected. When I did so, it in fact deleted my entire home directory, too.

At any rate, k3b appears to be useless in its present state. And I need the convenience of k3b as opposed to the many, many options of wodim. Thank you very much!

Dear submitter,

Some time ago you filed a report in the Debian bug tracking system against the k3b package, http://bugs.debian.org/k3b

Upstream have now declared a major milestone and released K3b version 2.0, which has now been uploaded to Debian unstable.

We have a fairly large backlog on bugs reported against K3b and require your assistance.

Could I ask you to install the K3b package from unstable and verify that your report is still valid with version 2.0.

If your bug has been resolved then please send an email to xxxx-done@bugs.debian.org, where xxxx is your Debian bug report number, giving your description of how the bug is working.

If your bug has not been resolved, then please first check upstream reports for a duplicate, and then send an update email to xxxx@bugs.debian.org, stating that the bug is still valid.
https://bugs.kde.org/buglist.cgi?quicksearch=k3b

If we don't hear from you in the near term, then we may have to close your report as without moreinfo most reports are difficult to reproduce.

Thanks for your assistance in working with Debian K3b.

Mark


====================================================================================
The Debian team values users reports, but we are busy, and so we
kindly ask you to access the upstream support facilities:

There is a user mailing list which maybe used to get support:
http://lists.sourceforge.net/lists/listinfo/k3b-user

To post a message to all the list members, send email to
k3b-user@lists.sourceforge.net.


If you know that the bug you want to report is in the "upstream"
code then please check/ file against the KDE Bug tracking system:
https://bugs.kde.org/buglist.cgi?quicksearch=k3b

You can also report bugs directly upstream using the K3b Help:Report Bug
menu entry.


If you feel that the bug is one that other Debian users should
know about then you are welcome to file a report in the Debian BTS
as well.  Please keep in mind, however, that managing bug reports
is part of the maintainers' workload.

As a minimum we ask that you Cc: k3b-user@lists.sourceforge.net any
reports you file in the Debian Bug Tracking system so that upstream
are aware of the issue you are reporting.

Hi there!

I just got the news that your new 2.0 version was up in unstable.

I downloaded it and started it.

Alas, the very first thing the program did was complain that no writable CD
media drives were in my system, and that hal needs to be in and working/up and
running.

This, as you may recall, is essentially the same behavior as the previous
version had.

I might note in passing that it is only my 2 DVD-RW drives that are presently
configured as SATA devices. (My two HDDs are still the old-fashioned parallel
ATA models.) Perhaps this will help to find my problem.

Thank you very much!

Willy,

Thanks for the update.

We will have to forward your report upstream as without your hardware it is almost impossible to debug remotely.

Could I ask you to forward the details returned from:

wodim -checkdrive
wodim -scanbug

Thanks,
Mark

Hi there, Mark!

Unfortunately, wodim does not recognize a "-scanbug" option. On the
presumption that you actually meant "-scanbus", I'm attaching a file that has
a wodim -scanbus command summary attached.

If that isn't correct, I await further clarification of your intent.

Thank you very much! :)