First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 217003
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Daniel Gryniewicz <dang@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Maxim Britov <maxim@office.modum.by>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 217003 depends on: Show dependency tree
Bug 217003 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2008-04-09 10:02 0000 
net-news/liferea doesn't disable gecko if xulrunner enabled.
From current 1.4.14 ebuild:
 # we prefer xulrunner over firefox over seamonkey
 if use xulrunner ; then
         G2CONF="${G2CONF} --enable-xulrunner"
 elif use firefox ; then
         G2CONF="${G2CONF} --enable-gecko=firefox"
 elif use seamonkey ; then
         G2CONF="${G2CONF} --enable-gecko=seamonkey"
 else
         G2CONF="${G2CONF} --disable-gecko"
 fi

liferea enables gecko by default. With +xulrunner we doesn't provide
--disable-gecko into configure.
It wrong for systems with FF3.

Reproducible: Always

------- Comment #1 From Maxim Britov 2008-04-09 10:03:45 0000 ------- 
As workaround I have to use local ebuild with:
        # we prefer xulrunner over firefox over seamonkey
        if use xulrunner ; then
                G2CONF="${G2CONF} --enable-xulrunner"
        fi
        if use firefox ; then
                G2CONF="${G2CONF} --enable-gecko=firefox"
        elif use seamonkey ; then
                G2CONF="${G2CONF} --enable-gecko=seamonkey"
        else
                G2CONF="${G2CONF} --disable-gecko"
        fi

------- Comment #2 From Daniel Gryniewicz 2008-04-09 13:19:58 0000 ------- 
I actually noticed this yesterday, when I was playing with webkit...

Anyway fixed in 1.4.14.  It will go stable in 30 days.

------- Comment #3 From Maxim Britov 2008-04-09 13:51:25 0000 ------- 
1.4.14 from current portage tree still unfixed
and I have to patch local ebuild for my ~amd64.

------- Comment #4 From Daniel Gryniewicz 2008-04-10 18:32:15 0000 ------- 
You didn't wait long enough for it to sync.  The version in the tree should be
fixed.
First Last Prev Next    No search results available      Search page      Enter new bug