Chromium crashes when starting. Segfaults?

[wolfman]

@wolfman

Okay, try the following, remove Chromium and then change your software sources download location and then re-install it and see if that helps?.

Ubuntu Mate Update Guide

@WalkOnATYCLB,

did you try the above?.

[aworan]

Hi wolfman,
As I said in the thread the problem is with chromium 49 for armhf architecture (not usual PC like x86 or amd64).
It is the same problem both raspberry pi or odrid which have same armhf architecture.
The problem appears with version 49, chromium works in version 48.
A bug report was open on launchpad. We must wait canonical to fix it.
You can revert to version 48, look my post in this thread until.

Aworan

[wolfman]

Hi @aworan,

can you not use Synaptic and “Force Version”?.

https://help.ubuntu.com/community/SynapticHowto#How_to_force_the_installation_of_a_package_version

[rph]

Hi, I notice that the problem still exists. Will it ever get resolved ? Thanks

[M_Rusli]

I too having the same issue with the Chromium browser… it cannot seem to run at all on my Raspberry Pi3.

Not only that now the pepper flash package is no longer to download via synaptic.

I did uninstall and reinstall the software again. Still I get the same sandbox errors!

[aworan]

I found a workaround to have the lastest version of chromium working see my tutorial there :

[Tutorial] - Install working chromium 50

Hi, There is a problem since months with chromium, standard installation don't work ! There is an error launching chromium and it don't start ! A bug report is open in launchpad but it isn't fixed yet. This is a workaround to install and have chromium working ! Remove chromium installation sudo apt-get remove chromium-codecs-ffmpeg-extra chromium-browser chromium-browser-l10n Next we have to download chromium for ubuntu 14.04, I know it is strange but the package for ubuntu 14.04 work w…

[t3kg33k]

So I just received my RPi3 today and installed Ubuntu Mate 16.04, tried installing Chromium and am experiencing the same crash, even at first launch.
Has there been a fix yet?

[internalfx]

I was able to get chromium 53 running with the --disable-gpu flag.

[aworan]

Victory !
Bug on launchpad was assigned and prioritize to high 10 days ago !
I hope it will work in next release

Chad Miller (cmiller) wrote on 2016-07-25: #20
Reproduced. Thanks, all. I don't need more me-toos for now.

Changed in chromium-browser (Ubuntu):
importance: Undecided → High
assignee: nobody → Chad Miller (cmiller)

[markartman]

Where do I put this flag, specifically?

[deric]

First of all check chrome://gpu whether GPU is enabled (if you’re able to start chromium).

$> vim /etc/chromium-browser/default

and update CHROMIUM_FLAGS="--disable-gpu" variable

[Sokunrotanak_Srey]

I run chromium v53 on Ubuntu Mate on Raspberry Pi3, it still crashed with the --disable-gpu flag. This is what I got from --verbose

[5128:5128:1005/091830:VERBOSE1:breakpad_linux.cc(1840)] Breakpad disabled
[1:1:1005/091832:VERBOSE1:sandbox_linux.cc(154)] Lacking support for seccomp-bpf sandbox.
[1:1:1005/091832:VERBOSE1:zygote_main_linux.cc(599)] ZygoteMain: initializing 0 fork delegates
[1:1:1005/091832:INFO:systeminfo.cc(82)] Available number of cores: 4
[5128:5128:1005/091833:VERBOSE1:gpu_info_collector_linux.cc(88)] PCI bus scanning is not supported
[5128:5128:1005/091833:VERBOSE1:proxy_config_service_linux.cc(853)] All gsettings tests OK. Will get proxy config from gsettings.
[5128:5128:1005/091833:VERBOSE1:proxy_config_service_linux.cc(1611)] Obtained proxy settings from GSETTINGS
[5128:5128:1005/091833:VERBOSE1:pref_proxy_config_tracker_impl.cc(151)] 0x57394fc0: set chrome proxy config service to 0x573a1340
[5128:5128:1005/091833:VERBOSE1:pref_proxy_config_tracker_impl.cc(276)] 0x57394fc0: Done pushing proxy to UpdateProxyConfig
[5128:5128:1005/091833:VERBOSE1:key_storage_linux.cc(23)] OSCrypt store set to 
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Google 'Pilot' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Google 'Aviator' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: DigiCert Log Server
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Google 'Rocketeer' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Symantec log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Venafi log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Symantec 'Vega' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: CNNIC CT log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Izenpe log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Certly.IO log
[5128:5128:1005/091833:VERBOSE1:mutable_profile_oauth2_token_service_delegate.cc(137)] MutablePO2TS::MutablePO2TS
[5128:5128:1005/091833:VERBOSE1:bluetooth_low_energy_event_router.cc(247)] Initializing BluetoothLowEnergyEventRouter.
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "424119844901-tilod0e1nm0dt85e1evrdfp3cc3ec01d.apps.googleusercontent.com" for API key GOOGLE_CLIENT_ID_MAIN
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "WCCejhqORuxKG272GAWxsPIU" for API key GOOGLE_CLIENT_SECRET_MAIN
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "424119844901-tilod0e1nm0dt85e1evrdfp3cc3ec01d.apps.googleusercontent.com" for API key GOOGLE_CLIENT_ID_CLOUD_PRINT
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "WCCejhqORuxKG272GAWxsPIU" for API key GOOGLE_CLIENT_SECRET_CLOUD_PRINT
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "424119844901-tilod0e1nm0dt85e1evrdfp3cc3ec01d.apps.googleusercontent.com" for API key GOOGLE_CLIENT_ID_REMOTING
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "WCCejhqORuxKG272GAWxsPIU" for API key GOOGLE_CLIENT_SECRET_REMOTING
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "424119844901-tilod0e1nm0dt85e1evrdfp3cc3ec01d.apps.googleusercontent.com" for API key GOOGLE_CLIENT_ID_REMOTING_HOST
[5128:5128:1005/091833:VERBOSE1:google_api_keys.cc(259)] Using default value "WCCejhqORuxKG272GAWxsPIU" for API key GOOGLE_CLIENT_SECRET_REMOTING_HOST
[5128:5128:1005/091833:VERBOSE1:proxy_config_service_linux.cc(853)] All gsettings tests OK. Will get proxy config from gsettings.
[5128:5128:1005/091833:VERBOSE1:proxy_config_service_linux.cc(1611)] Obtained proxy settings from GSETTINGS
[5128:5128:1005/091833:VERBOSE1:pref_proxy_config_tracker_impl.cc(151)] 0x574f37d0: set chrome proxy config service to 0x574c9798
[5128:5128:1005/091833:VERBOSE1:pref_proxy_config_tracker_impl.cc(276)] 0x574f37d0: Done pushing proxy to UpdateProxyConfig
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Google 'Pilot' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Google 'Aviator' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: DigiCert Log Server
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Google 'Rocketeer' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Symantec log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Venafi log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Symantec 'Vega' log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: CNNIC CT log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Izenpe log
[5128:5163:1005/091833:VERBOSE1:multi_log_ct_verifier.cc(67)] Adding CT log: Certly.IO log
[5128:5128:1005/091833:VERBOSE1:password_store_factory.cc(203)] Password storage detected desktop environment: GNOME
[5128:5128:1005/091833:VERBOSE1:password_store_factory.cc(226)] Trying libsecret for password storage.
[5128:5128:1005/091833:VERBOSE1:password_store_factory.cc(229)] Using libsecret keyring for password storage.
[5128:5128:1005/091833:VERBOSE1:extension_service.cc(1524)] AddComponentExtension Bookmark Manager
[5128:5128:1005/091833:VERBOSE1:extension_service.cc(1524)] AddComponentExtension Cloud Print
[5128:5128:1005/091833:VERBOSE1:extension_service.cc(1524)] AddComponentExtension Web Store
[5128:5128:1005/091833:VERBOSE1:extension_service.cc(1524)] AddComponentExtension Google Hangouts
[5128:5128:1005/091833:VERBOSE1:extension_service.cc(1526)] Component extension Google Hangouts (nkeimhogjdpnpccoofpliimaahmaaome) installing/upgrading from '1.2.0' to 1.3.0
[5128:5128:1005/091833:VERBOSE1:extension_service.cc(1524)] AddComponentExtension CryptoTokenExtension
[5128:5128:1005/091833:VERBOSE1:extension_service.cc(1524)] AddComponentExtension Chromium PDF Viewer
[5128:5128:1005/091833:VERBOSE1:account_reconcilor.cc(70)] AccountReconcilor::AccountReconcilor
[5128:5128:1005/091833:VERBOSE1:account_reconcilor.cc(81)] AccountReconcilor::Initialize
[5128:5128:1005/091833:VERBOSE1:ev_whitelist_component_installer.cc(141)] Registering EV whitelist component.
[5128:5128:1005/091833:VERBOSE1:file_type_policies_component_installer.cc(123)] Registering File Type Policies component.
[5128:5159:1005/091833:VERBOSE1:crl_set_fetcher.cc(105)] Loaded 190597 bytes of CRL set from disk
[5128:5193:1005/091833:VERBOSE1:default_component_installer.cc(198)] StartRegistration for Widevine Content Decryption Module
[5128:5193:1005/091833:VERBOSE1:default_component_installer.cc(198)] StartRegistration for EV Certs CT whitelist
[5128:5193:1005/091833:VERBOSE1:default_component_installer.cc(198)] StartRegistration for Signed Tree Heads
[5128:5163:1005/091833:VERBOSE1:crl_set_fetcher.cc(127)] Installed CRL set #3261
[5128:5193:1005/091833:VERBOSE1:default_component_installer.cc(198)] StartRegistration for Origin Trials
[5128:5193:1005/091833:VERBOSE1:default_component_installer.cc(198)] StartRegistration for File Type Policies
[5128:5128:1005/091833:VERBOSE1:startup_browser_creator_impl.cc(571)] StartupBrowserCreatorImpl::ProcessStartupURLs
[5128:5128:1005/091833:VERBOSE1:startup_browser_creator_impl.cc(579)] Pref: default
[5128:5128:1005/091833:VERBOSE1:cross_device_promo.cc(71)] CrossDevicePromo::CrossDevicePromo.
[5128:5128:1005/091833:VERBOSE1:cross_device_promo.cc(180)] CrossDevicePromo::MaybeBrowsingSessionStarted; Ineligible for promo.
[5128:5128:1005/091834:VERBOSE1:cross_device_promo.cc(169)] CrossDevicePromo::MaybeBrowsingSessionStarted. Same browsing session as the last call.
[5128:5128:1005/091834:VERBOSE1:cross_device_promo.cc(169)] CrossDevicePromo::MaybeBrowsingSessionStarted. Same browsing session as the last call.
[5128:5128:1005/091834:VERBOSE1:bluez_dbus_manager.cc(157)] Bluetooth supported. Initializing clients.
[5128:5149:1005/091834:VERBOSE1:bus.cc(873)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s
string "org.bluez"
[5128:5128:1005/091834:VERBOSE1:proxy_config_service_linux.cc(1723)] Detected no-op change to proxy settings. Doing nothing.
[5128:5128:1005/091834:VERBOSE1:proxy_config_service_linux.cc(1723)] Detected no-op change to proxy settings. Doing nothing.
[5128:5128:1005/091834:VERBOSE1:component_updater_service.cc(85)] CrxUpdateService starting up. First update attempt will take place in 360 seconds. Next update attempt will take place in 21600 seconds. 
[5128:5128:1005/091834:VERBOSE1:default_component_installer.cc(325)] FinishRegistration for Widevine Content Decryption Module
[5128:5128:1005/091834:VERBOSE1:default_component_installer.cc(325)] FinishRegistration for EV Certs CT whitelist
[5128:5128:1005/091834:VERBOSE1:default_component_installer.cc(360)] Component ready, version 7 in /home/administrator/.config/chromium/EVWhitelist/7
[5128:5128:1005/091834:VERBOSE1:ev_whitelist_component_installer.cc(102)] Component ready, version 7 in /home/administrator/.config/chromium/EVWhitelist/7
[5128:5128:1005/091834:VERBOSE1:default_component_installer.cc(325)] FinishRegistration for Signed Tree Heads
[5128:5128:1005/091834:VERBOSE1:default_component_installer.cc(325)] FinishRegistration for Origin Trials
[5128:5128:1005/091834:VERBOSE1:default_component_installer.cc(325)] FinishRegistration for File Type Policies
[4:4:1005/091834:VERBOSE1:child_thread_impl.cc(355)] Mojo is enabled on child
[5128:5192:1005/091834:VERBOSE1:ev_whitelist_component_installer.cc(41)] Reading EV whitelist from file: /home/administrator/.config/chromium/EVWhitelist/7/_platform_specific/all/ev_hashes_whitelist.bin
[5128:5192:1005/091834:VERBOSE1:packed_ct_ev_whitelist.cc(66)] Uncompressing EV whitelist of size 674082
[5128:5149:1005/091834:VERBOSE1:bus.cc(873)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s
string "org.bluez"
[5128:5149:1005/091834:VERBOSE1:bus.cc(702)] Filter function already exists: 1 with associated data: 0x57369e80
[5128:5149:1005/091834:VERBOSE1:bus.cc(873)] Method call: message_type: MESSAGE_METHOD_CALL
interface: org.freedesktop.DBus
member: GetNameOwner
signature: s
string "org.bluez"
[5128:5128:1005/091834:VERBOSE1:bluetooth_media_client.cc(75)] Remote Media added: /org/bluez/hci0
[5128:5128:1005/091834:VERBOSE1:bluetooth_agent_service_provider.cc(35)] Creating Bluetooth Agent: /org/chromium/bluetooth_agent
[5128:5128:1005/091834:VERBOSE1:bluetooth_adapter_bluez.cc(235)] 1 Bluetooth adapter(s) available.
[5128:5128:1005/091834:VERBOSE1:bluetooth_adapter_bluez.cc(895)] /org/bluez/hci0: using adapter.
[5128:5128:1005/091834:VERBOSE1:bluetooth_adapter_bluez.cc(897)] Registering pairing agent
[5128:5128:1005/091834:VERBOSE1:bluetooth_adapter_bluez.cc(970)] /org/bluez/hci0: adapter removed.
[5128:5128:1005/091834:VERBOSE1:bluetooth_adapter_bluez.cc(177)] Unregistering pairing agent
[5128:5128:1005/091834:VERBOSE1:bluetooth_agent_service_provider.cc(111)] Cleaning up Bluetooth Agent: /org/chromium/bluetooth_agent
[5128:5192:1005/091834:VERBOSE1:ev_whitelist_component_installer.cc(57)] EV whitelist: Successfully loaded.
[5128:5163:1005/091834:VERBOSE1:packed_ct_ev_whitelist.cc(26)] Setting new EV Certs whitelist.
[11:11:1005/091834:VERBOSE1:child_thread_impl.cc(355)] Mojo is enabled on child
[12:12:1005/091834:VERBOSE1:child_thread_impl.cc(355)] Mojo is enabled on child
Segmentation fault (core dumped)
administrator@administrator-desktop:~$ [3:3:0100/000000:FATAL:zygote_linux.cc(515)] Check failed: len > 0 (0 vs. 0)
#0 0x000076e1d9ae base::debug::StackTrace::StackTrace()
#1 0x000076e2ff4e logging::LogMessage::~LogMessage()
#2 0x000075d83b9a <unknown>
#3 0x000075d842cc <unknown>
#4 0x000075d8448e <unknown>
#5 0x000075d84778 <unknown>
#6 0x000075d84a8a <unknown>
#7 0x000075d85828 <unknown>
#8 0x000075b0a27c <unknown>
#9 0x000075b0a7b4 <unknown>
#10 0x000075b09e7e content::ContentMain()
#11 0x000054d9eb9c ChromeMain
#12 0x000072ac18aa __libc_start_main
Received signal 6
#0 0x000076e1d9ae base::debug::StackTrace::StackTrace()
#1 0x000076e1dc98 <unknown>
#2 0x000072ad0260 <unknown>
#3 0x000072ac1af6 <unknown>
#4 0x000072acf638 gsignal
#5 0x000072ad033a abort
[end of stack trace]

[FalconFour]

I have a solution! At least, it seems I do.
I’m running Ubuntu MATE 16.04 on an ODROID XU4 board. Really capable little machine. Except that I couldn’t get Chrome to sign-in - giving the infamous “Uh-oh!” error. Now, seeing Chrome 53 working, it seems that there’s a new interface for authenticating, which may be why it fails. In my build, Chromium’s packages were held-back by default, stuck at an old build (48, I think). Unlocking it resulted in the “Segmentation Fault” error discussed in this thread. Going through a couple hunches and some leads here, I finally found a combination that works.

Problem is, I’m a “new user” so I can’t post links… I’ll have to obfuscate these (the terminal commands will need to be edited).

Anyway, here’s what I did to get Chrome 53 working on it.

1. Go to http://ports.ubuntu.com/ubuntu-ports/pool/universe/c/chromium-browser/ and locate the Chromium packages for Ubuntu 14.04, not Ubuntu 16.04. In my case, these were:
   chromium-browser-l10n_53.0.2785.143-0ubuntu0.14.04*.1.1145_all.deb
   chromium-browser_53.0.2785.143-0ubuntu0.14.04.1.1145_armhf.deb
   chromium-codecs-ffmpeg-extra_53.0.2785.143-0ubuntu0.14.04.1.1145_armhf.deb
2. Install these packages using “dpkg -i”
3. Hold the packages, if desired, to prevent an “apt-get upgrade” from overwriting with bad versions.

In plain English, summary to get you on version 53:
Open a Terminal
Enter the commands (edit the “hxxp” since I “can’t post links”!)
cd ~/Downloads wget hxxp://ports.ubuntu.com/ubuntu-ports/pool/universe/c/chromium-browser/chromium-browser-l10n_53.0.2785.143-0ubuntu0.14.04.1.1145_all.deb wget hxxp://ports.ubuntu.com/ubuntu-ports/pool/universe/c/chromium-browser/chromium-browser_53.0.2785.143-0ubuntu0.14.04.1.1145_armhf.deb wget hxxp://ports.ubuntu.com/ubuntu-ports/pool/universe/c/chromium-browser/chromium-codecs-ffmpeg-extra_53.0.2785.143-0ubuntu0.14.04.1.1145_armhf.deb

Now, you’ll need to sudo, so you can’t paste commands all at once (it’ll enter pasted data as your password). So, start with one sudo that’ll give you a session:
sudo dpkg -i chromium-codecs-ffmpeg-extra_53.0.2785.143-0ubuntu0.14.04.1.1145_armhf.deb

Then, once that is done, run this:
sudo dpkg -i chromium-browser_53.0.2785.143-0ubuntu0.14.04.1.1145_armhf.deb sudo dpkg -i chromium-browser-l10n_53.0.2785.143-0ubuntu0.14.04.1.1145_all.deb sudo apt-mark hold chromium-browser chromium-browser-l10n chromium-codecs-ffmpeg-extra

That should be it! However, one last thing I did along the way that may or may not be necessary - one fix I attempted (that got Chromium 50 working) was to also install libgcrypt11_1.5.3-2ubuntu4.3_armhf.deb. You may need to look that package up and install as well. Would love to know if it’s necessary with the steps above.

[rph]

Hi,

I just installed version 16.04. Has the problem with Chromium been fixed yet ? Because Chromium is still crashing for me. I thought by now this issue would have been resolved…Anyone ?

[anon4084413]

Issue has not been resloved. Same issue on my RP3 running:

chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1291
Candidate: 59.0.3071.109-0ubuntu0.16.04.1291
Version table:
*** 59.0.3071.109-0ubuntu0.16.04.1291 500
500 http://ports.ubuntu.com xenial-updates/universe armhf Packages
500 http://ports.ubuntu.com xenial-security/universe armhf Packages
100 /var/lib/dpkg/status
49.0.2623.108-0ubuntu1.1233 500
500 http://ports.ubuntu.com xenial/universe armhf Packages

[markartman]

I’m running chromium just fine on my pi2 & pi3. I forget what version it is. I’ll check when I get home.

[MikaelsSlava]

In case anyone is still getting the "Segmentation fault" error message when launching chromium-browser (I'm using FullPageOS), the way I solved this is by deleting the .pki directory in the home of the user running it. Tried other stuff as well (like deleting .config/chromium directory and reinstalling/ downgrading chromium-browser) but this is what led me to get it working again.

Inspiration: Bottom of chromium & chrome segmentation fault / Pacman & Package Upgrade Issues / Arch Linux Forums