On 2020-01-29, Allan Streib <[email protected]> wrote: > Per the man page I have tried to launch chrome with an alternate data > directory hoping to achieve separate profiles. > > $ chrome --user-data-dir=~/.config/chromium_a > > > [75336:1591778608:0129/114259.294272:ERROR:process_singleton_posix.cc(280)] > Failed to create /home/astreib/.config/chromium_a/SingletonLock: No such file > or directory (2) > [75336:1591778608:0129/114259.294449:ERROR:chrome_browser_main.cc(1413)] > 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. > [75336:-995142592:0129/114259.302586:ERROR:cache_util.cc(141)] Unable to > move cache folder /home/astreib/.config/chromium_a/ShaderCache/GPUCache to > /home/astreib/.config/chromium_a/ShaderCache/old_GPUCache_000 > [75336:-995142592:0129/114259.302696:ERROR:disk_cache.cc(178)] Unable to > create cache > [75336:-995142592:0129/114259.302721:ERROR:shader_disk_cache.cc(605)] > Shader Cache Creation failed: -2 > > I have tried this with ~/.config/chromium_a as an empty directory, and > as a copy of ~/.config/chromium (which is created successfully when > chrome is started without any args). > > Thought I would ask if this is simply a known problem before I go > digging too deeply. > > amd64 6.6 release with syspatches and pkg updates applied as of today. > > Allan > >
You will at least need to relax the "unveil" restrictions in /etc/chromium. Whichever files have .config/chromium or .cache/chromium you will need to copy for the _a variant. That might not be the only thing you need to do, but there's no chance without that.
