Dear Maintainer,
* What led up to the situation?
Upgrade from buster to bullseye
* What exactly did you do (or not do) that was effective (or
ineffective)?
Changed the sources-list, update/upgrade/dist-upgrade
* What was the outcome of this action?
All burning programs k3b, xfburn, xorriso ignore manual setting of burning
speed
and uses max speed. After burning is complete the software gives an error and
the DVD is not useable.
* What outcome did you expect instead?
Respect setting manual speed and a functional DVD.
Hi, i am the developer of libburn, which serves underneath xfburn and xorriso. (No need to Cc: me, as i have now subscribed to this bug.)---------------------------------------------------------------------- Quite obviously this report is attributed to the wrong package. But it is not obvious which one would actually be the right one. The overall Debian system and the Linux kernel have not much stake in speed setting of DVD burners or burn success. To blame would rather be the backends, growisofs under K3B and libburn under the others. growisofs did not change in a decade. The jump from libburn-1.5.0 in Debian 10 to libburn-1.5.2 in Debian 11 isn't much suspicious either. Other distros use it since more than a year earlier. Please show your xorriso command line and the messages which you get at the end of the run. (No need to show the many progress messages prefixed by UPDATE. Everything else might be of interest. Most the very start and the very end of the run.) If you can afford experiments with rebooting, then it would be interesting to see whether you get better results from a Debian 10 Live ISO. E.g. pick your favorite desktop version from: https://cdimage.debian.org/mirror/cdimage/archive/10.11.0-live/amd64/iso-hybrid/ put it onto a USB stick: https://www.debian.org/CD/faq/#write-usb and after booting install xorriso like sudo apt-get update sudo apt-get install xorriso (Disclaimer: I did not test whether the 10.11.0 ISOs have apt-get.) Have a nice day :) Thomas
Hi Thomas,
thank you very much for taking care of my stuporous report.
But for my excuse, it is my first one ever.
I tested at first the live CD of Debian 10. K3B also disrespects
the speed setting. But the process seems to adjust the speed
automatically. 18x was starting speed and it was reduced, so that
the resulting speed was 4x. I initially set K3B to 8x. The burning
was also a success and the DVD is usable.
After that, I tried xorrecord under Debian 11, as I did before.
Unfortunately, I am not able to reproduce the error again with xorrecord.
The command I used is as follows:
xorrecord dev=/dev/dvd -nopad speed=8d -eject
/home/daten/DeVeDe/Kongresse/2021/KK_Habt-Glauben/02_NM.iso
The result was a success:
xorriso 1.5.2 : RockRidge filesystem manipulator, libburnia project.
Drive current: -outdev '/dev/dvd'
Media current: DVD-R sequential recording
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4489m free
Beginning to write data track.
libburn : NOTE : WRITE command repetition happened 6 times
Writing to '/dev/dvd' completed successfully.
xorriso : NOTE : Re-assessing -outdev '/dev/dvd' ('/dev/sr0')
xorriso : NOTE : Disc status unsuitable for writing
Drive current: -outdev '/dev/dvd'
Media current: DVD-R sequential recording
Media status : is written , is closed
Media summary: 1 session, 1543856 data blocks, 3015m data, 0 free
K3B under Debian 11 still behaves as before.
Setting speed is totally ignored, the burner makes noise like a starting
jet,
and finishes with error and overall speed of 18,4x.
Maybe I have had a different problem with xorriso before. I tested it only
once,
because I was annoyed by all the testing with K3B, XFBURN etc.
So with your information I think libburn, is not the issue.
Thanks a lot for your help and have a nice day!
Werner
Hi,
i am the developer of libburn, which serves underneath xfburn and xorriso.
(No need to Cc: me, as i have now subscribed to this bug.)
----------------------------------------------------------------------
Quite obviously this report is attributed to the wrong package.
But it is not obvious which one would actually be the right one.
The overall Debian system and the Linux kernel have not much stake
in speed setting of DVD burners or burn success. To blame would rather
be the backends, growisofs under K3B and libburn under the others.
growisofs did not change in a decade. The jump from libburn-1.5.0 in
Debian 10 to libburn-1.5.2 in Debian 11 isn't much suspicious either.
Other distros use it since more than a year earlier.
Please show your xorriso command line and the messages which you get at
the end of the run. (No need to show the many progress messages prefixed
by UPDATE. Everything else might be of interest. Most the very start and
the very end of the run.)
If you can afford experiments with rebooting, then it would be interesting
to see whether you get better results from a Debian 10 Live ISO.
E.g. pick your favorite desktop version from:
<https://cdimage.debian.org/mirror/cdimage/archive/10.11.0-live/amd64/iso-hybrid/>
put it onto a USB stick:
<https://www.debian.org/CD/faq/#write-usb>
and after booting install xorriso like
sudo apt-get update
sudo apt-get install xorriso
(Disclaimer: I did not test whether the 10.11.0 ISOs have apt-get.)
Have a nice day :)
Thomas
Hi, An initial utopic speed is not necessarily the fault of the burn program. The drive's buffer accepts data with high speed until it is full, so only after 2 or 4 MB the observed speed drops to the real speed of burning. DVD-R usually get burned with constant angular velocity (rounds per minute), so that the linear speed reaches the desired speed only at the end of burning. You could try with Xfburn again. Its source code looks like it would ask libburn to set a speed. Regrettably i find no hints in the web how to increase Xfburn's verbosity so that you get to see the debug message Set speed to ... kb/s which is to see immediately before the call to burn_drive_set_speed(). See: https://sources.debian.org/src/xfburn/0.6.2-1/xfburn/xfburn-burn-audio-cd-composition-dialog.c/?hl=299#L299 I count this as a piece of luck for me. :)) It is not normal that a drive produces bad results if it is asked for high speed or if it is not asked for low speed. So whatever K3B or growisofs (*) do wrong, your drive did its share to cause the failure. (*) It might be that K3B uses cdrskin instead of growisofs. But i have no idea how to find out which of both is in charge for DVD. (cdrskin is the cdrecord compatibility wrapper of libburn.) Have a nice day :) Thomas
Hey Thomas, right after starting xfburn, it won't even let me choose the speed nor burning mode (both grayed off). When I choose an ISO and press burn, xfburn complains about "this writing mode is not supported yet". When I click the tiny icon beside "DVD-R sequential recording", the former grayed menus for speed and writing mode are now available. Then I can also start the writing process, and it does not go to max speed and completes successfully. This is all very confusing. I have no clue what's going on here, and I am so sorry for bothering you with that. Have a nice day Werner Hi, An initial utopic speed is not necessarily the fault of the burn program. The drive's buffer accepts data with high speed until it is full, so only after 2 or 4 MB the observed speed drops to the real speed of burning. DVD-R usually get burned with constant angular velocity (rounds per minute), so that the linear speed reaches the desired speed only at the end of burning. You could try with Xfburn again. Its source code looks like it would ask libburn to set a speed. Regrettably i find no hints in the web how to increase Xfburn's verbosity so that you get to see the debug message Set speed to ... kb/s which is to see immediately before the call to burn_drive_set_speed(). See: https://sources.debian.org/src/xfburn/0.6.2-1/xfburn/xfburn-burn-audio-cd-composition-dialog.c/?hl=299#L299 I count this as a piece of luck for me. :)) It is not normal that a drive produces bad results if it is asked for high speed or if it is not asked for low speed. So whatever K3B or growisofs (*) do wrong, your drive did its share to cause the failure. (*) It might be that K3B uses cdrskin instead of growisofs. But i have no idea how to find out which of both is in charge for DVD. (cdrskin is the cdrecord compatibility wrapper of libburn.) Have a nice day :) Thomas
Hi,
w_thal@t-online.de wrote:
So - with the necessary black magic - it is possible to use Xfburn
for your purpose with your drive.
Insofar this is a success. {:)
I agree. Desktops like XFCE, GNOME, or KDE and their applications bring
my blood pressure up to unhealthy levels every time i have use them.
(As a good classic Linuxer i use fvwm2 as window manager with a config
file that essentially stems from a 20 year old SuSE installation.)
No need to apologize. If i would not be interested i could just have
staid away from this bug report.
Given the lack of any active GUI developers for optical disc burning,
i have to check out the user problems with those programs in order to
distinguish their own problems from potential problems in libburn or in
my command line programs.
Any normal desktop user is more qualified than me to operate Xfburn,
Brasero, or K3B. So i cannot help with talking one of them into doing
what the user wants. At best i can lookup error messages in their code
and follow the traces to a burner problem for which i have knowledge.
But especially with K3B's C++ spaghetti code i have big difficulties
to understand. Program execution tends to vanish in a fog of class
inheritance and function overloading. Often it is hard to find the code
part which does the actual work of talking to the drive or to the burn
program.
I will next dig out the instructions how to attribute this bug report
to the Debian package K3B, because you report a reproducible K3B problem
with the upgrade from Debian 10 to Debian 11.
(I don't hold a Debian rank. But any amateur is allowed to operate the
bug tracking system by mail messages. See:
https://www.debian.org/Bugs/server-control
)
Have a nice day :)
Thomas
Hey Thomas,
yes. At the moment, using xorrecord or xfburn, I am able to do the job.
Thanks a lot for your advice.
I am not such a purist, so I really appreciate the comfort of a desktop like KDE
or LXDE in this case. But I see that there is a huge overhead and with this also
the additional source of errors. But I have great respect for guys like you, doing it
the straight way. :-)
So is there anything I can do to help?
CU
Werner
PS: I am on vacation till December 14th.
Hi,
w_thal@t-online.de wrote:
So - with the necessary black magic - it is possible to use Xfburn
for your purpose with your drive.
Insofar this is a success. {:)
I agree. Desktops like XFCE, GNOME, or KDE and their applications bring
my blood pressure up to unhealthy levels every time i have use them.
(As a good classic Linuxer i use fvwm2 as window manager with a config
file that essentially stems from a 20 year old SuSE installation.)
No need to apologize. If i would not be interested i could just have
staid away from this bug report.
Given the lack of any active GUI developers for optical disc burning,
i have to check out the user problems with those programs in order to
distinguish their own problems from potential problems in libburn or in
my command line programs.
Any normal desktop user is more qualified than me to operate Xfburn,
Brasero, or K3B. So i cannot help with talking one of them into doing
what the user wants. At best i can lookup error messages in their code
and follow the traces to a burner problem for which i have knowledge.
But especially with K3B's C++ spaghetti code i have big difficulties
to understand. Program execution tends to vanish in a fog of class
inheritance and function overloading. Often it is hard to find the code
part which does the actual work of talking to the drive or to the burn
program.
I will next dig out the instructions how to attribute this bug report
to the Debian package K3B, because you report a reproducible K3B problem
with the upgrade from Debian 10 to Debian 11.
(I don't hold a Debian rank. But any amateur is allowed to operate the
bug tracking system by mail messages. See:
https://www.debian.org/Bugs/server-control
)
Have a nice day :)
Thomas
Hi, It's not so much about purism in my personal case, but rather about the unwillingness to repeatedly learn how to do the same things in frequently (*) changing ways. (*) Once every ten years is too much for my ageing brain. Not before somebody shows up and asks for tests or experiments. I don't see suspicious upstream commits at https://github.com/KDE/k3b/commits/master and multiple pages until version 18.08.1 which is in Debian 10. In Debian 11 the K3B version is 20.12.2. The Debian 11 changelog https://tracker.debian.org/media/packages/k/k3b/changelog-20.12.2-1 gives no hint that the Debian maintainers changed something related to burn speed or burning in general. The patches in https://sources.debian.org/src/k3b/20.12.2-1/debian/patches/ don't look suspicious either. So i am out of ideas about how to find the trigger for your problems in Debian 11. Stay safe. Best in a plague-free hut in a remote mountain valley ... Have a nice day :) Thomas