Follow-up on google chrome will not start on Slackware 15.0
by rocknrobin from LinuxQuestions.org on (#6QBCK)
Hell-o, I am following up on this thread:
https://www.linuxquestions.org/quest...ght=rocknrobin
which concerned not being able to start Google Chrome from my Slackware Distro 15.0 plasma kde desktop. After I got my head out of my keister and tried starting google-chrome-stable from a Konsole session on the plasma desktop what solved my issue was to run
sudo chmod 1777 /dev/shm
as suggested when trying to start Google chrome from Konsole.
Code:
[29243:29243:0806/124428.416039:FATAL:platform_shared_memory_region_posix.cc(219)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix.Chrome now starts and stops normally even after running an update from a script I got from Slackbuilds.org
https://slackbuilds.org/repository/1...oogle%20chrome
However when I restart or reboot Slackware it goes back to not being able to start Chrome. I then run the chmod on /dev/shm and it works again.
Does anybody know why the permissions get changed on /dev/shm on reboot or should I just put the chmod command in my rc.local file to run it at boot up time? It seems to me that the latter course would be just putting a band-aid on it.
Thanks for any and all help.
https://www.linuxquestions.org/quest...ght=rocknrobin
which concerned not being able to start Google Chrome from my Slackware Distro 15.0 plasma kde desktop. After I got my head out of my keister and tried starting google-chrome-stable from a Konsole session on the plasma desktop what solved my issue was to run
sudo chmod 1777 /dev/shm
as suggested when trying to start Google chrome from Konsole.
Code:
[29243:29243:0806/124428.416039:FATAL:platform_shared_memory_region_posix.cc(219)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix.Chrome now starts and stops normally even after running an update from a script I got from Slackbuilds.org
https://slackbuilds.org/repository/1...oogle%20chrome
However when I restart or reboot Slackware it goes back to not being able to start Chrome. I then run the chmod on /dev/shm and it works again.
Does anybody know why the permissions get changed on /dev/shm on reboot or should I just put the chmod command in my rc.local file to run it at boot up time? It seems to me that the latter course would be just putting a band-aid on it.
Thanks for any and all help.