[Bug 11701] New: Custom CD Information not stored consistently across GNOME Desktop
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Fri Jun 10 10:40:34 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=11701
Ubuntu | sound-juicer
Summary: Custom CD Information not stored consistently across
GNOME Desktop
Product: Ubuntu
Version: unspecified
Platform: i386
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: sound-juicer
AssignedTo: seb128 at ubuntu.com
ReportedBy: Thomas_Hinkle at alumni.brown.edu
QAContact: desktop-bugs at lists.ubuntu.com
Custom CD information is not stored consistently between the standard sound
programs -- namely, gnomecd and sound-juicer.
Also frustrating is the lack of a submit-to-database feature (like that in Grip)
in either of these programs.
IMO, if you can edit the data, you should be able to submit it back to the database.
So, here's a description of how to reproduce this bug.
1. Buy a brand new album from a local artist, unlikely to be in freedb's cddb
2. Put CD in the computer. Gnome-CD launches.
3. Click on the edit button in GNOME-CD and enter the CD information.
4. Decide to rip the CD for later listening. Open Sound-Juicer
5. The information's not there! I have to enter it again.
6. Decide to submit this information to the database for later use.
7. I have no way to do this!
8. Download grip, which, though it has a much clunkier interface, has a nice
"Submit info" button.
9. Once again, the information is not there! I thought .cddb/ stored all this
stuff by default.
10. Type the information a *third* time and submit it.
I am not sure where these different apps store their info, but I notice that I
have both a .cddb/ directory and a .cddb-slave directory, both created by grip,
which might make for some kind of standard.
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the desktop-bugs
mailing list