Bug 726115 - Sansa Fuze misidentified (fixed upstream, likely rawhide)
Summary: Sansa Fuze misidentified (fixed upstream, likely rawhide)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: media-player-info
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 15:04 UTC by Michael Ekstrand
Modified: 2012-01-11 16:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-11 16:00:20 UTC
Type: ---


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 36321 0 None None None Never

Description Michael Ekstrand 2011-07-27 15:04:11 UTC
Description of problem:
My Sandisk Sansa Fuze media player is not identified as a media player.

Version-Release number of selected component (if applicable):
media-player-info-13-1.fc15.noarch

How reproducible:
Always.


Steps to Reproduce:
1. Plug in a first-generation (v1) Sansa Fuze in MSC mode

Actual results:
* Nautilus shows the Fuze as a generic USB storage medium
* Rhythmbox and Banshee do not notice that there is a media player

Expected results:
* Nautilus shows the Fuze as a media player (iPod icon in device list)
* Rhythmbox and Banshee detect the Fuze

Additional info:
This is due to an erroneous device ID in sandisk_sansa-fuze.mpi.  It has been reported upstream (https://bugs.freedesktop.org/show_bug.cgi?id=36321) and fixed;  I believe the fix is in release 14, so an update to that release should fix the problem (as would a backported patch, of course).  It looks like 14 is already in rawhide, but F15 still contains the version with incorrect data for the Fuze.

Comment 1 Michael Ekstrand 2012-01-11 16:00:20 UTC
Fixed in F16.

Comment 2 Michael Ekstrand 2012-01-11 16:04:56 UTC
Mis-closed - fixing resolution.


Note You need to log in before you can comment on or make changes to this bug.