chromium error on Slackware64-current
by bosth from LinuxQuestions.org on (#54N1J)
I'm running Slackware64-current (multilib if it matters) and am having problems with AlienBob's Chromium (chromium-83.0.4103.97-x86_64-1alien) starting properly. It does start but I get an empty window with no text or GUI widgets.
On the console, I see the following errors:
Code:$ chromium
[17429:17429:0615/170159.397139:ERROR:browser_dm_token_storage_linux.cc(100)] Error: /etc/machine-id contains 0 characters (32 were expected).
[17457:17457:0615/170159.577722:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[17429:17451:0615/170159.769381:ERROR:client_native_pixmap_dmabuf.cc(218)] Failed to mmap dmabuf: Permission denied (13)
[repeated]
[19257:19304:0100/000000.106789:ERROR:native_pixmap_handle.cc(77)] dup: Too many open files (24)
[repeated]From what I can tell, the first error is not the issue here. The final error will continue printing until the process is killed.
Other programs are running fine (including Firefox, my browser of choice). Permissions are fine on /tmp and everywhere else I've looked. I get the same error with other users on the system and have tried wiping .config/chromium and .cache/chromium to no avail.
I don't use Chromium daily, but I believe this only emerged after the latest update to Chromium.
On the console, I see the following errors:
Code:$ chromium
[17429:17429:0615/170159.397139:ERROR:browser_dm_token_storage_linux.cc(100)] Error: /etc/machine-id contains 0 characters (32 were expected).
[17457:17457:0615/170159.577722:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[17429:17451:0615/170159.769381:ERROR:client_native_pixmap_dmabuf.cc(218)] Failed to mmap dmabuf: Permission denied (13)
[repeated]
[19257:19304:0100/000000.106789:ERROR:native_pixmap_handle.cc(77)] dup: Too many open files (24)
[repeated]From what I can tell, the first error is not the issue here. The final error will continue printing until the process is killed.
Other programs are running fine (including Firefox, my browser of choice). Permissions are fine on /tmp and everywhere else I've looked. I get the same error with other users on the system and have tried wiping .config/chromium and .cache/chromium to no avail.
I don't use Chromium daily, but I believe this only emerged after the latest update to Chromium.