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 564772 - MTP plugin crash when I plug-in my Creative Zen 32Gb
MTP plugin crash when I plug-in my Creative Zen 32Gb
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: Removable Media
0.11.x
Other All
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 592224 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-12-16 19:31 UTC by magnetik
Modified: 2009-10-21 20:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (44.13 KB, text/plain)
2008-12-25 17:51 UTC, magnetik
Details
output of mtp-tracks command (zipped) (133.87 KB, application/force-download)
2009-01-01 21:37 UTC, magnetik
Details

Description magnetik 2008-12-16 19:31:39 UTC
Steps to reproduce:
I start rhythmbox 0.11.6 on Ubuntu Intrepid
I plug in my Creative Zen 32Gb
Crash with :
PTP: Opening session
**
RhythmDB:ERROR:rhythmdb.c:3155:rhythmdb_entry_set_internal: assertion failed: (g_utf8_validate (g_value_get_string (value), -1, NULL))



Stack trace:
I've installed rhythmbox-dbg, and bug-buddy, but it seems that it doesn't works..
Ask me if you need this information

Other information:
Comment 1 Jonathan Matthew 2008-12-17 05:28:44 UTC
It looks like one (or more) of the tracks on the device has broken track metadata.  How did you add them?

I don't think we need a stack trace for this one.

Comment 2 magnetik 2008-12-17 05:35:15 UTC
Everything has been synchronized with the original Creative Zen application on Windows XP
Comment 3 magnetik 2008-12-25 17:51:01 UTC
Created attachment 125309 [details]
backtrace

Its the backtrace when I plug in my Creative Zen.

The icon of the Zen shows up, and then the program crash.
Comment 4 André Klapper 2008-12-30 21:37:29 UTC
Can you also install debug packages for libglib2 (or however Ubuntu calls it)? That part is missing in the backtrace.
Comment 5 Jonathan Matthew 2008-12-30 22:54:27 UTC
I don't think we need that information.  It's clear what's going on here - we're expecting to get a utf8 string from libmtp, but we're getting something else.  What's not clear is how that's happening.  The mtp/ptp protocol seems to use utf16, which libmtp then converts to utf8, so I don't really see how we could end up with invalid utf8 data..

Output from the 'mtp-tracks' program (from the mtp-tools package) might help.
Comment 6 magnetik 2009-01-01 21:37:02 UTC
Created attachment 125603 [details]
output of mtp-tracks command (zipped)

Here it is. I've got it with the command : mtp-tracks > mtp-tracks.txt

Ask me if you need more informations
Comment 7 Jonathan Matthew 2009-01-02 03:10:01 UTC
I'm only looking at song titles here, because that's what caused the crash according to the stack trace..

These look like they have been damaged in conversion at some point:

   Title: Ma première ligne (part 1)
   Title: Ma première ligne (part 2)
   Title: Ma première ligne (part 3)
   Title: Mr Issaïa
   Title: Ouverture facile à la con

Removing these songs from the device will probably stop it crashing.  If so, then we need to process the strings we get from libmtp to ensure they're valid utf8.

These are the only other songs that use non-ascii characters, but they're not likely to cause problems:

   Title: 108…
   Title: Comptine d'été n°1
   Title: Comptine d'été n°2
   Title: Comptine d'été n°3
   Title: Lamb‚ An Dro                     <- not a comma
   Title: LumiÞre du jour
   Title: Prière n°2
   Title: Prière n°3
   Title: Suis ta musique o¨ elle va
Comment 8 Jonathan Matthew 2009-10-10 21:56:59 UTC
commit 4ed644acc178c0319cb2217dd26132e82b0eed97
Author: Jonathan Matthew <jonathan@d14n.org>
Date:   Sun Oct 11 07:55:24 2009 +1000

    mtp: ignore non-utf8 strings we get from libmtp (bug #564772)
Comment 9 Jonathan Matthew 2009-10-21 20:17:49 UTC
*** Bug 592224 has been marked as a duplicate of this bug. ***