Firefox 2.0 Crashes on Ubuntu Edgy

Bug #68705 reported by evuraan
4
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: firefox

Firefox 2.0 (*this problem is not evident on FF 1.5.X) on Ubuntu Edgy crashes with the message:

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 100 error_code 8 request_code 143 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.)

strace on firefox until it crashed is uploaded, its here:

http://evuraan.googlepages.com/newff.txt

Revision history for this message
evuraan (evuraan) wrote :

This issue occurs even when firefox is evoked with

 MOZ_DISABLE_PANGO="1"

and

 MOZ_DISABLE_PANGO="0"

And firefox options --sync and --no-xshm :

ubuntu:/tmp$ firefox --sync --no-xshm
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 100 error_code 8 request_code 143 min@ubuntu:/tmp$ firefox --sync
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 100 error_code 8 request_code 143 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.)

ubuntu:/tmp$ firefox --sync
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 100 error_code 8 request_code 143 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.)

Revision history for this message
Andrew Bassett (awbassett) wrote :

I noticed you have flash installed - is it flashplugin-nonfree?

Also, what color depth are you running at? Try 24-bit if you're at 16-bit.

Revision history for this message
evuraan (evuraan) wrote : Re: [Bug 68705] Re: Firefox 2.0 Crashes on Ubuntu Edgy

These are the installed ones I found from about:plugins

        Shockwave Flash
        FutureSplash Player

On 10/28/06, Andrew Bassett <email address hidden> wrote:
> I noticed you have flash installed - is it flashplugin-nonfree?
>
> Also, what color depth are you running at? Try 24-bit if you're at
> 16-bit.
>
> --
> Firefox 2.0 Crashes on Ubuntu Edgy
> https://launchpad.net/bugs/68705
>

Revision history for this message
Manuel López-Ibáñez (manuellopezibanez) wrote :

@evuraan

Please, could you open a terminal and write:

sudo dpkg -l | grep flash

Also, could you open /etc/X11/xorg.conf and replace the line:
 DefaultDepth 16
by:
 DefaultDepth 24

then, reboot and try firefox again.

Thanks.

Revision history for this message
evuraan (evuraan) wrote :

This suggestion seems to be working; no crashes (so far) in 24-bit depth.

<snip>
Also, what color depth are you running at? Try 24-bit if you're at 16-bit.
<snip>

Revision history for this message
satkata (satkata-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

HI,

I know that Firefox is running fine with DefaultDepth 24, but I'm using 16, because Xorg needs less memory then.
But I hope that this issue is going to be fixed soon too. For now
"export XLIB_SKIP_ARGB_VISUALS=1" in the firefox startup script is solving my problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.