Rory McCann, 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/669688 Title: chromium crashes when trying to get geolocation for twitter[WAS: chromium-browser crashed with SIGSEGV in malloc()] Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Binary package hint: chromium-browser when going to write a tweet, chromium crashed ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: chromium-browser 6.0.472.63~r59945-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 CrashCounter: 1 Date: Mon Nov 1 22:47:58 2010 ExecutablePath: /usr/lib/chromium-browser/chromium-browser ProcCmdline: /usr/lib/chromium-browser/chromium-browser ProcEnviron: PATH=(custom, user) LANG=en_IE.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb69e3e87 <malloc+519>: mov (%edi),%edx PC (0xb69e3e87) ok source "(%edi)" (0x52bf2000) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: chromium-browser StacktraceTop: malloc () g_malloc () from /lib/libglib-2.0.so.0 g_strdup () from /lib/libglib-2.0.so.0 ?? () from /usr/lib/libgobject-2.0.so.0 g_value_copy () from /usr/lib/libgobject-2.0.so.0 Title: chromium-browser crashed with SIGSEGV in malloc() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare chromium-default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser # Options to pass to chromium-browser CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/669688/+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
