Then, after some days, it presented the issue of my question. It is exactly the same issue as in the Antoine Pintout linked report. Thanks to the fundamental observations from the Antoine Pintout answer, I recalled that I had installed several new fonts, not included in the Ubuntu base system.Ī first effect was that the "Save page" window in Chromium was no more able to use any font, displaying instead a vertical empty rectangle ▯ for each letter. I also tried to run chromium-browser -disable-gpu -disable-software-rasterizer after export MESA_GLSL_CACHE_DISABLE=true, but the error messages are the same as above. I use the CPU integrated graphic card, CPU is Intel Core i5 4670. I did not intentionally install any graphic driver, so I guess I'm using the default ones shipped with Ubuntu 20.04. MESA-LOADER: failed to open swrast (search paths /snap/chromium/1229/usr/lib/x86_64-linux-gnu/dri)Īnd the same with chromium -disable-gpu -disable-software-rasterizer. MESA-LOADER: failed to open kms_swrast (search paths /snap/chromium/1229/usr/lib/x86_64-linux-gnu/dri) MESA-LOADER: failed to open i915 (search paths /snap/chromium/1229/usr/lib/x86_64-linux-gnu/dri) MESA-LOADER: failed to retrieve device information Update 2: $ chromium-browser -disable-gpu -disable-software-rasterizer With chromium -disable-extensions, the message is the same. WARNING: Kernel has no file descriptor comparison support: Operation not permitted InitializeSandbox() called with multiple threads in process gpu-process. Update: when launched from a terminal, according to a suggestion in an answer, I get: $ chromium-browser -disable-extensions Note that the program is chromium, but despite this, the log lines automatically report the name chrome, for reasons I do not know (maybe because chromium is anyway based on chrome). In both /var/log/syslog and /var/log/kern.log, the following line is generated: kernel: traps: chrome trap int3 ip:557cd4d7b152 sp:7fffde23a9c0 error:0 in chromeĪlso, in /var/log/apport.log, for each execution attempt, this line appears: ERROR: apport (pid 5556) Thu Jul 16 10:32:47 2020: host pid 5324 crashed in a separate mount namespace, ignoring It all seems up-to-date, but chromium can not start. Snapd 2.45.2 8542 latest/stable canonical✓ snapd 89 1229 latest/stable canonical✓ -Ĭore18 20200707 1880 latest/stable canonical✓ base Name Version Rev Tracking Publisher NotesĬhromium. I am running Ubuntu 20.04 x86_64 and using chromium installed with snap: $ snap list
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |