chrome:bugreport crashes browser (Ubuntu daily build)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: chromium-browser
Using menu to nav to 'report problem' option opens chrome:
Editing url to chrome:bugreport (curiosity :P) then causes issues:- attempt to close tab crashes browser with segfault.
This probably shouldn't happen! Recent addition of chrome web-apps is only user change made recently...
(sorry if daily build bugreports aren't meant to be here!)
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: chromium-browser 10.0.611.
ProcVersionSign
Uname: Linux 2.6.35-23-generic i686
Architecture: i386
CrashDB: ubuntu
Date: Tue Dec 14 18:43:42 2010
Desktop-Session:
DESKTOP_SESSION = gnome
GNOME_
XDG_CONFIG_DIRS = /etc/xdg/
XDG_DATA_DIRS = /usr/share/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091019.2)
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: chromium-browser
ThirdParty: True
chromium-default: CHROMIUM_FLAGS=""
Andy S, 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: browser- dbg && sudo service apport start force_start=1
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install chromium-
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. _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: crashdb. conf
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/
gksudo gedit /etc/apport/
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: _my_crash_ report. crash
ubuntu-bug /var/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: /wiki.ubuntu. com/ReportingBu gs
https:/