Bug 671492 - Amarok crashes after libmtp update
Summary: Amarok crashes after libmtp update
Keywords:
Status: CLOSED DUPLICATE of bug 671361
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-21 16:25 UTC by Martin Kho
Modified: 2011-01-22 01:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-22 01:17:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
KCrash report (5.42 KB, text/plain)
2011-01-21 16:25 UTC, Martin Kho
no flags Details

Description Martin Kho 2011-01-21 16:25:29 UTC
Created attachment 474641 [details]
KCrash report

Description of problem:

After libmtp was updated to version 1.0.4-2 amarok crashes. Attached is a backtrace with all debuginfo-packages installed (three stars in KDE Crash Handler). This trace is created by Dr. Kongi from inside gdb. Outside gdb Dr. Kongi was "unable to start". Don't know why. Hope the backtrace is useful.

Version-Release number of selected component (if applicable):
* amarok-2.4.0-1.fc15.x86_64
* libmtp-1.0.4-2.fc15.x86_64

How reproducible:
Every time Amarok is started. 

Steps to Reproduce:
1. Start Amarok -> splash screen -> crash
  
Actual results:
Amarok crashes

Expected results:
Amarok doesn't crash 

Additional info:
I've filed a bug report [1] for libmtp, because the development team asked to do so because of the UNKNOWN device.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=671361

Comment 1 Kevin Kofler 2011-01-22 01:17:57 UTC
The crash is within libmtp code, the previous version worked, and the warnings on the console look very suspicious, so I'm fairly sure this crash is libmtp's fault.

*** This bug has been marked as a duplicate of bug 671361 ***


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