problem with mozilla/foxfire
Every time I click on MF, the screen goes black. Then white. Next, the desktop page icons appear without color. Then, the screen goes white. Next, the icons reappear and gradually fill in. Then, you can access MF. Any suggestions how to solve this problem which did not exist when I initially downloaded MF? Taantaan @ [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem with mozilla/foxfire
On Jan 13, 2005, at 2:50 PM, William Cox wrote: Any suggestions how to solve this problem which did not exist when I initially downloaded MF? Just a guess, but one possibility is a corrupted file which is used by the app, such as a preferences file. You might try renaming them and starting it again. Does it work as expected if you login as another user? TjL ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with mozilla/foxfire
I've been trying to get mozilla/firefox to work for a while - it mostly works but now and then it hangs so i decided to run it from a terminal and see what was going on - the below is what happens when i access certain sites (such as the forumns at amdmb.com). I suspect it is flash related but i'm not too sure - has anyone else seen this problem and if so do you ahve a work around? (note this is firefox understable freebsd stable 10) Latest version (1.7 - cvsup a couple of hours ago). I had the same problem with mozilla 1.6 and mozilla 1.7 - it definitly isn't new... I also have the flash and java plug in installed firefox The program 'firefox-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadShmSeg (invalid shared segment parameter)'. (Details: serial 135 error_code 168 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.) 1:~ firefox --sync Segmentation fault (core dumped) ___ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
