LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware 14.2 x64 - Chromium 83 wouldn't start (https://www.linuxquestions.org/questions/slackware-14/slackware-14-2-x64-chromium-83-wouldnt-start-4175677691/)

glupa4e 06-26-2020 02:35 PM

Slackware 14.2 x64 - Chromium 83 wouldn't start
 
Hello,

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.

Here is the version
Code:

bash-4.3$ chromium-browser --version
Chromium 83.0.4103.116

Please let me know if i can help you with further debug messages.

thank you!

TheRealGrogan 06-26-2020 03:48 PM

I'd try renaming ~/.config/chromium (or whatever it is... chrome, chromium, google-chrome... I can't remember but it's under ~/.config)

Could be wrong permissions on the socket or something in the profile directory.

glupa4e 06-27-2020 02:20 PM

As a normal user i did
Code:

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.

What should i do next?

bassmadrigal 06-27-2020 03:13 PM

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.

glupa4e 06-28-2020 02:00 PM

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.


TheRealGrogan 06-28-2020 02:42 PM

What about /tmp, are the permissions correct?

Code:

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.

Code:

df -hT
To check inodes use "df -i"

glupa4e 07-03-2020 11:25 AM

Thank you, TheRealGrogan!
 
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?

bassmadrigal 07-03-2020 12:37 PM

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.

glupa4e 07-03-2020 01:17 PM

Alright, bassmadrigal
 
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.

thanks to all!

TheRealGrogan 07-03-2020 02:21 PM

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 :-)

perbh 07-03-2020 03:31 PM

But ... slackware has '/etc/rc.d/rc.local_shutdown' which I have never come across anywhere else. This is what mine look like
Code:

#!/bin/bash
/usr/bin/find /tmp -mindepth 1 -maxdepth 1 -print0 | xargs -0r /bin/rm -rf

This will clean out /tmp on any reboot/shutdown


All times are GMT -5. The time now is 12:39 AM.