only burns DAO, but some drives support only TAO

I tested with a fresh installation of Dapper on the second Harddrive of the same machine, the problem is still the same. So it occurs on a brand ne installed system as well. Nautilus cdrecord does't work but gnomebaker do.
Burner is a siemens-fujitsu 4x speed CD-writer.

I also can't burn CDs with Nautilus. My burner is a Hewlett Packard CD- Writer Plus. I also get an error. Developers which further information do you need?

BUT I can burn CDs with bonfire, but NOT with gnomebaker.

Is this still a problem for both of you? Can you please post the full error here. thomas your problem seems like it might be different than Sebastian's as he can burn with gnomebaker. I also dont think bonfire uses cdrecord but thats why im asking for the errors if it is still a problem if not please let me know. thank you for reporting this bug.

Lately I reinstalled the whole System with Xubuntu, so I dont't have nautilus anymore. Maybe I can try the Ubuntu live-CD to get the error message...

I have a new dvd burner now. It seems to work in Dapper.

Thanks for following up. Please reopen the bug if you have more information or it happens again.

Hi there.

Why did you set the status to "rejected"? Nautilus STILL have a bug in the burning CD routine for sure!
I think it's the combination of nautilus burning CD function together with some older CD-burner models what causes the touble.
I also can confirm, that creating the iso-fs is always working fine, so I am sure it doesn't have to do with mkisofs implementation of nautilus.
Unfortunately nautilus give no detailed log about what went wrong. Using cdrecord on the commandline burns the iso-image created by nautilus without problems.
Sorry at present I cannot give further glues, but if you could check the routine nautilus is using to operate whith its back end cdrecord may give you an idea of what is going wrong. Correct me if I am wrong but from my understanding if nautilus is only a frontend to mkisofs and cdrecord it should not have problems with the actual "burning" process since this is part of the cdrecord backend.
Anyway if someone can provide more details please check this.

It has probably be closed because you stated you stopped using nautilus and without having the submitter replying to the questions people who don't have the issue can't fix it.
Could you get a debug log?
- gnome-session-remove nautilus
- gconf-editor, activate /apps/nautilus-cd-burner/debug
- run nautilus from a command line
- try burning a CD

the log should be displayed on the command line

Since the release of breezy nautilus executes cdrecord with the option -t dao. In former releases the -t option was not applied and cdrecord assumes using tao mode on my drive. If cdrecord runs with the -t dao (on my computer) it says that this writing mode isn't supported and the whole writing process will fail.

It is since the release of dapper and not breezy (mistake in my previous post).

Carsten, the dao option is known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=345871
Are you sure that's what the bug is about? That was not mentionned by previous comments, what did you make think the issue is due to that?

I've set the debug variable in the key nautilus-burner via gconf-editor and had a look at ~./xsession-errors
nautilus-burner creates first an iso with mkisofs -> works ok
then it erases the cd content (if cd-rw): cdrecord blank=fast -> works ok
and then it uses the following command to write the iso image to the burner:
cdrecord fs=16m dev=/dev/hdc -dao driveropts=burnfree -v -data -nopad imagename.iso -> cancels with an error message that this writing mode isn't supported on my specific drive
In breezy nautilus-burner executes the same command without -dao -> works
If I type the same command in a terminal I'll get the same result, without -dao the image gets burned (this is under dapper); cdrecord then says no writing mode specified, assuming tao mode. Your link to bugzilla.gnome.org describes exactly the same problem. This is a problem that will concern mainly "old" burners, which don't support DAO mode. Mine is from 1999; a 4x4x24x Philips CDD-4201.

thank you for the details. My question was rather "how do you know that your issue is the same than the one from the original submitter"? You should probably open a different bug because it might be a different bug and having them mixed is just confusing for everybody

The Initial Reporter of this bug 'Sebastian' has for sure the same problem as I do, as he has a 'siemens-fujitsu 4x speed CD-writer' (probably OEM model of the CDD-4201) and I'm also able to burn with Gnomebaker.

Oh and furthermore he was also able to burn with breezy in nautilus (just like me).

Ok, thank you Carsten, it was not obvious by reading the previous comment. Marking as equivalent of http://bugzilla.gnome.org/show_bug.cgi?id=345871 upstream

Do you still experience the same problem in feisty/gutsy?