Your message dated Sun, 4 Jul 2010 14:46:22 +1000
with message-id <[email protected]>
and subject line K3b 2.0.0-1 uploaded to unstable - bug ping
has caused the Debian Bug report #434658,
regarding k3b: verification doesn't work when burning video dvds
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
434658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=434658
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: k3b
Version: 1.0.2-1
Severity: normal
K3B includes an option to "verify written data" but it doesn't work.
Sometimes K3B fails with an error message while at other times it hangs
(both at the 50% mark when beginning the verify stage).
I have only tested this behaviour on burning video DVDs so I don't know
if it happens on other types of media or not. Sorry, I don't have an
error message for you, but the last time I burned a DVD, it hung. I am
sure that it is not a hardware problem however, because NeroLinux
v2.1.0.2 is able to verify OK when I use it instead.
I can also confirm the bug about K3B turning DMA off on the device.
Here's some stuff from the messages log that may be relevant:
Jul 25 10:11:35 localhost kernel: hdc: DMA timeout retry
Jul 25 10:11:40 localhost kernel: hdc: status error: status=0x58 {
DriveReady Se
ekComplete DataRequest }
Jul 25 10:11:40 localhost kernel: ide: failed opcode was: unknown
Jul 25 10:11:40 localhost kernel: hdd: dma_intr: status=0x51 {
DriveReady SeekCo
mplete Error }
Jul 25 10:11:40 localhost kernel: hdd: dma_intr: error=0x84 {
DriveStatusError B
adCRC }
Jul 25 10:11:40 localhost kernel: ide: failed opcode was: unknown
Jul 25 10:30:06 localhost kernel: hdc: command error: status=0x51 {
DriveReady SeekComplete Error }
Jul 25 10:30:06 localhost kernel: hdc: command error: error=0x50 {
LastFailedSense=0x05 }
Jul 25 10:30:06 localhost kernel: ide: failed opcode was: unknown
Jul 25 10:30:07 localhost kernel: ATAPI device hdc:
Jul 25 10:30:07 localhost kernel: Error: Illegal request -- (Sense
key=0x05)
Jul 25 10:30:07 localhost kernel: "28 00 00 00 04 ee 00 00 02 00 00 00
00 00 00 00 "
Jul 25 10:30:07 localhost kernel: end_request: I/O error, dev hdc,
sector 5048
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages k3b depends on:
ii cdparanoia 3.10+debian~pre0-5 audio extraction tool for sampling
ii cdrdao 1:1.2.2-6 records CDs in Disk-At-Once (DAO)
ii genisoimage 9:1.1.6-1 Creates ISO-9660 CD-ROM filesystem
ii kdebase-bin 4:3.5.7-2 core binaries for the KDE base mod
ii kdelibs-data 4:3.5.7.dfsg.1-1 core shared data for all KDE appli
ii kdelibs4c2a 4:3.5.7.dfsg.1-1 core libraries and binaries for al
ii libacl1 2.2.42-1 Access control list shared library
ii libart-2.0-2 2.3.19-3 Library of functions for 2D graphi
ii libattr1 1:2.4.32-1.1 Extended attribute shared library
ii libaudio2 1.9-2+b1 The Network Audio System (NAS). (s
ii libc6 2.6-2 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst
ii libdbus-qt-1-1c2 0.62.git.20060814-2 simple interprocess messaging syst
ii libdvdread3 0.9.7-3 library for reading DVDs
ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li
ii libfontconfig1 2.4.2-1.2 generic font configuration library
ii libfreetype6 2.3.5-1+b1 FreeType 2 font engine, shared lib
ii libgamin0 [libfam0] 0.1.8-2 Client library for the gamin file
ii libgcc1 1:4.2-20070712-1 GCC support library
ii libhal1 0.5.9.1-2 Hardware Abstraction Layer - share
ii libice6 1:1.0.3-2 X11 Inter-Client Exchange library
ii libidn11 0.6.5-1 GNU libidn library, implementation
ii libjpeg62 6b-13 The Independent JPEG Group's JPEG
ii libk3b3 1.0.2-1 The KDE cd burning application lib
ii libmusicbrainz4c2a 2.1.5-1 Second generation incarnation of t
ii libpng12-0 1.2.15~beta5-2 PNG library - runtime
ii libqt3-mt 3:3.3.7-5 Qt GUI Library (Threaded runtime v
ii libsm6 2:1.0.3-1+b1 X11 Session Management library
ii libstdc++6 4.2-20070712-1 The GNU Standard C++ Library v3
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxcursor1 1:1.1.8-2 X cursor management library
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii libxft2 2.1.12-2 FreeType-based font drawing librar
ii libxi6 2:1.1.1-1 X11 Input extension library
ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library
ii libxrandr2 2:1.2.1-1 X11 RandR extension library
ii libxrender1 1:0.9.2-1 X Rendering Extension client libra
ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii wodim 9:1.1.6-1 command line CD/DVD writing tool
ii zlib1g 1:1.2.3.3.dfsg-5 compression library - runtime
Versions of packages k3b recommends:
ii dvd+rw-tools 7.0-7 DVD+-RW/R tools
ii kcontrol 4:3.5.7-2 control center for KDE
ii kdebase-kio-plugins 4:3.5.7-2 core I/O slaves for KDE
pn vcdimager <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
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. Upstream have claimed that your
bug has been fixed-upstream via the forwarded link from to the upstream KDE
Bugzilla, thus we are now closing your Debian report.
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 has been resolved with version 2.0.
If your bug has been resolved then there is no need for any further action you
your part.
If your bug has not been resolved, then please first check upstream reports for
the reason upstream have closed their report. Then please add further comments
against the upstream report and if necessary reopen both the upstream and
Debian bug reports.
https://bugs.kde.org/buglist.cgi?quicksearch=k3b
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
[email protected].
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: [email protected] any
reports you file in the Debian Bug Tracking system so that upstream
are aware of the issue you are reporting.
-----------------------------------------
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
