Thanks for this information. This is still very curious since according to your /var/crash/, Upstart did seemingly crash, but on a different day to chrome (chromium) crashing. Also, the upstart crash file seems to have been uploaded before the crash occurred. That might be because you've had multiple init crashes.
Please could you attach both of the following to this bug:
Also, please could you attach file '/tmp/setuid+setgid.log' generated by the following which looks for setuid and setgid root binaries under /opt/google/:
Hi Huubb,
Thanks for this information. This is still very curious since according to your /var/crash/, Upstart did seemingly crash, but on a different day to chrome (chromium) crashing. Also, the upstart crash file seems to have been uploaded before the crash occurred. That might be because you've had multiple init crashes.
Please could you attach both of the following to this bug:
/var/crash/ _sbin_init. 0.crash _usr_lib_ chromium- browser_ chromium- browser. 1000.crash
/var/crash/
Also, please could you attach file '/tmp/setuid+ setgid. log' generated by the following which looks for setuid and setgid root binaries under /opt/google/:
sudo find /opt/google -user root \( -perm +4000 -o -perm +7000 \) -ls > /tmp/setuid+ setgid. log
Finally, a couple of questions:
1) How do you start chrome? From the command-line?
2) What user are you running chrome as (huub or root)?