i.MX Processors中的主题 Chromium browser does not start in user context

Chromium browser does not start in user context

MicMoba — Wed, 22 Feb 2023 14:01:00 GMT

I want to use Chromium-ozone-wayland browser on my device. I had build the yocto image sucessfully. Chrome Version: Chromium 96.0.4664.110 stable

When I start chromium as user I got the following error message:

user@ ~$ chromium [1223:1223:0222/143357.967200:ERROR:process_singleton_posix.cc(340)] Failed to create /home/moba/.config/chromium/SingletonLock: Operation not permitted (1) [1223:1223:0222/143357.967678:ERROR:chrome_browser_main.cc(1313)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.

I can start chromium as root user with 'chromium --no-sandbox'

What does it mean 'Failed to create a ProcessSingleton'? My home is located on a fat32 partition. But I can not image that this has something to do with it.

Edit:

When I use 'chromium --user-data-dir=/tmp/' chromium started. So error maybe depends on the fat32 partition?

Re: Chromium browser does not start in user context

AldoG — Thu, 02 Mar 2023 20:41:11 GMT

Hello,

looking through the web this seems to be a problem related to the space left in your partition:
https://bugs.chromium.org/p/chromium/issues/detail?id=73035
https://stackoverflow.com/questions/38894321/chromium-browser-singleton-bug-caused-by-power-failure

Best regards,
Aldo.

Re: Chromium browser does not start in user context

MicMoba — Fri, 03 Mar 2023 07:52:02 GMT

Hi AldoG,

thanks for the hints. I checked the remaining space at my home directory. It is over 5GB free space available. But it is a FAT32 partition. The rootfs is an ext4 partition. Maybe it has something to do with the mixture of both filesystems.