Rhythmbox Crashes with Sansa e260

Bug #145166 reported by Stephan Rose
4
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

Rhythmbox will crash when enabling the MTP plugin to sync with a MTP device or when the plugin is already enabled, it will crash when the device is connected.

Terminal Output:

Potential MTP Device with VendorID:0781 and ProductID:7420 responded to control message 2 with a response that was too short. Problems may arrise but continuing
PTP: Opening session
PTP_ERROR_IO: Trying again after resetting USB
Clearing stall on IN endpoint
Clearing stall on OUT endpoint
usb_clear_halt() on OUT endpoint: Connection timed out
usb_claim_interface(): Bad file descriptor
LIBMTP PANIC: Could not open session on device 1
LIBMTP PANIC: configure_usb_devices() error code: 7 on line 1806
LIBMTP_Get_First_Device: Error Connecting

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Stephan Rose (kermos) wrote :

Unfortunately I was not able to obtain a backtrace. When I ran it with GDB it actually didn't crash that time. I'll try it again though when I get a chance this week as it seems that only my office computer is having the problem. My PC at home works no problem which is weird. Both are running Gutsy and both are up to date and both my desktop configurations are virtually identical.

Revision history for this message
Stephan Rose (kermos) wrote :

Just by pure coincidence, I came across this bug and I think they might be related:

https://bugs.launchpad.net/rhythmbox/+bug/127090

Revision history for this message
Sebastien Bacher (seb128) wrote :

not easy to say without a backtrace showing where it's actually crashing

Revision history for this message
Stephan Rose (kermos) wrote :

Well it started doing it here on my home computer as well. So it's happening on both machines now. It seems to be very sporadic as earlier today I was having absolutely no problems.

I'm working on obtaining a complete stacktrace but it seems I am still missing some debug symbols.

Here is what I have so far, I will try to track down the additional missing symbols and see if I can get a more complete trace.

Starting program: /usr/bin/rhythmbox
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230178624 (LWP 13771)]
[New Thread -1245054064 (LWP 13775)]
[Thread -1245054064 (LWP 13775) exited]
Potential MTP Device with VendorID:0781 and ProductID:7420 responded to control message 2 with a response that was too short. Problems may arrise but continuing
PTP: Opening session
PTP_ERROR_IO: Trying again after resetting USB
Clearing stall on IN endpoint
Clearing stall on OUT endpoint
usb_claim_interface(): Bad file descriptor
LIBMTP PANIC: Could not open session on device 1
LIBMTP PANIC: configure_usb_devices() error code: 7 on line 1806
LIBMTP_Get_First_Device: Error Connecting
[New Thread -1245054064 (LWP 13808)]
[Thread -1245054064 (LWP 13808) exited]
Potential MTP Device with VendorID:0781 and ProductID:7420 responded to control message 2 with a response that was too short. Problems may arrise but continuing
PTP: Opening session

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1230178624 (LWP 13771)]
0xb535b9d3 in ptp_mtp_getobjectproplist () from /usr/lib/libmtp.so.6
(gdb) backtrace
#0 0xb535b9d3 in ptp_mtp_getobjectproplist () from /usr/lib/libmtp.so.6
#1 0xb534b2b2 in ?? () from /usr/lib/libmtp.so.6
#2 0x081fe458 in ?? ()
#3 0xffffffff in ?? ()
#4 0xbff8aa08 in ?? ()
#5 0x00005001 in ?? ()
#6 0x2001e458 in ?? ()
#7 0x0856b2a0 in ?? ()
#8 0x089196d8 in ?? ()
#9 0x08220a00 in ?? ()
#10 0x081fe458 in ?? ()
#11 0x00000004 in ?? ()
#12 0x00000000 in ?? ()

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you get a debug backtrace or let apport send the bug so it gets automatically retraced? That doesn't look like a duplicate

Revision history for this message
Stephan Rose (kermos) wrote :

If you can tell me how I'll be happy to do it. I can't send in a report with Apport because apport doesn't come up with Rhythmbox for some reason (works fine when other apps crash though).

Revision history for this message
Stephan Rose (kermos) wrote :

I found another MTP related crash when running mtp-files from the mtp-tools package. Maybe it's related. Apport came up for that so I filed a report.

https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/145838

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report as it lacks of a better trace, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in rhythmbox:
status: Incomplete → Invalid
Revision history for this message
Andrew (andrew-cranna-gmail-deactivatedaccount) wrote :

Hi guys

I am new to Ubuntu so I hope that I haven't messed this up. I followed the instructions to do the backtrace and I have attached the backtrace to this post. If the info isn't there please let me know and I will try again.

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.