No i am unable to reproduce this bug in firefox-3b5 nor firefox-2.0. most likely if X crashed it caused crash for firefox. Now if you ca get a backtrace of the issue than we will leave this open if it shows anything but without a verbose backtrace this is gonna be just about impossible to do anything with. I seem to feel it was not a crash if apport didnt send log to /var/crash. If you crash X anything you had running is going to report a crash when you log back in they are caused by the original crash and firefox nor gdm will cause X to crash it would be the other way around. Marking as incomplete until we get the back traces needed.
To backtrace please follow instructions at https://wiki.ubuntu.com/MozillaTeam/Bugs
Please dont set the status back to new alway set it back to incomplete since i have asked for information.
No i am unable to reproduce this bug in firefox-3b5 nor firefox-2.0. most likely if X crashed it caused crash for firefox. Now if you ca get a backtrace of the issue than we will leave this open if it shows anything but without a verbose backtrace this is gonna be just about impossible to do anything with. I seem to feel it was not a crash if apport didnt send log to /var/crash. If you crash X anything you had running is going to report a crash when you log back in they are caused by the original crash and firefox nor gdm will cause X to crash it would be the other way around. Marking as incomplete until we get the back traces needed. /wiki.ubuntu. com/MozillaTeam /Bugs
To backtrace please follow instructions at https:/
Please dont set the status back to new alway set it back to incomplete since i have asked for information.