LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-26-2020, 02:35 PM   #1
glupa4e
Member
 
Registered: Jan 2011
Posts: 264

Rep: Reputation: 2
Unhappy 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!
 
Old 06-26-2020, 03:48 PM   #2
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 389

Rep: Reputation: 254Reputation: 254Reputation: 254
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.
 
Old 06-27-2020, 02:20 PM   #3
glupa4e
Member
 
Registered: Jan 2011
Posts: 264

Original Poster
Rep: Reputation: 2
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?
 
Old 06-27-2020, 03:13 PM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,151

Rep: Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820
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.
 
Old 06-28-2020, 02:00 PM   #5
glupa4e
Member
 
Registered: Jan 2011
Posts: 264

Original Poster
Rep: Reputation: 2
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.
 
Old 06-28-2020, 02:42 PM   #6
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 389

Rep: Reputation: 254Reputation: 254Reputation: 254
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"
 
1 members found this post helpful.
Old 07-03-2020, 11:25 AM   #7
glupa4e
Member
 
Registered: Jan 2011
Posts: 264

Original Poster
Rep: Reputation: 2
Wink 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?
 
Old 07-03-2020, 12:37 PM   #8
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,151

Rep: Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820Reputation: 4820
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.
 
1 members found this post helpful.
Old 07-03-2020, 01:17 PM   #9
glupa4e
Member
 
Registered: Jan 2011
Posts: 264

Original Poster
Rep: Reputation: 2
Thumbs up 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!
 
Old 07-03-2020, 02:21 PM   #10
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 389

Rep: Reputation: 254Reputation: 254Reputation: 254
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 :-)
 
Old 07-03-2020, 03:31 PM   #11
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 338

Rep: Reputation: 65
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
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
FFMPEG for APACHE 2.4.6 (x64), PHP 5.5 (x64), MYSQL 5.6 (x64) on WINDOWS 8 (x64) Punctual Programming 3 08-07-2013 05:20 PM
Slackware 13.37 x64 & Windows 7 x64 Dual Boot Issues toolman30044 Slackware 4 08-08-2011 02:39 PM
LVM needs e2fsck after Upgrade from Kubuntu 8.10 x64 to 9.04 x64 don_wombat_73 Linux - Newbie 6 04-30-2009 04:13 PM
rss-glx_0.8.1 package wouldn't start in Mandriva 2008 zebra90210 Linux - Software 1 04-17-2008 12:05 AM
can i run linux mandriver x64 with windows x64 bit if so wich one should i install fi malmac2000 Linux - Software 2 04-26-2006 07:04 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration