After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 317607 - time incorect on cd-burning (1Milion hours reported)
time incorect on cd-burning (1Milion hours reported)
Status: RESOLVED FIXED
Product: nautilus-cd-burner
Classification: Deprecated
Component: cd-burner
2.12.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-30 14:58 UTC by Sebastien Bacher
Modified: 2006-09-29 22:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
Sample Debug Output (3.27 KB, application/x-bzip)
2005-11-28 13:42 UTC, Nicholas Doyle
Details

Description Sebastien Bacher 2005-09-30 14:58:29 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=16696

"Time incorect on cd-burning (1Milion hours reported until cd is written)
this with nautilus from 28 Sep 2005 (breazy version updated to that day)

http://bugzilla.ubuntu.com/attachment.cgi?id=4232
screen shot with 1Milion

screen shot with 1Milion until writing is finished "
Comment 1 William Jon McCann 2005-09-30 15:13:33 UTC
Could you post the commandline output with the debug gconf key enabled?
Comment 2 Sebastien Bacher 2005-10-10 17:21:19 UTC
Distro comment:

"No errors in debug mode 
Here is the relevant section , after iso file is created and just before it starts
to write with growisofs (maybe is an undefined variable somewhere)

make_iso stderr: Total translation table size: 0
make_iso stderr: Total rockridge attributes bytes: 28083
make_iso stderr: Total directory bytes: 55296
make_iso stderr: Path table size(bytes): 176
make_iso stderr: Max brk space used 41000
make_iso stderr: 2149301 extents written (4197 MB)
make_iso stdout: HUP
make_iso stderr: HUP
launching command: growisofs -dvd-compat -Z /dev/hdc=/tmp/image.iso.meeDJe
growisofs stdout: Executing 'builtin_dd if=/tmp/image.iso.meeDJe of=/dev/hdc
obs=32k seek=0'
growisofs stderr: /dev/hdc: "Current Write Speed" is 4.1x1385KBps.
growisofs stdout:    1277952/4401768448 ( 0.0%) @0.0x, remaining 229:33
growisofs stdout:    9404416/4401768448 ( 0.2%) @1.7x, remaining 62:16
growisofs stdout:   22249472/4401768448 ( 0.5%) @2.7x, remaining 36:05
growisofs stdout:   35160064/4401768448 ( 0.8%) @2.7x, remaining 28:58
growisofs stdout:   48365568/4401768448 ( 1.1%) @2.8x, remaining 27:00
growisofs stdout:   61767680/4401768448 ( 1.4%) @2.8x, remaining 24:35
growisofs stdout:   75366400/4401768448 ( 1.7%) @2.9x, remaining 22:57
growisofs stdout:   88571904/4401768448 ( 2.0%) @2.8x, remaining 22:43"
Comment 3 William Jon McCann 2005-10-11 15:43:51 UTC
Does this occur with both CD and DVD burning?  The initial report is for CD
burning but the debug output is from DVD burning.  Does this occur with CVS
HEAD?  Does the time remaining report correctly once the writing has started?
Comment 4 Sebastien Bacher 2005-10-20 14:13:26 UTC
reply on the distibution bug: 

"1. Yes with both dvd/cd burning 
2.Maybe i should check out HEAD version 
3.Time is correct once writing is started "


Is there some CVS changes supposed to fix that? I can do a CVS package for the
bug submitter if that's the case
Comment 5 William Jon McCann 2005-10-20 14:30:35 UTC
I've just merged the following into 2-12 from HEAD.  It may fix it.  If you are
able to have the submitter test it that would be great.  Thanks.

2005-10-20  William Jon McCann  <mccann@jhu.edu>

	* nautilus-burn-recorder.c (compute_time_remaining): 
	Don't use bps less than or equal to one.  Merged from HEAD.
Comment 6 Nicholas Doyle 2005-11-28 13:42:57 UTC
Created attachment 55318 [details]
Sample Debug Output

I am having the same problem with the time remaining dialog. I think the
problem is that (in my case) cdrecord is used as opposed to growisofs to write
the CD. cdrecord gives different debug output and perhaps it is being read
improperly and is giving the wacky times. I will attach a sample of my debug
output when burning a CD.
Comment 7 Sebastien Bacher 2006-02-19 21:58:35 UTC
Distro comment:

"I have noticed this problem as well (I am running an up-to-date dapper). Seems that the upload didn't fix the problem.

This happens while preparing to burn : when the burning has begun, the time is well updated and perfectly normal.

Marking the bug as Confirmed."
Comment 8 William Jon McCann 2006-09-29 18:32:57 UTC
Any chance we've fixed this in 2.16?  I still don't see it.
Comment 9 Sebastien Bacher 2006-09-29 22:05:40 UTC
comment from the distro bug: "I have upgraded to dapper (apt-get dist-upgrade) and bug seems to be fixed in dapper", marking as fixed