chromium-browser crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I don't remember opening chromium-browser recently, but it just decided to crash without even being open. I am running google-
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: chromium-browser 22.0.1229.
ProcVersionSign
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.2-0ubuntu3
Architecture: amd64
Date: Sun Nov 11 21:23:56 2012
Desktop-Session:
DESKTOP_SESSION = gnome-fallback
XDG_CONFIG_DIRS = /etc/xdg/
XDG_DATA_DIRS = /usr/share/
DiskUsage:
b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda1 ext4 28G 14G 13G 53% /\nudev devtmpfs 993M 4.0K 993M 1% /dev\ntmpfs tmpfs 401M 812K 400M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 1002M 1.6M 1001M 1% /run/shm\nnone tmpfs 100M 24K 100M 1% /run/user\n'
Inodes:
b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda1 1.8M 376K 1.4M 21% /\nudev 249K 461 248K 1% /dev\ntmpfs 251K 394 251K 1% /run\nnone 251K 4 251K 1% /run/lock\nnone 251K 12 251K 1% /run/shm\nnone 251K 16 251K 1% /run/user\n'
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2012-08-21 (82 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120821)
MarkForUpload: True
ProcCmdline: chromium-browser\ mailto:<email address hidden>
Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
raise () from /lib/x86_
abort () from /lib/x86_
?? ()
?? ()
?? ()
Title: chromium-browser crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #938563, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.