in path /apps/nautilus-cd-burner of gconf-editor option burnproofis not checked

Bug #102087 reported by monoworks
4
Affects Status Importance Assigned to Milestone
nautilus-cd-burner (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gconf-editor

In path /apps/nautilus-cd-burner of gconf-editor option burnproofis not checked. This is indirect an bug, no application crash, but a serious usability bug. Why should the option "burnproof" not be checked, if burner is capable and cd burn program also? Also from k3b I know it is no harm using burnproof even the cd/dvd burner is not capable of.

Sorry, gnomes usability is great, but this bug has now been several releases around and I am wondering, why this option has never been set.

ProblemType: Bug
Architecture: i386
Date: Mon Apr 2 22:42:40 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gconf-editor
Package: gconf-editor 2.18.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gconf-editor
ProcCwd: /home/dogbert
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8@euro
SourcePackage: gconf-editor
Uname: Linux beagle 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Revision history for this message
monoworks (launchpad-monoworks) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. nautilus-cd-burner does use burnproof when recording datas by default, no need to set this key. Does it work not correctly on your configuration? Could you describe a way you trigger the bug?

Changed in gconf-editor:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
monoworks (launchpad-monoworks) wrote :

Errrr, ok, there might be mislead information. Given your information, this bug report seems have to be created erroneus.

I know from earlier gnome-desktops that nautilus cd burner had to have this option in gconf activated only just to use burnproof. That is why I did not try burning without changing the setting. Burning with this setting worked without problem.
So my question: If without setting this option nautilus cd burner would have chosen burnproof? why is there an setting in gconf with the unchecked option burnproof, if it seems to be ignored? Is it just a now left over option in gconf which has been superseeded by the automatic selection of the right option?

Sorry for the more of work I have produced. This option in gconf is a little bit confusing.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The gconf key is used by libnautilus-burn, applications then a free to respect it. The nautilus-cd-burner code use burnproof on data CD anyway, that might not be the case of other clients. Settings the key will also make the option being used when recording an audio CD

Changed in nautilus-cd-burner:
status: Needs Info → Rejected
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

I don't understand why this bug has been rejected. You told us that the burnproof is only used on data CDs (does this include burning an iso?)
Why audio CDs are "left alone"?

Revision history for this message
Sebastien Bacher (seb128) wrote :

because the burnproof create glitches on audio CD and you usually rather want to use a slower speed rather than adding noises

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.