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 625413 - Evolution: I receive messages from ...
Evolution: I receive messages from ...
Status: RESOLVED DUPLICATE of bug 546256
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-07-27 16:47 UTC by purevw
Modified: 2011-10-04 09:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description purevw 2010-07-27 16:47:06 UTC 
I receive messages from E-Bay concerning hits to saved searches. Recently, Evolution is apparently not transferring the link address correctly to Firefox. If I click the link in the e-mail, I am taken to an error page at E-Bay. If I right click the link and copy, then paste it into Firefox, it works correctly. Example link:
http://rover.ebay.com/rover/0/e11021.m45.l1123/7?euid=7630073400351686682&loc=http%3A%2F%2Fcgi.ebay.com%2Fws%2FeBayISAPI.dll%3FViewItem%26item%3D150472705883%26ssPageName%3DADME%3AB%3ASS%3AUS%3A1123
  


Distribution: openSUSE 11.2 (x86_64)
Gnome Release: 2.28.2 (null) (SUSE)
BugBuddy Version: 2.28.0
Comment 1 Ralph Clark 2010-08-25 22:30:22 UTC 
I'm experiencing the same problem on Fedora 13 with evolution evolution-2.30.2-4.fc13.i686. The result is the same whichever browser is set up as the default URL handler.

Apparently evolution is inappropriately decoding the URL, (eg replacing "http%3A%2F%2F" with "http://") before handing it off the the browser. The URL needs to be passed to the browser intact in its original form.
Comment 2 Al Schapira 2010-08-26 01:02:59 UTC 
This is my problem too.  I filed bug 625525 and it was dup'd as 581032.
Comment 3 Akhil Laddha 2011-10-04 09:51:57 UTC 

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