LGB [Gábor Lénárt], 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 chromium-browser-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 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: chromium-browser (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/790118 Title: chromium (and also chrome) crashes sometimes (segfault at bbadbeef) Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser Though I report this bug against chromium-browser, it seems also google chrome stable and beta (channel) is affected too. It's hard to tell when it happens, it cannot be told that a single URL can trigger this, it seems any URL can trigger, usually it happens some times a day, usually at loading a new tab, but sometimes also when the browser is "idle". All of these browsers seems to crash with some common part in the kernel log: "segfault at bbadbeef", even on different machines! Please note that (I think) it's not the apparmor related bug, since the browser _usually_ works, just crashing some times a day. The borwser then still works, but all of my tabs shows the "Ow, snap" usual message. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: chromium-browser 13.0.781.0~svn20110529r87210-0ubuntu1~ucd1~natty ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic i686 Architecture: i386 CrashDB: ubuntu Date: Mon May 30 10:11:39 2011 Desktop-Session: DESKTOP_SESSION = gnome-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/gnome-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: Upgraded to natty on 2010-10-20 (221 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/790118/+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
