Prev: how to resurrect a file
Next: Virtual path
From: The Natural Philosopher on 11 Apr 2010 19:50
Harald Meyer wrote:
> The Natural Philosopher wrote:
>
>> I'll give memtest a go, tho.
>
> I didn't mean defective RAM, I meant problems with allocation of video RAM
> from the main memory. A driver problem.

Nah..dont think so. Its terribly specific to the one app..no other app
shows the same behaviour, so I don't think its a low level problem.
Because no one else has reported it I suspect its some kind of library
incompatibility between the GTK lib and Firefox 3.X.. it isn't a pure
Firefiox bug, because it doesnt show up on other platforms..its not a
GTK bug, because it doesn't show up an in any pother app. I managed to
change its behaviour by adding some switch to GTK..'USE_NATIVE'
something or other.

No, its something in the interface between my specific 64 bit firefox,
and my specific 64bit GTK I guess. And it appeared suddenly after
something got upgraded, but I cant remember what.

The curious thing is, once I run epiphany just ONCE, it seems to fix the
problem.

First  |  Prev  | 
Pages: 1 2
Prev: how to resurrect a file
Next: Virtual path