BurnProof not enabled in Nautilus

[Caleb Marcus]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks, I guess I will ask that question in the bug thread. I've never
noticed a degradation in quality when using BurnProof, and evidently
neither have the makers of the most popular Windows CD burners in
addition to GnomeBaker and Brasero, which all use it by default. I
have checked, and the gconf key is indeed not set in Gutsy.

The reason I asked this list is because someone in #ubuntu-desktop on
Freenode told me to contact the list for information on how to get the
debug information. I am sorry if this was the wrong place to ask.

Jo-Erlend Schinstad wrote:
> On 16/07/07, Caleb Marcus <caleb.marcus at gmail.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> When I burn a CD with Nautilus, it fails about 25% of the time. Other
>> burners are not affected. I found that this is because by default, the
>> gconf key /apps/nautilus-cd-burner/burnproof is not set by default. I
>> looked at the bug report (
>
> Well, according to developers that are working on this, using
> burnproof always degrades performance. So, would you prefer it if the
> quality of 75% of the cds for 100% of the users were lowered, or 25%
> of 25% to be problematic? That question probably isn't quite as easily
> answered as it sounds like. However, it seems everyone agrees that it
> should be enabled by default when using the cd-burner in nautilus.
>
>> http://bugzilla.gnome.org/show_bug.cgi?id=137099 ) and I really think
>> that the reasons they say they don't have it enabled by default are
>> invalid. Every CD burning program I've tried, including on Windows,
>> has had buffer underrun protection enabled by default. If a user
>> switches to Ubuntu to find that the burner will not function correctly
>> all the time like it did in Windows, it will degrade their experience.
>
> The bug report you pointed to, was not a Ubuntu bugreport, was it? It
> was a gnome bugreport. I'm not sure if you're aware of this, but
> Ubuntu has it's own bug tracker on launchpad.net. This link points to
> Ubuntus work on your feature request;
> https://bugs.launchpad.net/nautilus-cd-burner/+bug/18298
>
>> Comment 8 in the bug report requests some debug info, and I'm
>> wondering if this will help get the bug fixed, and how I can get that
>> info. It's been a known problem for several releases of Ubuntu, and
>> it's disappointing to see that nothing has been done about it.
>
> Did you notice how people have been asking for more information about
> this bug since february without anyone, like you, having answered the
> questions? Why should they prioritize a bug that nobody seems to care
> about? If you need to answer a question in order to ask a question, do
> so where the question is asked. That is, in the bug thread. Also, keep
> in mind that when you mail thiese questions here, instead of doing so
> in a post to the bug tracker thread, they are not seen in relation to
> the bug and will not be as useful. However, as Sarah Hobbs write when
> she closed the bug, you're welcome to reopen it providing you're
> willing to give the information needed to close the bug.
>
> « Sarah Hobbs  said on 2007-06-24:  (permalink)
>
> We are closing this bug report as it lacks the information, described
> in the previous comments, we need to investigate the problem further.
> However, please reopen it if you can give us the missing information
> and don't hesitate to submit bug reports in the future.»
>
> Oh, and have you confirmed that this is still an issue in Gutsy? I
> don't think this will be changed in Fiesty.
>
>
> I hope this was helpful.
>
> Jo-Erlend Schinstad
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGm4jFX2SHyykm3j4RAnFeAKDMIAZdmhkbd7vPuI/HRxo9WfWbogCeIf6o
Bcegdod3ytcXC7nIPSPd+58=
=WrF3
-----END PGP SIGNATURE-----