[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"

[Thomas Schmitt]

https://bugs.kde.org/show_bug.cgi?id=381074

--- Comment #15 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,

@Leslie:
Maybe you can determine the expectations of slotMediumChanged without having
a BD-R medium and drive.

Try by creating a data file of 21.5 GiB size

  dd if=/dev/zero bs=2048 count=11272192 of=test.img

and submitting it to K3B while it uses a CDemu drive with some virtual
blank DVD+R or DVD-R medium.

Print before the big "if" in slotMediumChanged()
  https://cgit.kde.org/k3b.git/tree/src/k3bemptydiscwaiter.cpp#n257
  if ( (d->wantedMediaType & K3b::Device::MEDIA_BD_RE) &&
the requirement settings and medium properties:

  d->wantedMediaType
  d->wantedMediaState
  d->wantedMinMediaSize

  medium.diskInfo().mediaType() 
  medium.diskInfo().diskState()
  medium.actuallyRemainingSize()

The "wanted" values are supposed to be realistic. At least the value
of actuallyRemainingSize() will be insufficient. So best print only
once and use a static variable to prevent a flood of more messages.

------------------------------------------------------------------------

It would also be helpful to assert that really the if-test in line 634
is reached and performed.
For that you could (very temporarily) insert a case before
  https://cgit.kde.org/k3b.git/tree/src/k3bemptydiscwaiter.cpp#n632
  // we have exactly what was requested (K3b never requests a specific
that prints a message and accepts any medium, state, and size.

    } else if (1) {

        // >>> print message that this line was reached

        finishWaiting( medium.diskInfo().mediaType() );

While above print proposal would be helpful on Cristian's system, too,
this mindless accepter here is not suitable for tests with real media,
although it is supposed to let Critian's intended burn run start.
(Only good if the medium is the right one, inserted, and already recognized
 by the drive.)

Without this accepter, you should look for the message from line 649:
        qDebug() << "------ nothing useful found.";
which would prove that really all tests were made and none matched.


Have a nice day :)

Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.