most likely, you performed a “graphical login” on behalf of an ordinary user (and this is not just normal, but “that's the way you should do”), and try to run the x-client on behalf of another user. which is not possible by default - the client will not be able to connect to your x-server instance.
The “normal” x client will report this:
$ su - пользователь $ xeyes No protocol specified Error: Can't open display: :0
and the one that you started, apparently, either "does not want" to report about it, or still connected to the x-server, but not to the instance that you are currently watching on the screen.
work should continue under ordinary users, getting root privileges (using su or, sudo programs better) only for solving administrative tasks: configuring the system, installing / removing packages and the like.
/usr/bin/google-chrome-stable- the terminal is just silent. By the way, maybe it's because I'm sitting under root. - user189127sudodidn’t configure and drove to install everything undersu... Now I don’t want to go back and redo everything again :). - user189127.profile,.bashrcand other files, and therefore the environment. But this can be transferred if you have already configured something there. It’s not too late, create a regular user with sudo-rights and switch to it. ) - Nick Volynkin ♦