Using Mozilla 1.7.2 or 1.7.3 crashes when accesing any flash enabled page (using the netscape-flash plugin, both version 6 or 7). This only happens when using x.org 6.8 (6.7 works ok). I don't know where this bug could be filed, Mozilla, netscape-flash or xorg. This is the dump Mozilla produces when ran from the command line lester@lester lester $ mozilla No running windows found (Gecko:18440): Gtk-WARNING **: Unable to locate theme engine in module_path: "industrial", The program 'Gecko' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 99 error_code 8 request_code 149 minor_code 3) (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.) I somewhere read this was caused because the flash plugin was trying to use a "visual" that didn't exist. gflashplayer doesn't crash, it just doesn't run the flash and only displays a blank screen. Reproducible: Always Steps to Reproduce: 1. Open Mozilla (from the command line to see the error) 2. www.macromedia.com 3. Mozilla crashes Actual Results: Mozilla crashes with a 'BadMatch (invalid parameter attributes)' error. Expected Results: The page should be rendered correctly with flash elements running. Apparently this happens only on X.org 6.8, and since it is no longer beta, this should be corrected. No, it is not related to java, I've tried with and without java, both sun and blackdown versions and the java stuff runs perfecly, but it crashes with the flash plugin, whether java is installed or not and with both versions I guess x.org 6.8 can't be unmasked until this is fixed.
is this with composite enabled?
Yes, exactly... composite enabled. I played with it several days ago and didn't imagine it could be the cause of this trouble. But, it could be filed as a x.org composite bug, am I right? =D Thanks for the advice!! Disabling the Composite extension in the xorg.conf file fixes this bug. (Composite is experimental!) Argh
My mozilla crashes the same. How can I disable composite? It seems to be enabled by default. I have no entries in my xorg.conf for it and Option "Composite" "Disable" isn't working too. I am using Xorg 6.8.0-r3 and mozilla-1.7.3-r3 my USE flags are: USE="recode video_cards_mach64 gtk gnome alsa aalib acpi adns aim apache2 apm arts audiofile avi bash-completion bidi bmp bzlib calendar cdr cross crypt cscope ctype cups curl curlwrappers dbm dbx dedicated dga dio directfb divx4linux dvd dvdr emacs emacs-w3 encode esd ethereal evo exif fastcgi fbcon flac flash ftp gb gd gdbm ggi gif gmp gnome gnustep gnutls gphoto2 gpm gps gtk gtk2 gtkhtml icq imagemagic imap imlib inifile ipv6 jabber jack java jpeg kde ladcca lcms libwww lirc mad maildir mbox mcal memlimit mhash mikmod milter mime ming mmap mmx mng motif mozilla mpeg mpi msession msn mysql nas ncurses netboot nis nls odbc oggvorbis openal opengl oscar oss pcmcia pcntl pda pcre pdflib perl php pic pie png pnp portaudio posix postgres ppds python qt quicktime readline recode ruby samba sasl scanner sdl session shared sharedmem simplexml slang slp sndfile snmp sockets socks5 sox speex spell spl sqlite sse ssl svg svga sysvipc szip tcltk tcpd tetex theora tidy tiff tokenizer truetype unicode usb vhosts videos wavelan wmf wxwindows xface xine xinerama xml xml2 xmlrpc xmms xosd xpm xprint xv xvid yahoo zlib insecure-driver"
I had the same problem, toggling the composite option in x.org solved it: Section "Extensions" Option "Composite" "Disable" EndSection
Marking as fixed since a workaround has been discovered. There are env variables which can also be used to prevent errors such as this, but this issue is related to the Composite extension, which is experimental and off-by-default right now. Browse Gentoo forums for some workarounds to this issue in the meantime. By the time compositing becomes stable, upstream products will probably have demonstrated a lot more support.
