Bug 137250
Summary: | gnome-vfs2 won't build cdda module due to libparanoia location | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John Thacker <johnthacker> |
Component: | gnome-vfs2 | Assignee: | Alexander Larsson <alexl> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | rawhide | CC: | abo, bnocera, drago01, pas37, rbultje, rodgerr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-05 19:30:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 144803 |
Description
John Thacker
2004-10-26 22:38:59 UTC
Still current for FC3, and it will create bazillions of warnings when you add new files in Totem for example. "It doesn't seem to actually break anything, mind you, just these warnings." It do. Totem is unable to play audio cds because of this. You're right, you're right. It won't play audio CDs because of this, at least the FC3 version. It seemed to work for me with a previous Rawhide version when I made this bug, but the FC3 totem won't play audio CDs. Maybe I had some components from the xine version around. Changing severity from low to normal since playing audio CDs doesn't work; it is a major loss of function, but there are other ways to play audio CDs. (Totem does play audio CDs without the need for the audio cables attached though I believe; are there as easy work arounds for that?) So, there are three ways to get this to work: 1. Patch the gnome-vfs2 sources so that it looks for the cdparanoia header files in /usr/include/cdda 2. Patch the gnome-vfs2 sources so that it works whether the cdparanoia header fiels are in the RedHat location or in the "normal" location. This would be a little more annoying, but we could adapt what grip does to work around it. 3. Put the cdparanoia headers back in /usr/include. Note that we can optionally not ship the "utils.h" header, since grip doesn't seem to need it anymore. In other words, bug #38223 is no long pertinent, so we should be free to move it back. I just tested compiling grip without utils.h present-- no problems. It would also be nice to fix 102754 as well. Boy has it been far too long in between cdparanoia releases. it can also be fixed be adding some links.... Isn't it about time that this product was repackaged and the bug got fixed? I like gnome, but I am tired of having to juice all my CDs to play them from the Hard Drive. If it's really hampering your usage of Totem, the quick fix is to run this as root: perl -pi~ -e "s,cdda,#cdda," /etc/gnome-vfs-2.0/modules/default-modules.conf Setting the priority to high, the fix is a recompile (or small patch) away. disabling the module wont help people play their cds. its been more than 1 month after the last comment and still no solution? if its 'just a recompile', why not do it now? When will it fix?? any fix in for fc4? or will we have to wait for fc5? OK, this is ridiculous. The cdda module doesn't need to be built, exactly, as it's deprecated. It ought to be at least commented out, though. However, commenting it out *won't* fix totem. There's further totem weirdness. If I put an audio CD in the drive, totem plays it perfectly well with "totem cdda://" no problem. However, if I just launch totem, the "Play Audio Disc" menu item is greyed out and unusable. I added more information in bug 144803 OK, I think I'm convinced from looking elsewhere that totem not supporting playing CDs in the GUI is intentional. Don't know that I agree, but whatever. In any case, the cdda module still ought to be commented out to remove the warning message. Since the cdda module is deprecated upstream, I'm closing this bug and starting a new one, bug 184061, with a more accurate description of the problem. (I.e., the module should definitely just be commented out.) *** This bug has been marked as a duplicate of 184061 *** |