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 571441 - gnome-open does not handle mailto: URIs correctly.
gnome-open does not handle mailto: URIs correctly.
Status: RESOLVED DUPLICATE of bug 559483
Product: libgnome
Classification: Deprecated
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: libgnome maintainer
libgnome maintainer
Depends on:
Blocks:
 
 
Reported: 2009-02-12 11:48 UTC by Chris Jones
Modified: 2009-02-19 12:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Make gnome-open handle mailto specially (587 bytes, patch)
2009-02-12 11:52 UTC, Chris Jones
none Details | Review

Description Chris Jones 2009-02-12 11:48:47 UTC
Please describe the problem:
"gnome-open mailto:foo@bar.com" will currently spawn a compose window with "To: ///foo@bar.com" in it. This is because the URI is passed through GIO as a GFile, and that object is known not to handle mailto URIs well.

Unless anyone knows of a more suitable place to fix this, I propose special-casing mailto, and just passing it directly to the uri launcher.

Steps to reproduce:
1. open a shell
2. run: gnome-open mailto:your@address.com
3. witness the compose window have leading slashes on the To address


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Chris Jones 2009-02-12 11:52:12 UTC
Created attachment 128548 [details] [review]
Make gnome-open handle mailto specially
Comment 2 Pedro Villavicencio 2009-02-17 17:31:25 UTC
Confirming, may somebody please have a look to the patch? Thanks.
Comment 3 Pedro Villavicencio 2009-02-19 12:55:13 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 559483 ***