Excerpts from solsTiCe d'Hiver's message of Fri Aug 07 00:44:03 -0400 2009:

...

export LD_PRELOAD=/usr/lib/libGL.so.1

that fix was working for me since i upgraded to firefox 3.5

but since the update of nvidia driver recently and firefox update too. this fix does not work ANYMORE.

Hmm, works for me (I upgraded my nvidia/kernel/xorg/firefox/flashplayer yesterday). Maybe it's somewhat dependent on card :/

look at https://bugzilla.mozilla.org/show_bug.cgi?id=496831 and other duplicated bug reports

it is supposed to be fixed. so it's coming in some near future

Okay, thanks very much for that. I guess I won't file a bug report with us as it's an upstream issue (kind of why I was asking). We can technically "fix" it by adding a wrapper to our firefox package to do that hack, but I'm pretty sure I agree with Aaron (and the devs in general) in that we should just wait for the aforementioned fix. Cheers. -- Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)

Excerpts from Jan de Groot's message of Fri Aug 07 09:58:58 -0400 2009:

On Fri, 2009-08-07 at 09:51 -0400, Andrei Thorp wrote:

...

Excerpts from solsTiCe d'Hiver's message of Fri Aug 07 00:44:03 -0400 2009:

...

...

export LD_PRELOAD=/usr/lib/libGL.so.1

that fix was working for me since i upgraded to firefox 3.5

but since the update of nvidia driver recently and firefox update too. this fix does not work ANYMORE.

Hmm, works for me (I upgraded my nvidia/kernel/xorg/firefox/flashplayer yesterday). Maybe it's somewhat dependent on card :/

...

look at https://bugzilla.mozilla.org/show_bug.cgi?id=496831 and other duplicated bug reports

it is supposed to be fixed. so it's coming in some near future

Okay, thanks very much for that. I guess I won't file a bug report with us as it's an upstream issue (kind of why I was asking). We can technically "fix" it by adding a wrapper to our firefox package to do that hack, but I'm pretty sure I agree with Aaron (and the devs in general) in that we should just wait for the aforementioned fix.

We already had such a bug, and I closed it as upstream, as it has something to do with two non-free components that we can't fix. Seems mozilla wants to work this around inside firefox, so it's just to wait for a version that includes their workaround.

Ah, okay, I did a search but didn't find anything. -- Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)