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 654213 - Fails to load cover art if the path contains ':'
Fails to load cover art if the path contains ':'
Status: RESOLVED DUPLICATE of bug 638589
Product: banshee
Classification: Other
Component: general
2.0.0
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-08 02:02 UTC by Martin Stjernholm
Modified: 2014-02-21 13:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Martin Stjernholm 2011-07-08 02:02:49 UTC
Got this error when I tried to load a cover art picture from the path

  /home/mast/music/various/Mitek: Process/cover.jpg

using the "Choose New Cover Art..." action:

[Warn  03:43:19.698] Caught an exception - System.UriFormatException: URI scheme must start with a letter and must consist of one of alphabet, digits, '+', '-' or '.' character. (in `System')
  at System.Uri.Parse (UriKind kind, System.String uriString) [0x00000] in <filename unknown>:0 
  at System.Uri.ParseUri (UriKind kind) [0x00000] in <filename unknown>:0 
  at System.Uri..ctor (System.String uriString, Boolean dontEscape) [0x00000] in <filename unknown>:0 
  at System.Uri..ctor (System.String uriString) [0x00000] in <filename unknown>:0 
  at Banshee.Collection.Gui.CoverArtEditor+EditorBox.SetCoverArt (Banshee.Collection.TrackInfo track, System.String path) [0x00000] in <filename unknown>:0 
  at Banshee.Collection.Gui.CoverArtEditor+EditorBox.<EditorBox>m__15 (System.Object , System.EventArgs ) [0x00000] in <filename unknown>:0 

I managed to use the picture by first copying it to another dir without ":". I also got a very similar error for another directory containing ":", while other directories worked fine, hence my conclusion that ":" is the problem.
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2014-02-21 13:27:01 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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