Glen Kjaerulff wrote:
Especially on this site:

http://www.mandrake.cz

Cool :-)
Work perfectly here..

Same problem, just crashes, with or without any plugins.


Be sure to run an up to date cooker (specially XFree86-libs)

Is running latest cooker, from last night.

How can I redirect error out from Mozilla, so it doesnt go to /dev/null??

/Glen Kjaerulff
Same problem here.

Here is a full crash test with all errors I got :

cd /usr/lib/mozilla-1.2.1
./run-mozilla.sh

Go to URL : http://www.clermont-ferrand.fr/vivre/telepro/mariage.htm

In the form first menu select "acte de naissance"
Then it crash

Crash dump here :

NP_Initialize
argv[0] src ../../images/vivre/telepro/telepro.swf
argv[1] quality high
argv[2] pluginspage http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash
argv[3] type application/x-shockwave-flash
argv[4] width 349
argv[5] height 161
starting up Xt stuff
gtk_xtbin_realize()
initial allocation 0 0 349 161
xt_client_create()
gtk_xtbin_resize 0x8a74ff0 349 161
gtk_xtbin_resize 0x8a74ff0 349 161
gtk_xtbin_resize 0x8a74ff0 349 161

(<unknown>:3496): Gtk-WARNING **: ../../gtk/gtksocket.c:957Can't add non-GtkPlug to GtkSocket

(<unknown>:3496): Gdk-CRITICAL **: file ../../../gdk/x11/gdkmain-x11.c: line 648 (gdk_error_trap_pop): assertion `gdk_error_traps != NULL' failed
gtk_xtbin_unrealize()
gtk_xtbin_destroy()
removing the Xt connection from the main loop
gtk_xtbin_destroy()
NP_Initialize
argv[0] src ../../images/vivre/telepro/telepro.swf
argv[1] quality high
argv[2] pluginspage http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash
argv[3] type application/x-shockwave-flash
argv[4] width 349
argv[5] height 161
gtk_xtbin_realize()
initial allocation 0 0 349 161
xt_client_create()

Gdk-ERROR **: The program '<unknown>' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 22 error_code 3 request_code 2 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...


Hope this wille help

Regards

--
Léa Gris - http://www.noiraude.net/
() Campagne du ruban texte brut contre les courriels en HTML,
/\ contre les pièces jointes Microsoft.


Reply via email to