chromium-browser core dumps unless stdin is /dev/null

Bug #941812 reported by James Hunt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Attempting to start chromium-browser results in a core dump unless stdin is /dev/null:

$ chromium-browser
Segmentation fault (core dumped)
$ chromium-browser < /dev/null # XXX: here, chromium works as expected.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.56~r121963-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
Uname: Linux 3.2.0-16-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Mon Feb 27 08:43:48 2012
Desktop-Session:
 DESKTOP_SESSION = ubuntu-2d
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg
 XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = /home/james/lib:/usr/local/lib:/home/db2inst1/sqllib/lib32
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to precise on 2012-01-12 (45 days ago)
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
James Hunt (jamesodhunt) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.