chromium-browser FATAL:plugin_service

[mama21mama]

mama@zeuza:~$ chromium-browser
[2555:2567:112972905896:FATAL:plugin_service.cc(73)] Check failed: false. Plugin loading should happen out-of-process.
Abortado

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: chromium-browser 17.0.935.0~svn20111110r109380-0ubuntu1~ucd1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CrashDB: ubuntu
Date: Thu Nov 10 18:54:09 2011
Desktop-Session:
 DESKTOP_SESSION = None
 XDG_CONFIG_DIRS = None
 XDG_DATA_DIRS = None
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: chromium-browser
ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)
chromium-default: CHROMIUM_FLAGS=""

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

mama21mama, 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