Bug 667062

Summary: add support for sansa fuze+
Product: [Fedora] Fedora Reporter: Jiri Moskovcak <jmoskovc>
Component: libmtpAssignee: Linus Walleij <triad>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: dfediuck, triad
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-31 22:02: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:
Attachments:
Description Flags
patch to add support for few new devices none

Description Jiri Moskovcak 2011-01-04 09:40:01 UTC
Description of problem:
my sansa fuze+ is not recognized by libmtp in Fedora

Version-Release number of selected component (if applicable):
libmtp-1.0.3-6

How reproducible:
100%

Steps to Reproduce:
1. connect sansa fuze+ to pc
2. run mtp-detect or mtp-connect

  
Actual results:
error message saying something about UKNOWN id pops out, suggesting me to contact libmtp devels...

Expected results:
fuze+ working over MTP

Additional info:
there is a patch in Ubuntu package which adds support for this player

Comment 1 Jiri Moskovcak 2011-01-04 09:44:40 UTC
Created attachment 471626 [details]
patch to add support for few new devices

  * New devices:
    - Nokia 2710 0421:02c1.
    - Nokia 5230 0421:02e2.
    - SanDisk Sansa Fuze+ 0781:74e0
    - Sony Walkman NWZ-B153F 054c:04be
    - Sony Walkman NWZ-E354 054c:04cb

I tested just the support for sansa fuze+ and it seems to work
Patch was created against the Fedora git.

Comment 2 Linus Walleij 2011-01-04 16:14:11 UTC
Wella the proper thing for me to do is roll a new release of libmtp I think (since I'm the libmtp maintainer too...)

Comment 3 Jiri Moskovcak 2011-01-05 10:36:58 UTC
(In reply to comment #2)
> Wella the proper thing for me to do is roll a new release of libmtp I think
> (since I'm the libmtp maintainer too...)

Even better ;)

Thank you.