i dont have this segfault in my archlinux 32 bits.
Moritz Wilhelmy wrote:
Hi,
I updated my arch-system one minute ago and surf seems to segfault with
the newest webkit (1.1.15.3).
I recompiled the newest surf from hg, and the same happens.
GDB said:
Program received signal SIGSEGV, Segmentati
On Thu, 22 Oct 2009 20:23:01 +0200
"Enno Boland (Gottox)" wrote:
> hi!
>
> It seems this is caused by archlinux libwebkit release. Downgrade
> you're webkit to an earlier release. uzbl has the same problem. For
> some strange reason midori still works...
>
> regards
what makes you think this i
Actually chromium does not use libwebkit.
2009/10/22 Moritz Wilhelmy :
> chromium also works.
>
> Maybe this is intended to piss every uzbl and surf-user off? :D
>
> Regards
>
> On Thu, Oct 22, 2009 at 08:23:01PM +0200, Enno Boland (Gottox) wrote:
>> hi!
>>
>> It seems this is caused by archlinux
chromium also works.
Maybe this is intended to piss every uzbl and surf-user off? :D
Regards
On Thu, Oct 22, 2009 at 08:23:01PM +0200, Enno Boland (Gottox) wrote:
> hi!
>
> It seems this is caused by archlinux libwebkit release. Downgrade
> you're webkit to an earlier release. uzbl has the same
hi!
It seems this is caused by archlinux libwebkit release. Downgrade
you're webkit to an earlier release. uzbl has the same problem. For
some strange reason midori still works...
regards
2009/10/22 Moritz Wilhelmy :
> Hi,
>
> I updated my arch-system one minute ago and surf seems to segfault wi
Hi,
I updated my arch-system one minute ago and surf seems to segfault with
the newest webkit (1.1.15.3).
I recompiled the newest surf from hg, and the same happens.
GDB said:
Program received signal SIGSEGV, Segmentation fault.
0xb6a8f3de in g_main_context_prepare () from /usr/lib/libglib-2.0.s
