Bug 193344

Created attachment 130069 [details]
k3b debugging output

Created attachment 130086 [details]
k3b debug report

Created attachment 130087 [details]
k3b bug report

I lost some text when I added the second attachment. It looks like a bug in
bugzilla.

I will try again. My outside searches suggest that this bug has something to do
with the automount feature. I may be mistaken.

I added "/dev/cdrom /media/cdrecorder auto noauto,owner,rw 0 0" to the fstab and
it generated attachment #2 [details].

I added "/dev/hdc /media/cdrecorder auto noauto,owner,rw 0 0" to the fstab and
it generated attachment #3 [details].

#2 and #3 appear different.

Hope this helps.

Reassigning to Fedora Core/k3b.

Reassigning to Fedora Core/k3b.

First attachment: Sense Key: 0x3 Medium Error, Segment 0
Second attachment: Sense Key: 0x4 Hardware Error, Segment 0
Third attachement: disk may be mounted or used by another applicationI added 

Adding s.th. to fstab has no effect on CD burning.
I can burn fine with my 'HL-DT-ST' 'DVDRRW GWA-4161B' '1.15'

Good Day . . .

Thank You for the reply.

While checking your bugzilla returned no hits on this problem, checking the
redhat forum yielded about 20 - 30 hits on the search item - "k3b exclusively"

The problem seems to be universal with no real suggestions for a bug solution.

For your attention.

Hope this helps.

Well, cdrecord cannot tell, which application is blocking the device.

Good Day . . .

Fiddling around with different types of cd/dvds and umount and mount leads me to
believe that possibly the automount feature may have a bearing on the bug.

Here are some more facts:

- I can insert a cd-rw and umount it prior to k3b and I can erase the disk.
- I cannot write to the disk after because k3b auto ejects the disk after the
erase and subsequently the cd-rw is remounted.
- I cannot umount a blank disk because the menu from secondary clicking on the
icon does not include an unmount option. If it is mounted then nothing shows
this from my limited technical knowledge.

I searched unsuccessfully for instructions about how to disable automount on the
cd/dvd. Maybe RedHat can point me in the right direction and I can help debug
this issue?

Hope this helps.

KDE or Gnome?

Good Day . . .

KDE

do as root:
# rpm -e autorun
and as a user (also in KDE):
$ gnome-volume-properties

Good Day . . .

Thank You for the reply.

All bad news.

- I erased autorun and started gnome-volume-properties as user
- Received error message about invalid MIT-MAGIC-COOKIE-1
- Searched - common problem across distros
- Something to do with system access (input/output error ?)
- tried k3b - same symptoms
- erased autofs since this has something to do with automount
- tried k3b - same symptons
- installed autorun & autofs
- tried k3b - something different
  same non writing but no closing error messages
  message in info box says "input/output error"
  k3b advises "Success" on closing write process
- started gnome-volume-properties
  no error message - gui appears
- removed all removeable media from automount
- tried k3b
  same non-writing
  same "Success" message on closing write process
- tried nautilus
  same non-writing
  same "Success" message on closing write process

I need the dvd so I will keep looking for a solution.
Hope your keep helping.
So far, I have lost 17 dvds - k3b will not allow simulate on dvds.

Hope this helps.

  

Try to use growisofs from dvd+rw-tools. k3b _should_ automatically use
growisofs, if it is installed. growisofs normally burns DVD just fine, besides
of some Plextor drives.

I will also release a new cdrecord version, which hopefully fixes some bugs.

Thank You for the reply.

Your suggestion generated essentially the same error.

I used "growisofs -Z /dev/hdc -R -J /home/. . ."
The following errors appeared:
  :-[ WRITE@LBA=120h failed with SK=4h/ASC=08h/ACQ=03h]: Input/output error
  builtin_dd: 288*2KB out @ average 0.0x1385KBps
  :-( write failed: Input/Output error

Hope this helps.

ps: I am now up to 22 dvd coasters. May I suggest that simulation for a dvd be
included at the earliest opportunity. :-)

here is a new cdrecord you can try.. you may try "-dummy", which works, if your
drive supports it.
http://www.redhat.com/archives/fedora-test-list/2006-May/msg00368.html

Good Day . . .

Thank You for the reply.

I regret to inform you that after the update was installed k3b still exhibited
the same symptoms - no writing followed by a successful message.

My last successful DVD write was a backup data disk on 6 April 2006. I have
tried to reverse all the personal changes that I have made to KDE and GDMSetup
but the bug is still present. I can still watch movies and copy files from the
DVD. Strange problem.

I'll put one of my earlier distros on a removeable hard drive and see if the
problem is present.

Hope this helps.

Good Day . . .

Good news and bad news. I never discounted that the drive has become worn out so
I took out a Sony dru-810a from my other machine and replaced the lg. The Sony
drive works! I successfully made a file backup on DVD.

To be sure about the worn out aspect I installed the lg into the Sony slot on my
other Suse 10.0 machine. Bad news is that it works! I used my last DVD and it
came out good.

I realise that you know far more about this subject than I do but I did locate
two online messages on this subject. The first contains an awful lot of
technical information and appears to be a complete duplicate of my bug.
Unfortunately no solution is found.

http://lists.debian.org/debian-amd64/2006/03/msg00169.html
http://k3b.plainblack.com/message-board/problem-with-dma

Hope this helps.

Please test:
https://www.redhat.com/archives/fedora-test-list/2006-June/msg00051.html

Good Day . . .

Thank You for the information.

The link the above link directed me to was for a file titled "cdrtools." The
next link to i386/ did not contain a file entitled "cdrtools" but it did contain
a file titled "cdrecord" with the same version and revision numbers as cdrtools.

Are we missing a file or is the name wrong?

Hope this helps.

Well... it's there...
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/5/i386/cdrecord-2.01.01.0.a10-0.FC5.1.i386.rpm

Good Day . . .

Thanks for the reply. Sorry for the delay but I have been away.

The point that I was making was that the link's file's title was 'cdrtools' but
the revision number belonged to 'cdrecord.' I downloaded that file.

It appears to work. When I exchanged the drives. The old drive did not work at
all on this machine. The new drive was recording backups to CD but would not
close the CD making it unreadable. A DVD backup worked well.

The new download seems to have solved the CD recording issue. Unfortunately it
was my last CD disc. I have about 25 DVD and CD coasters. I live in the country
so getting a new supply will have to wait for the 23rd of June and a special at
one of the electronics stores.

Thank You for the help. I really appreciate it.

If I can do anything to assist let me know.

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.