https://bugs.kde.org/show_bug.cgi?id=386401
Thomas Schmitt <scdbac...@gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |scdbac...@gmx.net
--- Comment #2 from Thomas Schmitt <scdbac...@gmx.net> ---
Hi,
Leslie Zhai wrote in Bug report 367639:
> Thanks a lot for your Multi-Session help :)
If i only would better understand the C++ oriented architecture of K3B.
When looking for the code which controls the multi-session "import",
i get quite lost. Only guideline is my backend knowledge. (The fog gets
thinner when i see media type names or SCSI specific terms.)
Up to now i only found an otherwise suspicious spot in line 155 of
src/projects/k3bdatamultisessionimportdialog.cpp
where K3B looks for MEDIA_DVD_PLUS_RW and MEDIA_DVD_RW_OVWR but not for
the similarly behaving types BD-RE and DVD-RAM. (Now i wonder why
multi-session on BD-RE is reported to be possible. Maybe i am looking
at the wrong spot in the code ...)
Whatever, we talk here about DVD+R which is a multi-session medium
on hardware level that should be perceived as STATE_INCOMPLETE if it
is already written and still appendable.
But the code piece, where the dialog causes the start of a mkisofs run,
is still on my to-search list. I.e. what code is executed after sebastian's
step 4 ?
> 4) I choose the last session then I press "OK"
> =>Result: nothing happens
Leslie wrote:
> @sebastian
> Please test as Thomas suggested, the simulator is not able to reproduce
> Multi-Session environment.
Somebody should donate to Leslie a DVD burner in a USB box and a few media.
My suggestion was to run in a shell terminal while the DVD+R is already
inserted in the drive:
dvd+rw-mediainfo /dev/sr0
and to show the output text of that program run.
(If you have more than one optical drive, then it could also be /dev/sr1
or even a higher number.)
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching all bug changes.
