core dumped - segmentation fault

[Lucazade]

In Precise Chromium always crash at first start.
core dumped - segmentation fault

I haven't found any other log about it, ask if needed! :)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: chromium-browser 17.0.963.83~r127885-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Mon Mar 26 13:55:44 2012
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
SourcePackage: chromium-browser
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.

[Maarten Jacobs (maarten256)]

I seem to be experiencing a similar issue - Chromium seems to core dump immediately when it loads. Only occassionally it doesn't - I'm actually writing this bug in Firefox as I can't seem to get Chromium to stay up.

I ran Chromium from the command line, and collected some information:

jacobsma@snellebak:~$ chromium-browser
Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
Gkr-Message: call to daemon returned an invalid response: (null).(null)()
[11259:11273:165486117836:ERROR:native_backend_gnome_x.cc(664)] Keyring find failed: Error communicating with gnome-keyring-daemon
[11259:11259:165486445951:ERROR:browser_main_loop.cc(138)] Gdk: IA__gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed
[11259:11259:165486446253:ERROR:browser_main_loop.cc(138)] GLib-GObject: g_object_ref: assertion `G_IS_OBJECT (object)' failed
[11259:11259:165487584864:ERROR:browser_main_loop.cc(138)] GLib-GObject: g_object_unref: assertion `G_IS_OBJECT (object)' failed
[11259:11259:165527533125:ERROR:x11_util.cc(1121)] X Error detected: serial 27968, error_code 10 (BadAccess (attempt to access private resource denied)), request_code 140, minor_code 1 (X_ShmAttach)
[11259:11259:165527535112:ERROR:x11_util.cc(1121)] X Error detected: serial 27969, error_code 148 (BadShmSeg (invalid shared segment parameter)), request_code 140, minor_code 3 (X_ShmPutImage)
[11259:11259:165527536294:ERROR:x11_util.cc(1121)] X Error detected: serial 28044, error_code 148 (BadShmSeg (invalid shared segment parameter)), request_code 140, minor_code 2 (X_ShmDetach)

>> During this session Chromium stayed up - however I figured perhaps the output was relevant.

Further sessions always result in the same output:

jacobsma@snellebak:~$ chromium-browser
chromium-browser: /build/buildd/cairo-1.10.2/src/cairo-surface.c:1287: cairo_surface_set_device_offset: Assertion `status == CAIRO_STATUS_SUCCESS' failed.
Aborted (core dumped)

>> The "cairo" error has been reported in varios other bugs (is it ever going to be fixed??) - and does not seem to be related to this problem as the core happens a fraction of time after the "cairo" error is logged.

I've collected two core dumps and will attach them to this bug report.

[Maarten Jacobs (maarten256)]

Here's data on my configuration:

Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
RelatedPackageVersions:
 chromium-browser 18.0.1025.151~r130497-0ubuntu1
 chromium-browser-l10n 18.0.1025.151~r130497-0ubuntu1
 chromium-browser-inspector N/A
 chromium-browser-dbg N/A
 chromium-codecs-ffmpeg N/A
 chromium-codecs-ffmpeg-extra 18.0.1025.151~r130497-0ubuntu1

I've attached the complete apport-bug output for reference.

[Maarten Jacobs (maarten256)]

The same, or similar issue is being tracked here:

http://code.google.com/p/chromium/issues/detail?id=121660

[Maarten Jacobs (maarten256)]

Actually - the work-around for this issue is to disable sync. If you cannot get Chromium to stay up, you'll have to delete your Chromium configuration:

1. cd ~/.config
2. rm -rf chromium
3. restart chromium - it should now stay up, as long as you don't "sign in" to chromium

These steps work for me and prevent Chromium from failing - if somebody has a case where Chromium still fails, even with sync disabled, then that's a different problem from what I'm observing on my installation.

[Cinquero (cinquero)]

have this problem, too. But has nothing to do with sync. Happens even after deleting ~/.config/chromium.

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

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