Summary: | Amarok crash on external USB device | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Valentin Rusu <valir> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | tmax26 |
Priority: | NOR | ||
Version: | 2.3.2 | ||
Target Milestone: | 2.4.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Valentin Rusu
2010-12-21 21:16:55 UTC
Sorry, but your backtrace is not useful, as you are lacking debugging symbols. If you can reproduce this bug, please check here on how to get a valid backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Hello Myriam, Please note that I used DrKonqi to submit this report. I used it to install the needed debugging symbols and It seemed happy when I submitted it, as it displayed the three stars. As I see, the Thread number 1 has plenty of KDE debugging info. Do you want me to install the libc debugging symbols also ? The problem is you don't have debugging symbols for Amarok installed AFAICS. Created attachment 55739 [details]
New crash information added by DrKonqi
amarok (2.3.2) on KDE Platform 4.5.5 (KDE 4.5.5) "release 1" using Qt 4.6.3
- What I was doing when the application crashed:
I was listening music with amark then I connect my sony walkman usb device and amarok crash, when I try to start again amarok until the sony walkman are connected it crash again.
-- Backtrace (Reduced):
#6 usb_bulk_io (dev=0x0, ep=<value optimized out>, bytes=0x18f1920 "\020", size=16, timeout=10000) at core.c:751
#7 0x00007f375c2c5995 in ptp_write_func (size=16, handler=0x7f375be926f0, data=0x18ff940, written=0x7f375be92708) at libusb-glue.c:880
#8 0x00007f375c2c5f4b in ptp_usb_sendreq (params=0x18e1670, req=0x7f375be92a90) at libusb-glue.c:1060
#9 0x00007f375c2c7fcb in ptp_transaction_new (params=0x18e1670, ptp=0x7f375be92a90, flags=0, sendlen=0, handler=<value optimized out>) at ptp.c:152
#10 0x00007f375c2cb3be in ptp_opensession (params=0x18e1670, session=1) at ptp.c:541
Your backtrace shows your problem is caused by a problem with libmtp which is handled upstream, see also bug 236994 *** This bug has been marked as a duplicate of bug 236994 *** |