Bug 8787 - duckduckgo search is missing from firefox in cauldron
Summary: duckduckgo search is missing from firefox in cauldron
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Pascal Terjan
QA Contact:
URL:
Whiteboard: 3beta2
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-23 01:28 CET by Dave Hodgins
Modified: 2013-01-26 02:59 CET (History)
3 users (show)

See Also:
Source RPM: firefox-17.0.2-5.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Dave Hodgins 2013-01-23 01:28:09 CET
After installing from the Mageia 3 beta 2 kde live dvd, I
decided to check firefox, to ensure it has the &t=mageia
option, when searching using duckduckgo, but found that
duckduckgo is not listed in the search engines.
Dave Hodgins 2013-01-23 01:28:35 CET

Whiteboard: (none) => 3beta2

Comment 1 David Walser 2013-01-23 11:38:15 CET
As I said here:
https://bugs.mageia.org/show_bug.cgi?id=8184#c52

It's actually not showing it *because* we added the &t=mageia in duckduckgo.xml.

Apparently there's something it now doesn't like about the syntax.

CC: (none) => luigiwalser, pterjan
Assignee: bugsquad => pterjan

Comment 2 Sander Lepik 2013-01-23 11:52:04 CET
http://svnweb.mageia.org/packages/cauldron/firefox/current/SOURCES/firefox-searchengines-duckduckgo.xml?r1=389233&r2=391542 - at least Firefox shows the xml now, before there was syntax error. Not sure if it fixes the problem.

CC: (none) => sander.lepik

Comment 3 Pascal Terjan 2013-01-23 12:34:08 CET
Yes this was indeed a syntax error, I should have at least checked that the xml was still valid, sorry :(
Comment 4 David Walser 2013-01-23 17:31:46 CET
Sander's fix is indeed correct.  This fix needs pushed in Cauldron and mga2.

I'll do it this weekend if nobody beats me to it.
Comment 5 David Walser 2013-01-26 02:59:03 CET
Should be fixed in firefox-17.0.2-7.mga3.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.