Created attachment 948841 [details] video showing the systemd crash on starting google chrome. Description of problem: systemd crashed - killed by SIGSEGV on starting google chrome 38.0.2125 (latest) Version-Release number of selected component (if applicable): systemd-208-22.fc20 google-chrome 38.0.2125.104 How reproducible: Each time Google-chrome is started Steps to Reproduce: 1. Start Google-chrome 38.0.2125.104 2. 3. Actual results: Google chrome starts and abrt reports a systemd crash (video attached). Google chrome continues to function normally but similar systemd crashes continue in background every few minutes. Expected results: Additional info: --- Running report_uReport --- A bug was already filed about this problem: Bugzilla: URL=https://bugzilla.redhat.com/show_bug.cgi?id=1154234 The bug is closed due to insufficient data.
OK, after the crash, does 'systemctl' work and print something?
systemctl seems to function normally. Where do i look for systemctl output? google-chrome howsoever outputs the following errors $ google-chrome-stable [1:1:1023/221545:ERROR:nacl_fork_delegate_linux.cc(292)] Bad NaCl helper startup ack (0 bytes) ATTENTION: default value of option force_s3tc_enable overridden by environment. [13939:13939:1023/221547:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [13897:13897:1023/221547:ERROR:desktop_window_tree_host_x11.cc(1547)] Not implemented reached in void views::DesktopWindowTreeHostX11::MapWindow(ui::WindowShowState) getrlimit(RLIMIT_NOFILE) failed I also have Google-Chrome beta installed which does not crash systemd. The output on running it. $ google-chrome-beta ATTENTION: default value of option force_s3tc_enable overridden by environment. [14086:14086:1023/221759:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process getrlimit(RLIMIT_NOFILE) failed
When systemd crashes then systemctl stops working. (systemctl communicates with systemd over dbus, and when systemd crashes is intercepts the signal and "freezes", so then systemctl waits a bit and fails with "did not receive a reply" or something similar). So if systemctl is working that means that systemd did not crash.
When systemd crashes then information about it should be logged in journal. Something like Oct 27 14:18:20 localhost.localdomain systemd[1]: Freezing execution. Oct 27 14:18:20 localhost.localdomain systemd[1]: Caught <SEGV>, dumped core as pid 1068. Also core file is then stored in /. Can you see similar journal entries on your machine?
I don't remember seeing a similar entry in the logs. I have moved on the Fedora 21 and I'm facing no problem now.