abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: rhythmbox '/home/ldng/.gvfs/Montage de gphoto2 sur usb%3A001,003' comment: I suspect an MTP bug. This is the European version of the YP-S3 component: rhythmbox crash_function: rhythmdb_entry_lookup_by_location_refstring executable: /usr/bin/rhythmbox kernel: 2.6.33.8-149.fc13.x86_64 package: rhythmbox-0.12.8-4.fc13 rating: 4 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1283112381 uid: 500 How to reproduce ----- 1. Connect my Samsung YP-S3 2. Open nautilus 3. From there launch Rythmbox 4. Let the drive 'load'. It appears twice 4. Click on the first S3 device
Created an attachment (id=441829) File: backtrace
Created attachment 441830 [details] lsusb -v output the output of the lsusb -v command in case it can help.
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Just connecting an MTP mp3 player to USB. I saw 3 entries in the devices section in rhythmbox: The player and two "unknown device" or similar. Although there are some files on the device, the list was empty. Before I could try to drag some files, rhythmbox had crashed. That's reproducible and occured several times in a row. Comment ----- This is from dmesg: usb 2-1: new high speed USB device using ehci_hcd and address 3 usb 2-1: New USB device found, idVendor=0402, idProduct=0611 usb 2-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2 usb 2-1: Product: PLAYER usb 2-1: Manufacturer: KEENHIGH usb 2-1: SerialNumber: 00403056900000001128 scsi7 : usb-storage 2-1:1.0 usb 5-2: new low speed USB device using uhci_hcd and address 3 usb 5-2: New USB device found, idVendor=045e, idProduct=001e usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 5-2: Product: Microsoft IntelliMouse® Explorer usb 5-2: Manufacturer: Microsoft input: Microsoft Microsoft IntelliMouse® Explorer as /devices/pci0000:00/0000:00:1d.0/usb5/5-2/5-2:1.0/input/input9 generic-usb 0003:045E:001E.0002: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Explorer] on usb-0000:00:1d.0-2/input0 rhythmbox[5340]: segfault at 128 ip 00000035d88a0d03 sp 00007f7fcebfca38 error 4 in librhythmbox-core.so.0.0.0[35d8800000+144000] usb 2-1: usbfs: process 5392 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5392 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5392 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5392 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5392 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5393 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5393 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5393 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5393 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5393 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5393 (rhythmbox) did not claim interface 0 before use usb 2-1: usbfs: process 5393 (rhythmbox) did not claim interface 0 before use usb 2-1: reset high speed USB device using ehci_hcd and address 3 usb 2-1: USB disconnect, address 3 That's in between is me plugging my mouse in.
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Connect an MTP player 2. agree that rhythbox is the application to use 3. watch Rythmbox crash Comment ----- I don't use the application often, but the times I have - it has crashed
*** Bug 621603 has been marked as a duplicate of this bug. ***
*** Bug 635922 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.