After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 688071 - Rhytmbox segfaults with MTP device
Rhytmbox segfaults with MTP device
Status: RESOLVED DUPLICATE of bug 678138
Product: rhythmbox
Classification: Other
Component: Removable Media
2.97
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-11-11 00:58 UTC by Patrik Dufresne
Modified: 2012-11-11 01:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Log file using -D mtp (16.08 KB, text/x-log)
2012-11-11 01:06 UTC, Patrik Dufresne 		Details
Trace using gdb (20.90 KB, text/x-log)
2012-11-11 01:07 UTC, Patrik Dufresne 		Details

Description Patrik Dufresne 2012-11-11 00:58:18 UTC 
Copying a music album from my music library into the removable media (Google Galaxy Nexus with Androide 4.1.1) cause Rhytmbox to crash with segfault. The removable device was plug into USB port and use MTP.

Step to reproduce:
1. Open Rhytmbox with the command line "rhytmbox -D mtp"
2. Wait until it open
3. Using usb cable, plug the cellphone to the laptop
4. On the cellphone, I make sure the device use MTP
5. In Rhytmbox, the cellphone is displayed under the section 'Devices' labeled as 'Media Player'
6. I select an album from my music library, drag it to the 'Media Player'
7. Rhytmbox crash.

Can reproduce the problem over and over. I attach a trace generate using gdb and a log file.
Comment 1 Patrik Dufresne 2012-11-11 01:06:56 UTC 
Created attachment 228669 [details]
Log file using -D mtp
Comment 2 Patrik Dufresne 2012-11-11 01:07:21 UTC 
Created attachment 228670 [details]
Trace using gdb
Comment 3 Patrik Dufresne 2012-11-11 01:08:15 UTC 
May be related to bug #678349
Comment 4 Jonathan Matthew 2012-11-11 01:12:19 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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