Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 235449 - libmtp 0.1.5 won't work with amarok
Summary: libmtp 0.1.5 won't work with amarok
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-05 20:40 UTC by Vlad Pescaru
Modified: 2008-08-02 23:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:28:28 UTC

Attachments (Terms of Use)

Description Vlad Pescaru 2007-04-05 20:40:24 UTC
The new version of libmtp (0.1.5) wont't work with amarok (it can't tranfer
files to my player anymore, although on the project page it's written that
"iRiver devices are expected to work now")
Maybe the amarok package needs to be rebuild

Comment 1 Gian Paolo Mureddu 2007-07-27 22:16:11 UTC
Install the libmtp-examples package, and try to run 'mtp-detect' (without the
quotes), it should be able to see your device. If libmtp can't detect your
device, then the problem lies within libmtp rather than amarok. see this bug,
maybe it is also affecting FC6:

Comment 2 Aurelien Bompard 2008-03-19 06:51:55 UTC
Hi, it's been a while... Do you still have this bug ? Does the mtp-detect
command work ?

Comment 3 Bug Zapper 2008-04-04 06:47:26 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 4 Bug Zapper 2008-05-06 19:28:26 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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