Chromium w Debianie unstable nie startuje

Gdyby komuś w Debianie unstable przestało działać chromium, a przy uruchomieniu polecenia w konsoli pokazywało się coś takiego:

$ chromium [4278:4278:1113/085947.509811:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox. #0 0x562ca49ba9ee <unknown> #1 0x562ca492699c <unknown> #2 0x562ca55b8f90 <unknown> #3 0x562ca45f9365 <unknown> #4 0x562ca45fe5ce <unknown> #5 0x562ca45f7e5a <unknown> #6 0x562ca2d09e95 ChromeMain #7 0x7fbb5a4f6b17 __libc_start_main #8 0x562ca2d09d3a _start Received signal 6 #0 0x562ca49ba9ee <unknown> #1 0x562ca49b9433 <unknown> #2 0x562ca49ba965 <unknown> #3 0x7fbb633dc8e0 <unknown> #4 0x7fbb5a509f3b gsignal #5 0x7fbb5a50b2f1 abort #6 0x562ca49ba905 <unknown> #7 0x562ca4926a76 <unknown> #8 0x562ca55b8f90 <unknown> #9 0x562ca45f9365 <unknown> #10 0x562ca45fe5ce <unknown> #11 0x562ca45f7e5a <unknown> #12 0x562ca2d09e95 ChromeMain #13 0x7fbb5a4f6b17 __libc_start_main #14 0x562ca2d09d3a _start r8: 0000000000000000 r9: 00007ffe7d2f0920 r10: 0000000000000008 r11: 0000000000000246 r12: 00007ffe7d2f0da0 r13: 00007ffe7d2f0f60 r14: 000000000000016b r15: 00007ffe7d2f0ba0 di: 0000000000000002 si: 00007ffe7d2f0920 bp: 00007ffe7d2f0b70 bx: 0000000000000006 dx: 0000000000000000 ax: 0000000000000000 cx: 00007fbb5a509f3b sp: 00007ffe7d2f0920 ip: 00007fbb5a509f3b efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated.

to sprawa jest znana, błąd jest zgłoszony i wystarczy doinstalować pakiet chromium-sandbox.

Dodaj komentarz