Linux solves the problem that Deepin cannot start Google Chrome browser as root user

To solve the problem that Deepin cannot start Google Chrome browser as root user, follow the steps below.

1. Find the path of Chrome

which google-chrome

If the path is: /usr/bin/google-chrome

2. Edit the google-chrome file

Open google-chrome and modify the command at the end of the file.

vim /usr/bin/google-chrome

Add --user-data-dir --no-sandbox to the end of exec -a "$0" "$HERE/chrome" "$@"

Press Esc, :wq, exit and save, and now you can open the Chrome browser!

ps: Let's see how to start Apache|Nginx with a non-root user

As we all know, port 80 of Apache is a system reserved port. If it is started by other non-root users, the following error will be reported:

(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
No listening sockets available, shutting down
Unable to open logs

Because ordinary users can only use ports above 1024, ports within 1024 can only be used by the root user.

However, in order to avoid having to go through the root user every time you start the computer, you can solve this problem by setting the UID.

You can complete it by performing the following operations at one time.

Do the following in the root user environment
cd ……/apache/bin
chown root httpd
chmod u+s httpd
su again - USERNAME
Go to the normal user and use .../apache/bin/apachectl start

Why not chmod u+s apachectl?
Because the set UID method is only valid for binary files, and tailing apachectl found:
apachectl is a script file. After careful review, I found the following sentence

HTTPD='/home/……/apache/bin/httpd'

Conclusion: The apachectl script starts the entire httpd service by starting the httpd file.
Run cat httpd again, and various unreadable garbled characters appear. Press ctrl+c to end the output, and you can tell that httpd is a binary file.
Finally, chmod u+s httpd. Of course, you must ensure that the owner of httpd is the root user. If not, execute:
Just chown root httpd.

Similarly, the same is true for starting nginx. Use the root user to enter....nginx/sbin

Then chown root nginx

chmod u+s nginx

Then you can start it through a normal user.

The same is true for tomcat.

Of course, it is also possible to modify the default port to a value greater than 1024.

Summarize

The above is what I introduced to you about Linux to solve the problem that Deepin cannot start Google Chrome browser as root user. I hope it will be helpful to you. If you have any questions, please leave me a message and I will reply to you in time!