Subhro Sankha Kar
subhro at 80386.org
Wed Jul 4 06:51:15 UTC 2012
On 04-Jul-2012, at 1:59 AM, Lars Eighner wrote:
> On Wed, 4 Jul 2012, Subhro Sankha Kar wrote:
>> On 03-Jul-2012, at 9:14 PM, Tobias Rehbein wrote:
>>> Am Tue, Jul 03, 2012 at 01:04:07AM -0500 schrieb Lars Eighner:
>>>> Call me crazy, but it seems that since the perl bump (5.12 -> threaded-5.16)
>>>> when firefox (13.0.1,1) got rebuilt, it seems twitter pages do not fully
>>>> load, give me the slow loading banner, and the page (not browser or X)
>>>> freezes, but no such problems were evident before, and twitter seems
>>>> entirely normal in Opera 12.00.
>>> Disabling SPDY in about:config (a solution proposed on the net) didn't fix
>>> this issue.
> Another thing that doesn't work is rebuilding firefox from the ground up
> with portupgrade -fR firefox.
Where does it burp? Can you post, say, the last 10-15 lines of the compile?
>> Can you post the contents of about:config and also try to launch FF from
>> command line and see if there is anything interesting reported back? Also, I hope you do not have any funky CFLAGS set in your make.conf?
> Of course firefox will not run from the command line ("Error: no display
> specified"), but there are no messages as firefox fails repeated to load
> twitter pages fully when firefox is launched in an xterm.
Sorry for the ambiguity, I indeed meant to launch FF from xterm (or some equivalent Terminal Emulator in X) and report back the error. But since you say there is no problem with that, guess things should be good.
> QT4_OPTIONS= CUPS
> WITH_GCC = yes
> # added by use.perl 2012-07-03 02:17:12
This looks pretty generic, so nothing to complain about.
> I hate GUIs, so my mouse-fu skills are not good enough to copy about.config,
> but here is a "save as"
Okay, try this out. Go to preferences and disable "hardware acceleration". Also go to about:config and search for "gfx". Set the property "gfx.direct2d.disabled" to true. Bounce the browser and go to "about:support". At the bottom of the page, "GPU Accelerated Windows" should read "0/1". See if that makes a difference.
Subhro Sankha Kar
Working and Playing with FreeBSD since 2002
More information about the freebsd-questions