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 380847 - Running ubuntu feisty/edgy mp3 file to audio cd doesn't work
Running ubuntu feisty/edgy mp3 file to audio cd doesn't work
Status: RESOLVED NOTABUG
Product: brasero
Classification: Applications
Component: general
0.5.1
Other All
: Normal normal
: 0.5
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-11-30 11:24 UTC by davmor2
Modified: 2007-02-17 21:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description davmor2 2006-11-30 11:24:26 UTC 
Please describe the problem:
I am now running Ubuntu feisty but was running edgy on a 64bit version.  Brasero in both cases didn't create an audio cd from some mp3 files I had, nor some ogg files.  The app allows me to drag and drop in place lists how long the cd will be but when clicking on burn the dialog appears but nothing happens.

Steps to reproduce:
1. install edgy amd 64 bit or feisty amd 64 bit
2. install brasero from backports 
3. open drag and drop files
4. click on burn
5. sit back for 4 hours before you give in and use serpentine


Actual results:
burn dialog appears as expected and then nothing happens.

Expected results:
I expect a delay and then for the bar on the meter to increase as the cd is burnt

Does this happen every time?
yes

Other information:
this bug is also reported on ubuntu malone number 72692.  I have been informed that brasero is not patched so is an upstream issue.
Comment 1 Philippe Rouquier 2007-02-17 12:20:25 UTC 
It could help if we had a log to see what's happening. Could you run brasero in a console with -g switch and send me all the output please ?
Thanks for reporting the bug.
Comment 2 davmor2 2007-02-17 19:29:50 UTC 
This is no longer the case with Feisty herd4 it may of been an implementation error.
Comment 3 Philippe Rouquier 2007-02-17 21:01:55 UTC 
good to know, I'll close the bug but feel free to re-open it if it comes up again.