Date: Thu, 05 Jul 2007 08:55:14 -0500 From: Reid Linnemann <lreid@cs.okstate.edu> To: Anton Galitch <anton.galitch@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: flash Message-ID: <468CF842.1080803@cs.okstate.edu> In-Reply-To: <7c80322b0707021607j64ef1ae4j6b0aacba978f6797@mail.gmail.com> References: <54357.74.64.6.149.1183317914.squirrel@mail.el.net> <18056.11717.973968.984604@jerusalem.litteratus.org> <20070702011717.47687ee9@gumby.homeunix.com.> <200707011937.57100.freebsd@dfwlp.com> <7c80322b0707011754sabd25fcmf3701cc8a5622a2b@mail.gmail.com> <20070702081119.2a989ebc@turion.freeode.co.uk> <7c80322b0707021601n44dab561w48728d1c2d2d7118@mail.gmail.com> <7c80322b0707021607j64ef1ae4j6b0aacba978f6797@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Written by Anton Galitch on 07/02/07 18:07>>
> and no, with flash7 It doesnt even load the application, just the grey
> square, thats the log from the console:
>
>
>
> %firefox
> *** NSPlugin Wrapper *** WARNING: unhandled variable 11 in NPP_GetValue()
> The program 'npviewer.bin' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadMatch (invalid parameter attributes)'.
> (Details: serial 103 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 get similar results from both flash9 and flash7 plugins, none of the
links in the follow-up posts have helped thus far.
The program 'npviewer.bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 89 error_code 8 request_code 147 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.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?468CF842.1080803>