Activity log for bug #267101

Date Who What changed Old value New value Message
2008-09-06 11:05:33 KevinM bug added bug
2008-09-06 11:05:33 KevinM bug added attachment 'Disk speed2.png' (Disk speed2.png)
2008-09-17 17:37:50 Wouter Stomp None: bugtargetdisplayname Ubuntu nautilus-cd-burner (Ubuntu)
2008-09-17 17:37:50 Wouter Stomp None: bugtargetname ubuntu nautilus-cd-burner (Ubuntu)
2008-09-17 17:37:50 Wouter Stomp None: statusexplanation
2008-09-17 17:37:50 Wouter Stomp None: title Bug #267101 in Ubuntu: "Inconsistant burn settings when burning CD ISO files" Bug #267101 in nautilus-cd-burner (Ubuntu): "Inconsistant burn settings when burning CD ISO files"
2008-10-03 08:46:30 Sebastien Bacher nautilus-cd-burner: status New Incomplete
2008-10-03 08:46:30 Sebastien Bacher nautilus-cd-burner: assignee desktop-bugs
2008-10-03 08:46:30 Sebastien Bacher nautilus-cd-burner: importance Undecided Low
2008-10-03 08:46:30 Sebastien Bacher nautilus-cd-burner: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? * Did you use the same discs each time? Could you run /usr/lib/nautilus-cd-burner/list_cddrives after putting the CD in the drive? This will help us to find and resolve the problem.
2008-10-04 17:58:49 KevinM bug added attachment 'CD-burn-problems.tar.gz' (Screenshots and logs.)
2008-11-18 13:23:29 Sebastien Bacher nautilus-cd-burner: status Incomplete Invalid
2008-11-18 13:23:29 Sebastien Bacher nautilus-cd-burner: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? * Did you use the same discs each time? Could you run /usr/lib/nautilus-cd-burner/list_cddrives after putting the CD in the drive? This will help us to find and resolve the problem. 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.