First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 50145
Alias:
Product:
Component:
Status: CLOSED
Resolution: LATER
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Dan Johnston <dejohnst@msn.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 50145 depends on: 51529 Show dependency tree
Bug 50145 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.




View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-05-05 16:24 0000 
It seems that the latest couple versions of rhythmbox has had xine support
removed the ebuilds.  Unfortunately, this is required to play .m4a files
(generated with iTunes).  I would request that xine support be enabled until
gst-plugins-faad can be used to play iTunes generated .m4a files.

The actual error rhythmbox throws up when trying to use gstreamer to play .m4a
files is that there is no handler for audio/x-m4a mime types.

Reproducible: Always
Steps to Reproduce:
1. emerge gstreamer-0.8.3
2. Try to import an iTunes generated .m4a file (you won't be able to)
3. If you already had one in your library, it won't play.

Actual Results:  
rhythmbox no longer supports .m4a files. 

Expected Results:  
rhythmbox should be able to use the xine backend to play .m4a files.

------- Comment #1 From Dan Johnston 2004-05-05 16:26:47 0000 ------- 
Oops, step one to reproduce should be emerge rhythmbox-0.8.3, not gstreamer...

------- Comment #2 From Yi Quang (RETIRED) 2004-05-05 18:03:25 0000 ------- 
xine support has been removed because there is a lack of maintainership for it.
 Please wait while we try to get this sorted out on our side.

------- Comment #3 From foser (RETIRED) 2004-05-06 06:05:17 0000 ------- 
and this is described in the ChangeLog
First Last Prev Next    No search results available      Search page      Enter new bug