[Bug 669688] Re: chromium crashes when trying to get geolocation for twitter[WAS: chromium-browser crashed with SIGSEGV in malloc()]

2014-01-20 Thread Christopher M. Penalver
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 Ubuntu
Bugs, which is subscribed to 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()]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/669688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 669688] Re: chromium crashes when trying to get geolocation for twitter[WAS: chromium-browser crashed with SIGSEGV in malloc()]

2011-01-07 Thread shankao
I think I have got in the same bug and it's perfectly reproducible with
a different path of actions:

1. Go to twitter and mark the make me geolocalizable option.
2. Go to a web page where they allow you to tweet something and click in the 
given button
3. When arriving in twitter.com page, chromium crashes

I have noted that it does not happen when, after the crash, I reopen
chromium and restore my tabs. The browser goes happily to twitter so
it's probably something happening during the page change.

** Changed in: chromium-browser (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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()]

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 669688] Re: chromium crashes when trying to get geolocation for twitter[WAS: chromium-browser crashed with SIGSEGV in malloc()]

2010-11-01 Thread Rory McCann


-- 
chromium crashes when trying to get geolocation for twitter[WAS: 
chromium-browser crashed with SIGSEGV in malloc()]
https://bugs.launchpad.net/bugs/669688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs