1 |
Hi folks, |
2 |
|
3 |
I've been using chromium successfully on my ~x86 system for quite a |
4 |
long time, but starting with the last two updates that came in during |
5 |
the last few days (namely, chromium-40.0.2214.85 and |
6 |
chromium-40.0.2214.91), I started having problems. |
7 |
|
8 |
Both of these versions build just fine, but upon trying to launch |
9 |
them, the browser's interface comes up just fine, but will only |
10 |
display a "Something went wrong..." page. I can try typing in and |
11 |
accessing URLs, but all I will ever get is this error page. |
12 |
|
13 |
That's not all, though, I also get to see error messages, namely the |
14 |
following in my terminal: |
15 |
|
16 |
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf |
17 |
failure in syscall 0265 |
18 |
|
19 |
And this here in dmesg: |
20 |
|
21 |
chrome[5274]: segfault at e806109 ip b5c5c945 sp ac280980 error 6 in |
22 |
chrome[b1864000+5eed000] |
23 |
|
24 |
Great, I thought, something wrong with the sandbox stuff. So I tried |
25 |
to launch chromium without it ("chromium --no-sandbox"), and indeed: |
26 |
The browser works absolutely fine this way - I get none of the |
27 |
problems or messages mentioned above. |
28 |
|
29 |
Of course, I tried to find a related entry in both the Gentoo as well |
30 |
as the chromium bug trackers, but I couldn't find anything in either. |
31 |
I'm a bit reluctand to report my own bug as I wouldn't be 100% sure |
32 |
that I'm not causing the problem (after all, I'm building my chromium |
33 |
with USE=custom-cflags, which is not officially supported, but has |
34 |
always produced nicely working builds for me in the past), so I |
35 |
thought I'd ask here first if I'm the only one observing this |
36 |
behavior. |
37 |
|
38 |
The question, thus, would probably be: Anyone using one of the recent |
39 |
chromium-40 versions on ~x86 or anywhere else and seeing something |
40 |
similar? Or probably someone who has experienced something like that |
41 |
before and could offer a guess what might be wrong here - a real bug, |
42 |
custom-cflags, or something entirely different? |
43 |
|
44 |
Thank all of you in advance! |
45 |
|
46 |
Greetings, |
47 |
Nils |