SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i installed the latest version of Chromium from Alien Bob's repository. Now i get the following error:
Code:
bash-4.3$ chromium-browser
[22786:22786:0626/212952.641252:ERROR:process_singleton_posix.cc(1002)] Failed to create socket directory.
[22786:22786:0626/212952.641400:ERROR:chrome_browser_main.cc(1258)] 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.
bash-4.3$ cd .config/
bash-4.3$ chromium
[23514:23514:0627/211636.845053:ERROR:process_singleton_posix.cc(1002)] Failed to create socket directory.
[23514:23514:0627/211636.845270:ERROR:chrome_browser_main.cc(1258)] 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.
bash-4.3$ chromium-browser
[23554:23554:0627/211649.661350:ERROR:process_singleton_posix.cc(1002)] Failed to create socket directory.
[23554:23554:0627/211649.663610:ERROR:chrome_browser_main.cc(1258)] 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.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
No, what TheRealGrogan meant was to rename chromium's config folder in case there's some permissions or corruption issue. That folder most likely sits under ~/.config. For Chrome, it is ~/.config/google-chrome/, but I'm not sure what Chromium's is (probably ~/.config/chromium/).
Simply rename it doing the following (changing the folder to match whatever is on your system).
Code:
mv ~/.config/chromium ~/.config/chromium-bak
This essentially gets you a new profile. Now try and start chromium and see if it gives you the same error.
Thank you bassmadrigal! I did what you posted. In my case i have chromium and chromium-browser. I deleted chromium config profile and started again chromium-browser and here is what i got
Code:
bash-4.3$ chromium-browser
[26177:26177:0628/205641.844869:ERROR:process_singleton_posix.cc(1002)] Failed to create socket directory.
[26177:26177:0628/205641.845118:ERROR:chrome_browser_main.cc(1258)] 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.
bash-4.3$ chromium
[26221:26221:0628/205654.993149:ERROR:process_singleton_posix.cc(1002)] Failed to create socket directory.
[26221:26221:0628/205654.993374:ERROR:chrome_browser_main.cc(1258)] 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.
ls -ld /tmp
drwxrwxrwt 7 root root 118784 Jun 28 15:06 /tmp
The /tmp directory should be set as "chmod 1777" if it isn't. (special permission so that all users can write to it, but only the owners have access to their objects within)
Consider cleaning out /tmp of anything that looks chromium related.
I also have to mention, could there still be a chromium process running? (I don't know if you've rebooted the machine or anything since). "killall -9 chromium" or chromium-browser.
Could you be out of space, or inodes on any of your partitions?
The error basically means that chromium can't create its "ProcessSingleton" socket.
The problem was that i really had my partition under /tmp full. When i deleted it, all went smoothly.
I have this issue that i install pckages using sboui and it stores the packages under
Code:
/tmp/SBo
and from time to time it gets full and i end up in such stupid situations, either not able to login or like the one with chromium.
TheRealGrogan, do you maybe know how could i set it up that older files are deleted there or after successful installation they are deleted from that location?
I don't use sboui, but looking through the files in its github, I believe if you change CLEAN_PACKAGE=no to CLEAN_PACKAGE=yes in sboui-backend.conf (I'm guessing under /etc/sboui/), that should remove things.
In fact, there is a configuration file residing under
Code:
/etc/sboui/sboui-backend.conf
as resommended by bassmadrigal i changed settings to
Code:
# Whether to remove built package after installing (yes/no)
CLEAN_PACKAGE=yes
# Whether to remove temporary source and package directories after building
CLEAN_TMP=yes
i hope this would save me from falling in so hilarious situations.
Slackware would be one of the few distros left where /tmp isn't volatile. Most others mount it on a tmpfs mount nowadays, and other (e.g. non-systemd) distros may clear it in the startup scripts. However, yeah, it's the default location for package building on Slack, so unless that changes, the distro really can't clear it... imagine someone having to reboot and all the packages they just built are gone :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.