Date: Thu, 06 Oct 2005 22:46:34 +0200 From: Mika <freebsd@mean.net> To: Tyler Gee <geekout@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: Firefox dies unexpectedly. Message-ID: <1128631594.16127.5.camel@beeyatch.mean.net> In-Reply-To: <6e01203b0510060849x15fd2652w5fd1c922a2edc32c@mail.gmail.com> References: <1128613406.84353.5.camel@beeyatch.mean.net> <6e01203b0510060849x15fd2652w5fd1c922a2edc32c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I got rid of the flashplugin and it seems to have done the trick. I guess I'll do without flash, really don't need it anyway. //Mika On Thu, 2005-10-06 at 09:49 -0600, Tyler Gee wrote: > It usually has something to do with Flash and your libmap.conf. > Having said that, I have been unable to fix mine after uninstalling > and reinstalling. Try commenting out those lines in your libmap.conf > and visiting the same sites to see if you experience the same > problems. If not, I don't know what the problem is. If so, you can > narrow it down to working with your libmap and your Flash. > > ~Tyler > > > On 10/6/05, Mika <freebsd@mean.net> wrote: > > Hi, > > > > has anyone have the problem that firefox dies spontaneously ? I get this > > output from firefox --sync, it seems to happen on very different sites, > > and not always at the same site. I'm trying to figure out if it's > > Firefox,Xorg or FreeBSD that causes this to happen. > > > > gluffis@beeyatch:~:firefox --sync > > NP_Initialize > > New > > open dsp: Device busy > > SetWindow > > SetWindow > > SetWindow > > New > > SetWindow > > SetWindow > > SetWindow > > NewStream > > WriteReady > > Write > > WriteReady > > Write > > WriteReady > > Write > > WriteReady > > Write > > WriteReady > > Write > > DestroyStream > > Destroy > > The program 'Gecko' received an X Window System error. > > This probably reflects a bug in the program. > > The error was 'BadShmSeg (invalid shared segment parameter)'. > > (Details: serial 129 error_code 178 request_code 147 minor_code 2) > > (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.) > > > > > > Mozilla Firefox 1.0.6, Copyright (c) 1998 - 2005 mozilla.org > > > > FreeBSD beeyatch 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Sun Sep 25 11:21:45 > > CEST 2005 > > > > -- > > Even alcohol can bend the room. > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1128631594.16127.5.camel>