Bug 684208 - amarok crashes on launch, libmtp related?
Summary: amarok crashes on launch, libmtp related?
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 684214
Blocks: 684224
TreeView+ depends on / blocked
 
Reported: 2011-03-11 13:14 UTC by Rex Dieter
Modified: 2012-08-06 19:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rex Dieter 2011-03-11 13:14:27 UTC
[rdieter1@localhost ~]$ amarok
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work 

(amarok:2367): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
QObject::connect: Cannot connect Meta::MediaDeviceHandler::incrementProgress() to (null)::incrementProgress()
QObject::connect: Cannot connect Meta::MediaDeviceHandler::endProgressOperation(QObject*) to (null)::endProgressOperation(QObject*)
Device 0 (VID=0b97 and PID=7762) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Device 1 (VID=045e and PID=0040) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
QObject::connect: Cannot connect Meta::MediaDeviceHandler::incrementProgress() to (null)::incrementProgress()
QObject::connect: Cannot connect Meta::MediaDeviceHandler::endProgressOperation(QObject*) to (null)::endProgressOperation(QObject*)
Device 0 (VID=0b97 and PID=7762) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Device 1 (VID=045e and PID=0040) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
ignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
inep: usb_get_endpoint_status(): Input/output error
outep: usb_get_endpoint_status(): Input/output error
usb_clear_halt() on IN endpoint: Numerical result out of range
usb_clear_halt() on OUT endpoint: Numerical result out of range
usb_clear_halt() on INTERRUPT endpoint: Numerical result out of range
LIBMTP libusb: Attempt to reset device
unnamed app(2366): Communication problem with  "amarok" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.amarok was not provided by any .service files" " 
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
Unable to start Dr. Konqi

Comment 1 Rex Dieter 2011-03-11 13:32:16 UTC
dmesg output includes a bunch of:

[ 1995.605454] usb 2-2.3.2: usbfs: process 2582 (amarok) did not claim interface 0 before use

Comment 2 Fedora End Of Life 2012-08-06 19:57:46 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2012-08-06 19:59:24 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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