Ubuntu
brasero package

can't write a music disc because cdrdao is not installed

Bug #653140 reported by Jon Martin Berntsen on 2010-10-01

This bug report is a duplicate of: Bug #605603: brasero can't use cdrdao to burn cd. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	brasero (Ubuntu)	New	Low	Unassigned

Bug Description

Binary package hint: brasero

But the thing is that I just installed cdrdao via aptitude, but brasero can't see it. See the screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: brasero 2.30.2-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Fri Oct 1 18:53:23 2010
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
LANG=nb_NO.utf8
SHELL=/bin/bash
SourcePackage: brasero
XsessionErrors:
(polkit-gnome-authentication-agent-1:1361): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:1367): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Tags:

Revision history for this message

Jon Martin Berntsen (jberntsen) wrote on 2010-10-01:

Screenshot.png Edit (177.6 KiB, image/png)
Dependencies.txt Edit (5.7 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (31.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (774 bytes, text/plain; charset="utf-8")

Pedro Villavicencio (pedro) on 2010-10-04

Changed in brasero (Ubuntu):
importance:	Undecided → Low

Revision history for this message

Gary M (garym) wrote on 2010-11-14:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #605603, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.