https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #85 from Leslie Zhai ---
Git commit 7114ed5d9661af6a833e55d76d63ab06de148032 by Leslie Zhai.
Committed on 28/08/2018 at 07:53.
Pushed by lesliezhai into branch 'master'.
Change my email address.
Hi Thomas, my brain is better now except
https://bugs.kde.org/show_bug.cgi?id=381074
Luigi Baldoni changed:
What|Removed |Added
CC|aloi...@gmx.com |
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381074
Leslie Zhai changed:
What|Removed |Added
CC||julius...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=381074
Luigi Baldoni changed:
What|Removed |Added
CC||aloi...@gmx.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #82 from Thomas Schmitt ---
Hi,
> now in the official patch only a line is edited
> https://cgit.kde.org/k3b.git/commit/?id=a359173975e574c4cae62214f7de28648d14167c
This is not the fix for Bug 381074 but rather the
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #81 from Cristian Aravena Romero ---
Hello,
Thomas asked me to add this "K3b::Device::MEDIA_WRITABLE_BD;" in two places of
the same file. And now in the official patch only a line is edited
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #80 from Cristian Aravena Romero ---
Created attachment 107733
--> https://bugs.kde.org/attachment.cgi?id=107733=edit
Running Debian 9.1.0
(In reply to Thomas Schmitt from comment #75)
[...]
> If both answers are
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #79 from Thomas Schmitt ---
Hi,
the outcome of the sha512sum run indicates full success as far as K3B
is concerned.
This bug is indeed completely done.
Have a nice day :)
Thomas
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #78 from Cristian Aravena Romero ---
Hello,
(In reply to Thomas Schmitt from comment #75)
[...]
> Important to K3B would be the questions:
>
> - Did the burn run with the Debian ISO succeed ?
> (Your image
>
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #77 from Thomas Schmitt ---
Hi,
forget my first question whether the burn run ended successfully.
I just found
https://bugsfiles.kde.org/attachment.cgi?id=107723
which looks very good. Effective speed around 2x with
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #76 from Thomas Schmitt ---
Hi,
i forgot to mention that
dd if=/dev/sr0 count=11223478 bs=2048 | sha512sum
will last about 1200 seconds at average 4x read speed and probably make
some noise when it reaches 6x or 8x
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #75 from Thomas Schmitt ---
Hi,
> Help...
I am riddling what we see with your fgrep run.
Did you copy+paste my fgrep line together with my three output lines ?
Somehow the shell "bash" tried to execute the lines which
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #74 from Cristian Aravena Romero ---
(In reply to Cristian Aravena Romero from comment #72)
[...]
> (In reply to Thomas Schmitt from comment #70)
>
>
> [...]
>
> > $ fgrep -r MEDIA_WRITABLE_DVD';' .
> >
https://bugs.kde.org/show_bug.cgi?id=381074
Leslie Zhai changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #72 from Cristian Aravena Romero ---
Hello,
(In reply to Thomas Schmitt from comment #70)
[...]
> $ fgrep -r MEDIA_WRITABLE_DVD';' .
> ./libk3b/projects/videodvd/k3bvideodvddoc.cpp:return
>
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #71 from Thomas Schmitt ---
> Now the qDebug() statements about "Bug 381704" need to be removed.
Oops. Number flip. qDebug() statements about "Bug 381074", of course.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #69 from Cristian Aravena Romero ---
Created attachment 107724
--> https://bugs.kde.org/attachment.cgi?id=107724=edit
Image of k3b recording the .iso of Debian 9.1.0 in the Blu Ray
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #68 from Cristian Aravena Romero ---
Created attachment 107723
--> https://bugs.kde.org/attachment.cgi?id=107723=edit
k3b.txt
Dear Friends,
I am happy :-) We have solved this "Error". Now you can record the .iso
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #67 from Leslie Zhai ---
Git commit 329c969be1dbc3455d65925bcad32f4df3a5b428 by Leslie Zhai.
Committed on 06/09/2017 at 01:54.
Pushed by lesliezhai into branch 'master'.
Add BD-RE MediaType as Thomas's idea.
M +4
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #66 from Thomas Schmitt ---
Hi,
> I get lost ... Please tell me to download the commit
Excuse my enthusiasm. :))
And forget about the qDebug() proposal of Comment 62 for now.
Edit file
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #65 from Cristian Aravena Romero ---
Hello,
I get lost ... Please tell me to download the commit
Regards,
--
Cristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #64 from Thomas Schmitt ---
Hi,
if the change in line 264 does not help, try the same in line 252 ff.:
else if( d->isDvdImage )
mt = K3b::Device::MEDIA_WRITABLE_DVD |
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #63 from Thomas Schmitt ---
Hi,
i found a suspect:
https://cgit.kde.org/k3b.git/tree/libk3b/jobs/k3biso9660imagewritingjob.cpp#n232
void K3b::Iso9660ImageWritingJob::startWriting()
{
...
else {
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #62 from Thomas Schmitt ---
Hi,
do we get through this piece of code ?
https://cgit.kde.org/k3b.git/tree/libk3b/projects/datacd/k3bdatajob.cpp#n699
bool K3b::DataJob::waitForBurnMedium()
{
// start with all
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #61 from Thomas Schmitt ---
Hi,
this qDebug and its "<<" methods are a little debugger on its own.
I would have expected some hex number which we'd need to decipher to
a list of media types. But this is comfortable.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #60 from Cristian Aravena Romero ---
Created attachment 107704
--> https://bugs.kde.org/attachment.cgi?id=107704=edit
$QT_LOGGING_RULES="*.debug=true" k3b / k3b_log.txt
Hello Thomas and Leslie,
Bug 381074: wanted:
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #59 from Cristian Aravena Romero ---
Hello,
caravena@caravena-530U3C-530U4C:~/Programas/k3b$ k3b
QFileInfo::absolutePath: Constructed with empty filename
kdeinit5: preparing to launch
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #58 from Leslie Zhai ---
Git commit 4cc3da32a6dac6405a67f7791f49ef38149dadd6 by Leslie Zhai.
Committed on 05/09/2017 at 02:28.
Pushed by lesliezhai into branch 'master'.
also print the properties which sees as
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #57 from Thomas Schmitt ---
Hi,
> * k3b_log_file.txt is empty
So those messages came out of stderr, not stdout.
It may be that macro K3B_DEBUG is not defined and thus the qDebug()
statements did not get compiled. Try
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #56 from Cristian Aravena Romero ---
Hello,
caravena@caravena-530U3C-530U4C:~$ k3b | tee -i /tmp/k3b_log_file.txt
QFileInfo::absolutePath: Constructed with empty filename
kdeinit5: preparing to launch
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #55 from Cristian Aravena Romero ---
In reply to Thomas Schmitt from comment #52)
[...]
> > What log?
>
> I can only guess where qDebug() messages show up.
> The web talks of "application output". An example on
>
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #54 from Thomas Schmitt ---
Hi,
those warnings are kind of a reminder of a developer who did not
finish his work yet. If no error messages appear, then k3b is probably
ready to run.
But don't ask me where the executable
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #53 from Cristian Aravena Romero ---
Created attachment 107692
--> https://bugs.kde.org/attachment.cgi?id=107692=edit
/home/caravena/Programas/k3b/k3b/src/k3bemptydiscwaiter.cpp:271:2:
Hello,
Information when
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #52 from Thomas Schmitt ---
Hi,
> What log?
I can only guess where qDebug() messages show up.
The web talks of "application output". An example on
http://www.qtcentre.org/threads/19534-redirect-qDebug%28%29-to-file
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #51 from Cristian Aravena Romero ---
Created attachment 107691
--> https://bugs.kde.org/attachment.cgi?id=107691=edit
Editing the source code
Hello,
Are the changes correct?
Regards,
--
Cristian
--
You are
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #50 from Cristian Aravena Romero ---
(In reply to Thomas Schmitt from comment #49)
> If you find the messages in the log, then show them together with
> the code piece by which you printed it.
Hello,
What log?
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #49 from Thomas Schmitt ---
Hi,
there is no need to upload. Just change the code, build K3B, and test what
it reports. If you find the messages in the log, then show them together with
the code piece by which you
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #48 from Thomas Schmitt ---
Hi,
if you feel adventurous enough: I propose something like
qDebug() << "Bug 381074: wanted: "
<< __PRETTY_FUNCTION__ << d->wantedMediaType
<<
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #47 from Cristian Aravena Romero ---
Hello,
https://github.com/KDE/k3b/compare/master...caravena:patch-1
Regards,
--
Cristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #46 from Cristian Aravena Romero ---
Hello,
caravena@caravena-530U3C-530U4C:~/Programas/k3b/k3b$ gedit
src/k3bemptydiscwaiter.cpp
caravena@caravena-530U3C-530U4C:~/Programas/k3b/k3b$ git commit -m
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #45 from Cristian Aravena Romero ---
(In reply to Thomas Schmitt from comment #44)
[...]
> A more significant constant text like "Bug 381074:" would help to recognize
> the texts from your change.
+#ifdef K3B_DEBUG
+
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #44 from Thomas Schmitt ---
Hi,
the changeset is labeled "master". So i assume
git clone git://anongit.kde.org/k3b
or in a cloned directory of git://anongit.kde.org/k3b
git pull
Then build and run with a blank
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #43 from Cristian Aravena Romero ---
(In reply to Leslie Zhai from comment #41)
> Git commit 837eeb482a13af6a27616a4412f5cd8d92b7feaf by Leslie Zhai.
> Committed on 04/09/2017 at 02:11.
> Pushed by lesliezhai into branch
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #42 from Thomas Schmitt ---
Hi,
we not only need to know the wanted properties but also the properties
which K3B sees as present at that point in the code.
To my understanding that would be:
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #41 from Leslie Zhai ---
Git commit 837eeb482a13af6a27616a4412f5cd8d92b7feaf by Leslie Zhai.
Committed on 04/09/2017 at 02:11.
Pushed by lesliezhai into branch 'master'.
Prints the desired info in a user-visible
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #40 from Leslie Zhai ---
I will add qDebug to print them next Monday, I am using my phone to reply :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #39 from Thomas Schmitt ---
Hi,
just to summarize the riddle we are trying to solve:
K3B reports to see an empty BD-R medium but in the same window demands
to get fed by an empty medium of at least 21.4 GiB.
An empty
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #38 from Thomas Schmitt ---
Hi,
@Cristian:
Leslie asks you to run K3B under control of the program gdb, to set a
"breakpoint" at line 257 of k3bemptydiscwaiter.cpp, and to let gdb
print the desired variable content when
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #37 from Cristian Aravena Romero ---
(In reply to Thomas Schmitt from comment #34)
> Hi,
>
> i just did a git pull in my clone from git://anongit.kde.org/k3b.git
> and cannot see any related commit by git log.
> Can you
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #36 from Cristian Aravena Romero ---
(In reply to Leslie Zhai from comment #35)
> Please use GDB to set breakpoint and print
Hello Leslie
?
Regards,
--
Cristian
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #35 from Leslie Zhai ---
Please use GDB to set breakpoint and print
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #34 from Thomas Schmitt ---
Hi,
i just did a git pull in my clone from git://anongit.kde.org/k3b.git
and cannot see any related commit by git log.
Can you point me to the changeset which puts the print statements into
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #33 from Cristian Aravena Romero ---
Created attachment 107640
--> https://bugs.kde.org/attachment.cgi?id=107640=edit
k3b v17.11.90 (git)
Hello,
At night I try, already is the version of compiled k3b
Regards,
--
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #32 from Leslie Zhai ---
Yes!
> Hello Leslie Zhai,
>
> git clone git://anongit.kde.org/k3b (?)
>
> Regards,
> --
> Cristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #31 from Cristian Aravena Romero ---
Hello Leslie Zhai,
git clone git://anongit.kde.org/k3b (?)
Regards,
--
Cristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #30 from Thomas Schmitt ---
Hi,
are the proposed print commands already in place ?
If so, how would they look ?
Are they supposed to show up in
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #29 from Cristian Aravena Romero ---
Hello,
Report en Launchpad.net
https://bugs.launchpad.net/k3b/+bug/1713485
Regards,
--
Cristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #28 from Cristian Aravena Romero ---
(In reply to Leslie Zhai from comment #26)
> (In reply to Cristian Aravena Romero from comment #25)
> > (In reply to Thomas Schmitt from comment #24)
[...]
> > > i am out of ideas,
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #27 from Cristian Aravena Romero ---
Hello Leslie Zhai,
git clone git://anongit.kde.org/k3b (?)
Regards,
--
Cristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #26 from Leslie Zhai ---
(In reply to Cristian Aravena Romero from comment #25)
> (In reply to Thomas Schmitt from comment #24)
>
> Hello,
>
>
> > i am out of ideas, except that Leslie prepares a test version of
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #25 from Cristian Aravena Romero ---
(In reply to Thomas Schmitt from comment #24)
Hello,
> i am out of ideas, except that Leslie prepares a test version of K3B
> by which Cristian can build and test.
I look forward
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #24 from Thomas Schmitt ---
Hi,
i am out of ideas, except that Leslie prepares a test version of K3B
by which Cristian can build and test.
It should show the information mentioned in
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #23 from Cristian Aravena Romero ---
Created attachment 107544
--> https://bugs.kde.org/attachment.cgi?id=107544=edit
Empty BD-R medium - ISO Debian 9.1.0 - k3b 17.8.0
Hello,
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #22 from Thomas Schmitt ---
Hi,
> BD R empty
> https://bugs.kde.org/attachment.cgi?id=107536
Indeed. Unformatted and unused.
Does this medium produce the messages from
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #21 from Cristian Aravena Romero ---
Created attachment 107536
--> https://bugs.kde.org/attachment.cgi?id=107536=edit
bd_mediainfo.txt (BD R empty)
(In reply to Thomas Schmitt from comment #20)
> Hi,
>
> the given
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #20 from Thomas Schmitt ---
Hi,
the given BD-R medium is not blank but rather seems to have been
used already with growisofs. Only growisofs formats BD-R to state SRM+POW:
Mounted Media: 41h, BD-R SRM+POW
The
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #19 from Cristian Aravena Romero ---
Created attachment 107535
--> https://bugs.kde.org/attachment.cgi?id=107535=edit
bd_mediainfo.txt
Hello Leslie Zhai,
[...]
> Hi Cristian,
>
> > dvd+rw-mediainfo /dev/sr0 2>&1 |
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #18 from Thomas Schmitt ---
Hi,
if there is no simple code change which circumvents that size check,
then you will have to prepare the printing of the decision criteria
for Cristian, so that he can try.
With the data
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #17 from Leslie Zhai ---
Hi Cristian,
> Try by creating a data file of 21.5 GiB size
Then how to reproduce the issue?
https://pbs.twimg.com/media/DHzWyToVYAAwEse.png
Regards,
Leslie Zhai
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #16 from Leslie Zhai ---
> One can see how the criteria are set up in waitForDisc():
> Currently i fail to see the spot where this is called. So it would be
> interesting to see by what values the loop gets
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #15 from Thomas Schmitt ---
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
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #14 from Thomas Schmitt ---
Hi,
Leslie Zhai wrote:
> QEventLoop http://doc.qt.io/qt-5/qeventloop.html
This does not help much with understanding under which circumstances
the particular medium waiting loop shall end.
I
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #13 from Leslie Zhai ---
Hi Thomas,
Thanks for your kind suggestion!
> but currently i do not understand how this loop works and were the state is
> changed.
QEventLoop http://doc.qt.io/qt-5/qeventloop.html
it
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #12 from Thomas Schmitt ---
Hi,
i have to correct a copy+paste error of mine.
It's not line 691
return i18n("Please insert an empty medium into
drive%1", deviceString);
but line 728
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #11 from Thomas Schmitt ---
Hi,
the screenshot message
https://bugsfiles.kde.org/attachment.cgi?id=106037
does not really look to me as a complaint about lack of medium space.
It rather looks like the medium is not
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #10 from Thomas Schmitt ---
Hi,
i would need to search for the 8.8.0 ISO, because now 9.1.0 is in the
"current" directory at the Debian download site.
Let's have a look at 9.1.0. It should suffice to get the 450 KB Jigdo
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #9 from Leslie Zhai ---
Hi Cristian,
Sorry for my late response!
> See this report:
> https://bugs.launchpad.net/cdemu/+bug/1697987
Yes, I do not have BD medium for testing, and the simulator is not able to
https://bugs.kde.org/show_bug.cgi?id=381074
Leslie Zhai changed:
What|Removed |Added
CC||scdbac...@gmx.net
--
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #8 from Cristian Aravena Romero ---
ping
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #7 from Cristian Aravena Romero ---
Hi,
See this report:
https://bugs.launchpad.net/cdemu/+bug/1697987
Regards,
--
Cristian
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #6 from Cristian Aravena Romero ---
ping Leslie :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #5 from Cristian Aravena Romero ---
(In reply to Leslie Zhai from comment #4)
> Hi Cristian,
Hello Leslie
[...]
> Could you reproduce the issue all the time?
Yes.
Regards,
--
Cristian
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=381074
Leslie Zhai changed:
What|Removed |Added
CC||lesliez...@llvm.org.cn
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #3 from Leslie Zhai ---
Git commit 81b4b37b9b580ac701a57c570c8eca58d1b1 by Leslie Zhai.
Committed on 12/06/2017 at 03:38.
Pushed by lesliezhai into branch 'master'.
Reproducebility race?
M +2-1
https://bugs.kde.org/show_bug.cgi?id=381074
Cristian Aravena Romero changed:
What|Removed |Added
Summary|Does not write image|[MATSHITA BD-MLT
86 matches
Mail list logo