Thanks so much for your direction as assistance.. The I will inform you that ever since ff 26. I have only had that issue once and that was the first time I tried it after the update. Ever since that it appears to be working fine. I tested today and worked fine. I will test it more thoroughly over the next couple of days. But this issue might already be resolved.
But even if it is resolved I am going to keep you notes so that I can do my bug submissions correctly. On Sun, Jan 19, 2014 at 12:03 PM, Christopher M. Penalver < [email protected]> wrote: > LDZ, thank you for reporting this and helping make Ubuntu better. However, > your crash report is missing. Please follow these instructions to have > apport report a new bug about your crash that can be dealt with by the > automatic retracer. First, execute at a terminal: > cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y > upgrade && sudo apt-get -y install firefox-dbg && sudo service apport start > force_start=1 > > If you are running the Ubuntu Stable Release you might need to enable > apport in /etc/default/apport and restart. > > Now reproduce the crash, then open your file manager, navigate to your > /var/crash directory and open the crash report you wish to submit. > If this fails you will have to open a terminal and file your report with > 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash > is the crash you would like to report. If you get an error that you aren't > allowed to access this report you will have to file it with 'sudo > ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command > against the crash report and a window pops up asking you to report this, > but then never opens a new report, you would be affected by > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order > to WORKAROUND this, one would need to open the following file via a command > line: > gksudo gedit /etc/apport/crashdb.conf > > and comment out the line: > 'problem_types': ['Bug', 'Package'], > > by changing it to: > # 'problem_types': ['Bug', 'Package'], > > Save, close, and try to file the crash report again via: > ubuntu-bug /var/crash/_my_crash_report.crash > > Please follow https://wiki.ubuntu.com/MozillaTeam/Bugs when you file > this crash report so the necessary information is provided. > > I'm closing this bug report since the process outlined above will > automatically open a new bug report which can then dealt with more > efficiently. > > Thank you for your understanding. > > Helpful bug reporting tips: > https://wiki.ubuntu.com/ReportingBugs > > ** Attachment removed: "this is the crash file that I got" > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1253464/+attachment/3914384/+files/_usr_lib_firefox_firefox.1000.crash > > ** Changed in: firefox (Ubuntu) > Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1253464 > > Title: > firefox crashed with SIGSEGV started in ff 24 and continues in ff 25 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1253464/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253464 Title: firefox crashed with SIGSEGV started in ff 24 and continues in ff 25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1253464/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
