k3b stops responding on verification

[CH]

Binary package hint: linux-image-2.6.15-23-386

k3b writes just fine to a USB-attached CD/DVD-RW (Pioneer DVR-110D) drive, but stops responding on verification of data. I have been on the #ubuntu-bugs IRC channel & was advised by iegary to file this bug against the 23 kernel. (The 22 kernel was doing this two days ago ...until the late-day updates fixed it & is still working.)

The kernel-specific updates applied today were:

        linux-image-2.6.15-23-386 linux-restricted-modules-2.6.15-23-386

      The following packages were upgraded:

adept app-install-data example-content fontconfig initscripts k3b katapult kde-guidance kdebluetooth konq-plugins ksystemlog kubuntu-artwork-usplash kubuntu-default-settings libc6 libc6-dev libc6-i686 libfontconfig1 libglib2.0-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libk3b2 libkipi0 libscrollkeeper0 linux-386 linux-image-386 linux-restricted-modules-386 linux-restricted-modules-common lsb-base lsb-release mozilla-firefox-locale-en-gb ntpdate openssh-client qobex scrollkeeper sysv-rc sysvinit usplash vim vim-common vim-runtime xkeyboard-config xterm
      43 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.

[CH (yogich)]

For full details on a more elaborate test on the 22 kernel, two days ago, see:

http://pastebin.com/726685

[CH (yogich)]

Installed updated linux-image-386 (kernel-2.6.15-23-386) and the verification problem still exists in k3b, though rather than locking up it eventually finished with an error. Now, an interesting aside: I re-verified the DVD on which the backup was burned --using the app that did the backup-- and the verify succeeded.

[Jovan Svorcan (jova)]

Same problem with lg h55G and nec ad7170

[Rich Johnson (nixternal)]

Can this still be reproduced on Hardy or Gutsy? If so, it would be nice to know what the tests you performed were as the pastebin link no longer works. Thanks!

[MohamadReza Mirdamadi (mohi)]

also the same problem here. with Suzuki and liteon roms. It doesn't always happen, but sometimes!

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.