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 506398 - toc image type not autodetected correctly
toc image type not autodetected correctly
Status: RESOLVED FIXED
Product: brasero
Classification: Applications
Component: general
0.7.0
Other Linux
: Normal normal
: 0.7
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-12-30 11:08 UTC by Denis Leroy
Modified: 2008-07-06 13:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Denis Leroy 2007-12-30 11:08:41 UTC 
After choosing the recently opened project "brasero.toc", brasero shows me the "Image burning setup" dialog with "brasero.toc" as the Path, and "Let brasero choose" as the image type. Clicking on burn yields an error message "The image can't be burnt, it doesn't appear to be a valid image or cue file". I have to manually select "toc image (cdrdao)" in the image type pull-down menu for the burn process to work correctly. Something wrong with the image type auto-detection ?
Comment 1 Luis Medinas 2008-04-16 18:52:22 UTC 
Philippe can you take a look at this ?
Comment 2 Philippe Rouquier 2008-04-22 18:06:46 UTC 
It is probably a problem with gnome-vfs. In 0.7 we rely on this library to retrieve the mime types (GIO in 0.8). So the problem lies there. Brasero installs some files to describes .toc files.
I'll check on my install of fedora.
Comment 3 Philippe Rouquier 2008-07-06 13:35:56 UTC 
Fixed in trunk.
I added an internal function to detect cuesheet types which is used whenever a cuesheet type is detected by GIO so as to check the type validity and correct it if needed.
Of course, feel free to reopen this bug if it doesn't work for you.