#519200 k3b: Should recognize cdrskin as cdrecord (it's compatible)

Package:
k3b
Source:
k3b
Description:
Sophisticated CD/DVD burning application
Submitter:
Date:
2014-07-29 19:15:19 UTC
Severity:
normal
#519200#5
Date:
2009-03-10 22:46:13 UTC
From:
To:
cdrskin works in place of wodim or cdrecord if wodim is removed and cdrskin gets an alternative (or probably just any symlink) named cdrecord.  Since the cdrecord name is being avoided in debian for legal reasons (TTBOMK), k3b should recognized cdrskin as a valid cdrecord replacement.

The possibly is a separate bug in which cdrskin, symlinks through alternatives is not recognized as the burner program unless wodim is removed (i.e. no choice of which burner program to use when there is more than one that is found by search; wodim is automatically chosen in that case).

#519200#10
Date:
2010-07-04 04:29:07 UTC
From:
To:
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.

#519200#17
Date:
2011-03-24 21:21:24 UTC
From:
To:
Dear Mark,
I'm not the original reporter, but I see this with 2.0.2-1, so don't close this
particular bug.

Kind regards,
Kai Wasserbäch

#519200#28
Date:
2011-06-14 05:53:02 UTC
From:
To:
Hi,

k3b should also recognize xorriso as valid low level app for burning
and image manipulation (cdrskin is a burner only app). Xorriso provides
some cdrecord and mkisofs compatible option interface:

xorriso -as cdrecord ...
(or call it via xorrecord symlink instead)

xorriso -as mksisofs ...
(or call it via xorrisofs symlink instead)

Another approach (which is more demanding) would be to use
libisoburn API: /usr/include/libisoburn/libisoburn.h
or even better the higher xorriso API:
/usr/include/libisoburn/xorriso.h
and link with libisoburn as well.

#519200#33
Date:
2014-07-29 19:07:52 UTC
From:
To:
Kernel: Linux (AMD64) release 3.9-0.bpo.1-amd64
Debian Wheezy 7.6 plus backports
KDE: 4.8.4
wodim (9:1.1.11-2)
xorriso (1.2.2-2)


Dear Developers for K3b,

Thank you for all your hard work and maintenance of the K3b package.  I use it
extensively and it usually works very well.

Recently, I began to use Blu-Ray discs (BD-R, BD-RE, and BD-RE DL) for backup
due to the size of my burgeoning data.  At this point I discovered that many
instabilities exist with cdrkit and growisofs relating to blu-ray discs of all
types.

Examples:
i) cannot detect the disc is already formatted
ii) cannot simultaneously format disc prior to sequential burn
iii) is highly unstable insofar as will "work" one in ten times
iv) size detection of disc and corresponding ISO/UDF image is erratic
v) cannot perform "backups" such as preserving permissions very easily
vi) will not burn the jigdo Debian 7.6 blu-ray discs (had to use xorriso on
the command line (this is probably the easiest method to recreate the problem)
---- BREAK ---

I removed wodim (cdrkit) and installed cdrskin (the wraparound cdrecord
replacement for xorriso) but K3b became even more unstable.  I only got K3b to
recognize cdrskin after I installed a Debian Alternatives manually.  K3b never
recognized cdrskin automatically.  When I completed the Alternatives it made
K3b less useful for buning NON-blu-ray discs; hence the reason I am submitting
this bug report/update.

Please consider integrating xorriso as a freestanding backend for K3b...

  OR

Please consider using the libburn4 library as mentioned in the report from Mr.
Danchev above.


Thank you,
Mr. C. Cropper