Original reporter = https://launchpad.net/~matt.eskes-deactivatedaccount
Matt Eskes, 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 ** Changed in: firefox (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/534883 Title: Firefox XID collision causing Core Dump in Lucid Status in “firefox” package in Ubuntu: Invalid Bug description: Binary package hint: firefox Noticed that Firefox was crashing when trying to view certain websites in Lucid. Started firefox from command prompt in order to get debugging feedback which lead to: meskes@Neptune:$ firefox 2.4+ kernel w/o ELF notes? -- report this (firefox-bin:18871): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18871): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18871): Gdk-WARNING **: XID collision, trouble ahead (firefox-bin:18871): Gdk-WARNING **: XID collision, trouble ahead Segmentation fault (core dumped) meskes@Neptune: Now I have noticed one thing in common when this happens; the sites I'm trying to view, in this case a local new site had an embedded flash video. Don't know if that's got anything of anything to do with it, but I figured that I might add that for what good it may or may not do. ProblemType: Bug Architecture: amd64 AuditLog: Date: Tue Mar 9 00:02:27 2010 DistroRelease: Ubuntu 10.04 FirefoxPackages: firefox 3.6+nobinonly-0ubuntu5 firefox-gnome-support 3.6+nobinonly-0ubuntu5 firefox-branding 3.6+nobinonly-0ubuntu5 abroswer N/A abrowser-branding N/A KernLog: Package: firefox 3.6+nobinonly-0ubuntu5 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic SourcePackage: firefox Uname: Linux 2.6.32-15-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/534883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
