Page 1 of 1

Chrome Won't Start

PostPosted: Mon Sep 21, 2015 5:41 am
by tjh
I have NO idea what's happening here.

Chrome has been running fine for me under grsec. I have a little script I run to fix the binaries:

Code: Select all
paxctl -cm /opt/google/chrome/chrome
paxctl -cm /opt/google/chrome/chrome-sandbox
paxctl -cm /opt/google/chrome/nacl_helper


But today, chrome refuses to start. Booting into a non-grsec kernel is fine.

Chrome isn't even trying to start. There's nothing appearing in dmesg. This is what I get when I strace chrome:

Code: Select all
tim@xps:~$ strace  /opt/google/chrome/chrome
execve("/opt/google/chrome/chrome", ["/opt/google/chrome/chrome"], [/* 61 vars */] <unfinished ...>
+++ killed by SIGKILL +++
Killed


Here's dmesg:

Code: Select all
[ 1141.748611] grsec: process /usr/bin/strace(strace:4121) attached to via ptrace by /usr/bin/strace[strace:4119] uid/euid:1000/1000 gid/egid:1000/1000, parent /bin/bash[bash:4098] uid/euid:1000/1000 gid/egid:1000/1000
[ 1141.749235] grsec: process /usr/bin/strace(strace:4122) attached to via ptrace by /usr/bin/strace[strace:4119] uid/euid:1000/1000 gid/egid:1000/1000, parent /bin/bash[bash:4098] uid/euid:1000/1000 gid/egid:1000/1000


I can't figure it out. No error message, no matter what paxctl I give chrome it won't run at all.

Any suggestions as to what's causing this? I would think "corrupt binary" but as I said, a non-grsec kernel it runs just fine.

Every other binary seems to be running fine. The only thing I can think I've done is to install paxctld. But it's not even running...

Re: Chrome Won't Start

PostPosted: Mon Sep 21, 2015 5:54 am
by PaX Team
check the PaX flags on the chrome binaries, they're probably inconsistent (including the xattr based ones if you enabled them in the kernel).

Re: Chrome Won't Start

PostPosted: Mon Sep 21, 2015 2:46 pm
by tjh
Thanks PaX Team, that's exactly what it was.

I hadn't read the man page closely for paxctld and of course it states quite clearly it modifies the xattr attribs. Which were set a bit differently.

Fixed now, thanks again.