libmtp crashes (1.5 backport request)

Bug #121087 reported by jane
6
Affects Status Importance Assigned to Milestone
Feisty Backports
Invalid
Undecided
Unassigned
libmtp (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,
I have an iriver clix, and my libmtp doesn't work with it properly. but i think from reading the libmtp pages, that this is exactly the problem fixed between 1.3 (in feisty) and 1.5 (now in gutsy). Could there please be a backport of this to feisty?
thanks!!

Revision history for this message
Vincent Legout (vlegout) wrote :

suscribe feisty-backports

Vincent Legout (vlegout)
Changed in libmtp:
status: New → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

Backports are for new features, not bug fixes. Are their new features that would warrant a backport?

Changed in libmtp:
status: Confirmed → Invalid
Changed in feisty-backports:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Feisty Backports because there has been no activity for 60 days.]

Changed in libmtp:
status: Invalid → Incomplete
Changed in feisty-backports:
status: Invalid → Incomplete
Changed in libmtp:
status: Incomplete → Invalid
Revision history for this message
jane (launchpad-diversity-radio) wrote :

Scott- sorry I didn't see the quesion a month or so back.
Are there new features?.... well, it depends whether you count on getting anything to recognise my hardware as a new feature. obviously it would be a massive new feature for me (and would allow me to have a whole new feature in my pocket...) but, unfortunately probably version 1.5 is a bug fix over 1.3. The changelog summaries detail this:
http://libmtp.sourceforge.net/index.php?page=download

On the other hand, perhaps someone would consider 0.2.1 to have "new features" worthy of a backport, if version 0.1,5 doesn't cut the mustard?

Revision history for this message
jane (launchpad-diversity-radio) wrote :

I've just seen that a 0.2.1 backport request has also been made: https://bugs.launchpad.net/feisty-backports/+bug/135363

pinzia (pinzia)
Changed in feisty-backports:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.