Arch Linux

Nadyita

Member

Registered: 2017-09-11

Posts: 1

Chrome crashing after last pacman update

Hey all!

Just ran a pacman update this morning and 'lo and behold - after a reboot, all chrome-stable plugins start with the "awww snap!" and crash. So I started it from the terminal and saw the following several times:

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0281

dmesg also listed some hundreds of these:

[  196.278463] Chrome_ChildIOT[1969]: segfault at e119 ip 000055e16a01c553 sp 00007fa04ec78390 error 6 in chrome[55e167b4b000+5bb2000]

Chrome works if I start it with

google-chrome-stable --disable-seccomp-filter-sandbox

it works. Everything I find related to this issue has been fixed long ago, but maybe someone else can help me fixing this? Would greatly appreciate it!

- Nadya

digitalone

Member

Registered: 2011-08-19

Posts: 350

Re: Chrome crashing after last pacman update

I don't know, but chromium-vaapi does not work with latest mesa update.
Maybe it's a similar problem and you can resolve downgrading mesa.

turek

Member

Registered: 2017-09-11

Posts: 7

Re: Chrome crashing after last pacman update

I am getting the same error after "pacman -Syu" this morning while running a different app (jetbrains-toolbox from AUR) which I guess uses an embedded qtwebengine for something.

First it errors/warns with:

[0911/121308:WARNING:resource_bundle.cc(311)] locale_file_path.empty() for locale
Qt WebEngine ICU data not found at /work/external/qt-installer/Qt/5.7/gcc_64/resources. Trying parent directory...
Qt WebEngine ICU data not found at /work/external/qt-installer/Qt/5.7/gcc_64. Trying application directory...
Installed Qt WebEngine locales directory not found at location /work/external/qt-installer/Qt/5.7/gcc_64/translations/qtwebengine_locales. Trying application directory...
Qt WebEngine locales directory not found at location /tmp/.mount_UfePUr/usr/share/jetbrains-toolbox/libexec/qtwebengine_locales. Trying fallback directory... Translations MAY NOT not be correct.
Qt WebEngine resources not found at /work/external/qt-installer/Qt/5.7/gcc_64/resources. Trying parent directory...
Qt WebEngine resources not found at /work/external/qt-installer/Qt/5.7/gcc_64. Trying application directory...
[0911/121308:WARNING:resource_bundle.cc(311)] locale_file_path.empty() for locale

and then the stack trace:

/home/qt/work/qt/qtwebengine/src/3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0281
Received signal 11 SEGV_MAPERR 00000c003119
#0 0x7f6e13588a2e <unknown>
#1 0x7f6e13588deb <unknown>
#2 0x7f6e0eee4da0 <unknown>
#3 0x7f6e13d72048 <unknown>
#4 0x7f6e13ed3c9e <unknown>
#5 0x7f6e0eee4da0 <unknown>
#6 0x7f6e0e328326 __GI_epoll_pwait
#7 0x7f6e14a64df0 <unknown>
#8 0x7f6e14a63042 <unknown>
#9 0x7f6e1357fd5e <unknown>
#10 0x7f6e135b95a8 <unknown>
#11 0x7f6e135a3b65 <unknown>
#12 0x7f6e135d1b21 <unknown>
#13 0x7f6e135ce1c7 <unknown>
#14 0x7f6e0eeda08a start_thread
#15 0x7f6e0e3281bf __GI___clone
  r8: 0000000000000002  r9: 00007f6e027be56c r10: 0000000000000000 r11: 0000000000000246
r12: 00007f6e027be570 r13: 0000000001c6f550 r14: 00007f6e027be5c0 r15: 0000000001c6e4c0
  di: 0000000000000001  si: 00007f6e15669786  bp: 00007f6e027be5c0  bx: 000000000c003119
  dx: 000000000c000000  ax: 000000000c003000  cx: 00007f6e0eee38bb  sp: 00007f6e027be570
  ip: 00007f6e13d72048 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000006
trp: 000000000000000e msk: 0000000000000000 cr2: 000000000c003119
[end of stack trace]

repeated multiple times over and over again.

This doesn't seem like a problem with jetbrains-toolbox since it didn't even get updated today and the errors are all about qtwebengine.
glibc on the other hand was updated today and according to some quick googling I did, some glibc incompatibilities have caused similar errors in the past.

I think I should add that Chrome works flawlessly (google-chrome from AUR, not chromium from extra).

Last edited by turek (2017-09-11 12:47:30)

sccraven

Member

Registered: 2017-09-11

Posts: 2

Re: Chrome crashing after last pacman update

I got the same error when trying to run jetbrains-toolbox as well.

It looks like the problem is in the latest version of glibc.

I was able to get toolbox working again after downgrading glibc back to version 2.25-7.  In order to downgrade glibc, I also had to downgrade binutils back to version 2.28.0-4.

I did this by running the following commands from /var/cache/pacman/pkg:

pacman -U binutils-2.28.0-4-x86_64.pkg.tar.xz
pacman -U glibc-2.25-7-x86_64.pkg.tar.xz

turek

Member

Registered: 2017-09-11

Posts: 7

Re: Chrome crashing after last pacman update

Thanks for the workaround sccraven.

Is that an Arch problem tho or something wrong with glibc? This is the only relevant topic I found on this issue, which suggests the Arch package is broken.

sccraven

Member

Registered: 2017-09-11

Posts: 2

Re: Chrome crashing after last pacman update

I don't know.

I'm not sure if / how much the maintainers of the Arch package change from the upstream source.
I would think that it's not changed any except for whatever needs to be added for pacman to install it, but that's just a guess.

srki_82

Member

Registered: 2012-04-21

Posts: 9

Re: Chrome crashing after last pacman update

Maybe simply rebuilding QT5 against new glibc should do the trick?

turek

Member

Registered: 2017-09-11

Posts: 7

Re: Chrome crashing after last pacman update

I am rebuliding qt5-webengine against new glibc. If it doesn't work, I will rebuild whole QT5.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,249

Re: Chrome crashing after last pacman update

Why do you think that will help? Chrome doesn't use Qt5 so don't waste your time with rebuilding qt5

Ah just saw the qt5-webengine thing. But again, jetbrains uses its own bundled library, rebuilding your correctly working system libraries will not fix the issue

And this is pretty much a thread hijack, in order to not confuse people you should open new threads for seperate issues, which your issue clearly is.

Last edited by V1del (2017-09-12 09:11:26)

turek

Member

Registered: 2017-09-11

Posts: 7

Re: Chrome crashing after last pacman update

V1del, thanks for your response.

You are partially right. This is the same issue (problems with sandboxing), but jetbrains-toolbox indeed uses it's own version of Qt5 WebEngine, so there is no need to recompile Qt5 for me.

Thanks for all your help. I will open another thread with problems with jetbrains-toolbox and post the solution there.

Last edited by turek (2017-09-12 11:18:27)

bhundven

Member

From: Seattle, WA

Registered: 2015-11-20

Posts: 2

Re: Chrome crashing after last pacman update

See my comments here for jetbrains-toolkit: https://youtrack.jetbrains.com/issue/ALL-2017